Ada Lovelace Day: Professor Leah Buechley

While in Boston last week for LibrePlanet, I met Professor Leah Buechley.

She doesn’t know I’m going to post this, but I figured that I would just do it, and ask forgiveness later.

What impresses me the most about Leah is her creative thinking about the issues of women in technology – recontextualizing issues of breadth and acceptance to apply to any minority groups. I learned about Leah because of her work to create Lilypad Arduino, a microcontroller designed for wearable DIY projects and textiles. She’s put together a sweet tutorial on using Lilypad, and continues to do research related to creative expression through materials not traditionally considered for computing.

She’s part of the high-low tech group at MIT, a group dedicated to integrating high and low technological materials, processes, and cultures.

A super interesting project she’s working on right now is Living Wall – wallpaper designed out of paper and conductive paint that response to it’s environment. The result is beautiful, functional and a geek’s paradise for making an interactive home.

Some of her research targets the issue of creating new communities by tweaking how the technology is used, focusing and targeting use of technology in a novel way. She did this with lilypad arduino by introducing people who aren’t traditionally microcontroller hackers (sewers, knitters, crafters) to a platform designed for their specific uses. Her ideas and success certainly inspire my free and open source software advocacy.

I was completely inspired in the very small amount of time I spent with her chatting about tech communities and the problems we’re trying to solve around diversity. I loved her directness and curiosity. I’m looking forward to seeing what beautiful and super geeky projects she’ll be working on next.

We need vision and collaboration

This is my final comment in this thread – in reference to a comment that we should to create a mega event like SXSW… (I have more to say about this idea, actually, because a large group of us discussed the possibility in detail, and why we thought it wouldn’t work.)

I don’t know much about how SXSW is structured inside, but I do know that they are providing a a unified vision for the conference. That has attracted not just more organizing power, but a huge, devoted attendee and presenter pool.

Stepping out on a limb – perhaps the issue here is more that a vision has not been offered which attracts the groups that you want to collaborate with. Collaboration is not the same thing as aggregation.

Portland tech groups collaborate with each other all the time, but they are loose affiliations and focused on what provides the most value for the limited resources we have. I’ll also say that they are joyful connections – based on mutual benefit, friendship and an outcome whose goal is not just a product, but also having fun.

We often have conversations with each other about how we can make things less expensive, smaller and more fun, rather than how we can grow larger.

It’s possible to have this mindset exist within a larger framework that might encompass it all. It just takes time, trust building, and work to find connections that truly benefit the community. The direct, local benefit should be considered first, and maybe involve promotion outside of our community second. Maybe third.

The tech community has regular, free-form events on Thursday nights at the Lucky Lab, and periodic meetings on Saturdays around OS Bridge. I won’t be here this week, but definitely will be next week. 🙂

I’d be happy to talk with you or anyone else how we might create a larger framework.

Whatever it is needs to be something which can be incrementally built up, and I don’t know that a mega event is what we really need.

Space and time to help our neighbors

I wrote the following in response to Mark Lawler’s original post.

Hey Mark,

We’ve never met. I’m not currently on the board of Legion of Tech, but was one of the founding board members.

I currently am chair of the Open Source Bridge conference and am deeply involved in the open source community both in Portland and throughout the world.

It saddens me deeply to read what you’ve written.

As a person who devotes a substantial amount of her time to volunteering in technical communities, and is also a full-time software developer, I know that the volunteers who work on tech events are the life-blood of our community. Without them, and the incredible number of hours they volunteer, we would have no portland tech “scene”, “community” or an environment that new tech companies or startups would consider being part of.

As points of reference around “decay” – Reductive Labs, a VC-funded startup that develops an open source product, moved to Portland *because* of our vibrant, diverse tech scene. Small Society, Raven Zachary’s consultancy, stayed in Portland because he loves it here – and he is a fixture in our community. Urban Airship (VC funded) is made up of Pythonistas and advocates who have been regulars and organizers of user groups like PDX Python and a new-ish Django group. @al3x, a lead developer at Twitter, is moving to Portland from the bay area next month and will be joining Rael Dornfest, who develops the user experience for Twitter. ShopIgniter just got funded and is hiring.

These are just the examples I have off the top of my head – were I to consult the Silicon Florist blog, I’m sure a dozen more would immediately pop out.

When I look at our community, I see productivity, diversity, opportunity and passion. I see acceleration.

Drumming for consolidation seems to me to be a fundamental misunderstanding of what could be done further to best serve the needs of this community. That’s what these volunteers do – they directly serve the needs of the Portland tech community.

Their goal isn’t to be on a national radar – their goal is to be productive citizens, making the place that they live better. It’s great when others notice, but we work for the gratitude of our neighbors and friends, not national recognition.

And, so, when thinking about the fragmentation, I recommend that you consider whether what you are saying and doing is providing a space and time for people to help their neighbors. Because that’s ultimately what matters to us.

Portland High Tech Groups are Portland Software’s Own Worst Enemies

I had really hoped to be able to share the entire conversation with you, and fortunately I have gotten permission to do so!

I’m reposting Mark Lawler‘s original post to a LinkedIn forum with his permission below. Tomorrow, I’ll post my response. I welcome constructive comments and want to keep this an open forum for discussion.

But a warning: Some people have had a very emotional reaction to Mark’s words, including myself. I very much want to hear people’s thoughts and responses. However, please think for a moment before you post, and keep your comments to things that you would say to Mark were you to meet him in person.

He also wanted to provide some context for his comments:

I do ask that you be an honest broker in rehosting this under the following context (you can quote below):

  • Groups and individuals leading these groups honoring commitments; our word should really be our bond
  • That even though we have many wonderful diverse communities in PDX we do seem to sometimes dive down in to technical and business model “religious” wars
  • There are real stereotypes attributed to Portland and Portland’s high-tech scene that doesn’t do us any favors
  • Perhaps working collaboratively on an event or two a year and drawing press attention through a critical mass wouldn’t be a bad thing (there is some of this going on and it is a good thing)
  • There is real economic value in the bigger picture for all of us in this industry if we can do this to help promote the Silicon Forest

And here is Mark’s original post:

Portland High Tech Groups Are Portland Software’s Own Worst Enemies
By Mark Lawler

Portland has a very vibrant software community. It is one that is quite diverse and covers the entire technology spectrum and represents nearly every business model imaginable. With this diversity comes the desire for each of us to associate with various groups and communities that better represent our interests and sometimes our own ways of thinking. That said, Portland also has a cancer, and that illness manifests itself in how these groups just cannot seem to work together for the common good. The cause? Perhaps it is the strong desire for each of these groups to maintain its own individuality, autonomy, brand identity. Perhaps it is the entrepreneurial pull to forge one’s own ground and to be different from what is already out there. However, it is this bifurcation and standoffishness between the various high tech groups in Portland that is holding us back as we watch the Silicon Forest as a whole slowly decay.

I was just in a meeting last Thursday with Skip Newberry, the Economic Development Policy Advisor for the Office of the Mayor of Portland. With me were key members of some local high tech groups that put on local events to benefit their individual segments of the Portland high-tech community. Our pitch to the Mayor’s Office was simple: It is through all of us working together as a unified front that Portland will be able to combat some of its more silly, yet detrimental stereotypes regarding its software community and industry. That together we could combat the incorrect notions that developers in Portland suffer from “Portland Lazy” disease or that Portland doesn’t have a very rich pool of high-tech talent for companies to leverage. In a unified front four groups were working together to have a mega event in May where they were pooling interests and resources to help Portland in its quest to get itself and the Silicon Forest back on the national radar. We were asking the Mayor’s office if they would be willing to attend the event and use one of the sessions to highlight Portland’s Economic Development plan for the local software industry to the attendees that were interested in learning more about it and sharing their own thoughts while at the same time highlight how we are all working together. During this discussion we talked about Portland’s historic past of having various technical communities and groups working against each other and fighting various technical and business model “religious” wars and how this one event in May was very significant in showing that we could all work together.

You can only imagine my surprise when I learned the very next day that the board of directors for the one of the groups had met Thursday night, that same night that one of their board members had attended this meeting with the Mayor’s office with the rest of us, and decided to pull out of the event.

Now I’m not going to speculate as to why they decided to do it. We all have our reasons for changing our minds. However, I am going to comment on is how this action, just in the very nature of its timing and its impact, is exactly what is wrong with the Portland software community. I love Portland and Portland software. With the time that I spend as a volunteer I work every day to help promote and grow this industry. I pine over the return to the heyday of the Silicon Forest and work hard through the success of the companies I work for and the great products I deliver along with these volunteer efforts to claw our way back.

I have just two questions… Why can’t we all just get along? Why can’t we all drop the inane focus on our individual charters, beliefs and the stubborn demands of individuality to try to work together for the common good of Portland Software and the growth of the industry in Oregon? I ask everybody in high tech sweep away the individual chips on our shoulders and to come together to rally for this common good. If we don’t work together we will go the way of the tanners, textile, shipbuilding, and forestry workers before us. I find that result both uninteresting and unacceptable…

You can contact Mark at: @mark_lawler; http://www.linkedin.com/in/marklawler)

This town needs…

There was a thread in a walled garden recently asking the question: “Why can’t we all just get along?” This was in response to a difficult parting of ways between organizations in Portland trying to run a couple events cooperatively.

Unfortunately, the thread was deleted, so even if you were to join the group at this point, the conversation is lost. Fortunately, I saved a copy and can quote from it in the future as needed!

The situation, as I saw it described, is that some people think of the grass-roots organized groups as obstinate. As unwilling, and possibly opposed, to compromise. The phrase “stubborn demands of individuality” was used to describe the problem the original poster brought up.

In any growing, functional organization or community, there will be conflict. What matters is how we handle that conflict.

I plan on re-posting my original comments here in my blog because I want the thoughts and conversations that were started inside a closed space to come out into the open.

There’s certainly an opportunity in Portland for the many lovely, energetic and productive volunteer groups to pool our talents and resources. Some of that energy has certainly been pooled to produce Open Source Bridge, for which I am enormously grateful.

So, the question in my mind is should we also be doing something else? And if so, what would that something else be?

And by something — I mean just about anything. I’ve never counted, but I’d guess based on the groups and events that I’ve attended that we have well over 1000 volunteers in our technology communities in Portland. Add in the larger professional organizations, and I’m sure we’ve got over 10,000 people in the Portland area (and Vancouver!) whose involvement we could count on.

Let’s hatch a plan.

There’s a push to look outward, and to speak outward. To get “press attention”, which to some, means success. I don’t agree.

We need a different vision. Our communities are ones of people who *do* things. (I’d even go so far to say we have a ‘do-ocracy‘.) We make things, we share them and then we make more things. Certainly there’s room in our communities for people who help us share what we’re doing. But we can’t talk about things we haven’t done.

Anything that enhances our community, must help us do things. Change must make collaboration easier, sharing better and involvement in our communities even more rewarding than it already is.

So, help me. What does success look like to you? What do you wish that you could get out of our technology groups, but don’t?

Speakers workshop at LibrePlanet next week!

I’m headed off to Boston (and then NYC!) next week for three days of free software love at LibrePlanet, March 19-21.

While there, I’ll be giving a speaker’s workshop – how to give talks at technical conferences. There’s not really a magical formula, just lots of tips and things to practice that will help you not only give great talks, but find excellent places to give those talks, be prepared for speaking to any size crowd, and have a good time while you do it.

I started giving talks at conferences about five years ago, and have been running my own conferences for three years. I still get the butterflies when I get up in front of people, but I’ve got a whole kit of strategies I now use to deal with it.

The workshop is scheduled for 3:30-5:30pm, and I’m sure we’ll all head out for dinner and conversation right after.

I’ve also got one free pass to the conference left, so leave a comment if you’ll be in the area and can use the pass.

Also, I’ll have some incredibly profane free software advocacy stickers on-hand to share. We’re free software activists, but we can still have fun, right? 🙂

Unlocking the clubhouse: cultural resistance and learning communities

I finished reading “Unlocking the clubhouse” on Saturday, finally. The book is only about 150 pages long, but it’s full of useful information about increasing participation of women in computer science.

The chapter that most stuck with me was chapter 6, “Persistence and Resistance: Staying in Computer Science.” I have said more than once, in a tongue-in-cheek way, that Code-n-Splode‘s mantra for men who think that we should not have the “dude token” policy should be: “It’s just not about you.”

My feeling is that establishing a culture where female voices dominate, rather than are assimilated in, creates a social environment that’s fundamentally different. And that that difference is *good*. I wouldn’t say that the book totally supports that notion, but it points out situations where women found peer groups that did not conform to a male hacker stereotype, and that foundation of social support helped them stay in their course of study.

The students referred to in the paragraph are undergraduates at Carnegie Mellon University:

Women who accept the prevailing culture as the norm and who continuously compare themselves to this norm and find themselves coming up short are the ones who suffer the most.

The majority of women struggle to find a place where they can feel comfortable in the prevailing culture…

Ironically, it is in this area of relationship to culture that international women may have an edge. The international women do not as readily use the U.S. male hacker as their reference group. Since they are not fully part of this culture, their reference group is elsewhere. Many international students have alternative success norms and social bonds that protect them. Other priorities are dominant, and with these come other scales for self-evaluation.

So, rather than bringing their cultural norms to the hacker culture and modifying it, the international women have their own social structures which exist outside of the dominant culture. “Cultural resistance” was the title for this section, and it’s a great way of characterizing the lack of assimilation.

I have more than a few times heard women-specific groups discouraged because of they emphasize differences that the dominant culture feels should be unimportant. I’m interested in further research that discusses the effects of splinter groups, particularly when they are created for women.

The second interesting topic in this chapter concerned learning communities.

Former University of California calculus professor Uri Treisman (1992) believes that a supportive learning community is critically important for the success of minority students in math and science.

The story went on to describe Professor Treisman’s observation that Asian students tended to socialize *and* study in supportive groups, which tended to help students stick with the courses and get better grades. He established similar groups for Hispanic and African American students, and found across several universities and colleges that these groups helped retention. Our observations and the resulting user group for women mirrors that Professor’s experience.

There’s a special connection created when you live and engage with material in a supportive learning community. They take time to create, and are a bit harder to maintain outside of an academic context (where life, work and diverging interests can be a bit more challenging to coordinate).

Code-n-splode has been fairly quiet about its successes, but I think now is the time for us to start talking a bit more about how well the group has succeeded.

Photo courtesy of DrPantzo under a Creative Commons License.

Why you should go to LCA 2011

capsicum

I returned from LCA 2010 on Sunday with an ecstatic grin, and tons of projects to work on for the rest of the year. I was lucky enough to have End Point send me to New Zealand! I knew a few of the organizers, and had high expectations. LCA totally surpassed them all.

Next year, LCA will be held in Brisbane, Australia. You should really go.

I’ll break it down for you:

* Content

The talks were really good. People went out of their way to talk about the technical issues they are facing without sugar coating it, dumbing it down, or resorting to lists of features.

Ted Ts’o‘s talk on EXT4 development was amazing in this regard. I came thinking that he’d give a laundry list of features, how it differed from EXT3, when he thought they’d be “production ready”. What I got instead was an incredibly detailed accounting of the failures in testing and systems analysis that filesystems developers had encountered over many, many years. The new development effort had its own fair share of bug creation, but they also found long standing bugs in EXT3. He went so far as to break down effort in terms of new feature creation, bug fixing and two other tasks (i wish I had a copy of the slides already!). Anyway, interesting talk, great advice for those who work with concurrency-sensitive applications (most of us these days) and very interesting case studies in failure.

Paul Gunn, an engineer at Weta Digital, gave a detailed talk on his experiences scaling their data centers. Much of the lessons there were fairly well understood by data center engineers (hot/cold aisles, raise the temperature to save some dollars!, don’t cram stuff under the floor where air is supposed to flow!, use high ceilings to sink heat). It’s always great to see companies sharing their practical experiences with developers.

Another fun project I learned about was Sheepdog – an EBS replacement developed by a team from NTT. The whole project looked fantastic – providing snapshot, cloning and thin provisioning, and a reasonable looking GUI. This could be a fundamental building block of free clouds.

I also was inspired by Cucumber-nagios, a relatively new project from Lindsay Holmwood. He and others have been talking about “behavior driven infrastructure“, a great bit of syntactic sugar on systems automation work that started with cfengine in the early ’90s. I look forward to playing around with these tools. And I really like that he leveraged nagios’ existing interfaces rather than inventing something new. This type of collaboration between projects is a breath of fresh air for sysadmins, who (if they’re anything like me) struggle to make awesome new tools talk to the awesome old ones.

I spent some time in an Arduino intro class, soldering and hacking on a temperature probe for a few hours. I ended up with a working temperature monitor and an appreciation for how easy to use the tools are.

* Hallway Track

There was a fantastic common area filled with people hacking on their talks, having conversation or maybe just hanging out to see what would happen next. IRC was full of hilarious chatter, and people connecting to see new babies (my god, so many people have had babies!).

There were also some couches, and a nice courtyard that often filled up with people. The common spaces in a conference seem to determine how well people can connect once they’re not just sitting in front of a speaker.

Another convenient and wonderful aspect of the location was the food. Excellent restaurants at reasonable prices were within a 5 minute walk of the conference venue. This made impromptu coffee breaks and relaxed but productive lunches very easy and enjoyable. I really, really liked this.

* Inspiration

Three keynotes by Biella Coleman, Benjamin Mako Hill and Glyn Moody were inspirational and subversive. All three were rallying cries for a hacker mentality – the drive to tweak, tinker, create and share. All three spoke to the pleasures and joys of software development.

Biella Coleman brought up the origins of the Free Software Foundation, and even played a video of a very young Richard Stallman talking about his frustration with not being able to modify source code. She also discussed the responsibility leaders in free and open source have to be transparent in their management of their projects (and how we remind ourselves of that in amusing ways).

Benjamin Mako Hill gave a rallying talk about antifeatures, and how their existence is a competitive advantage for free and open source software. Pia Waugh gave a detailed description of the talk, and the categories of antifeatures – protection money, market segmentation, securing monopolies and protecting copyrights. A memorable quote was “I have yet to meet a free software DVD player that respects the unskippable DVD track.” Mako reminds me that humor is the best medicine for something that’s seriously broken.

Glyn Moody went a slightly different route – talking about how sharing and openness are leaking out into the rest of the world. The Human Genome Project and Project Gutenburg were two of several examples he used, and to briefly cast a glance at what was at stake if public ownership had not been achieved – in particular with the Human Genome Project. He managed to convey a sense of urgency and importance that is often missing.

What free software actually gets used for and why are critically important stories. We all need to get better at telling compelling stories.

* Friendship

Free software is built on friendships. Trust, willingness to make mistakes in front of each other, and a desire to build on top of others work to make something better are the traits I see among those who collaborate with each other. Building free software can be a painful process – long nights, tedious bugs, no recognition for the work that went into it all. Conferences like LCA are a tremendous affirmation of the work that we all do.

From the scripted get-togethers, to the spontaneous hackfests and anti-scripted gatherings (the un-professional networking session!), all events are attempts to connect to the other people who know what it’s like to live inside of free software. And we relax around each other, make jokes and enjoy for a few days the knowledge that we’re doing something really cool.

I met so many people for whose time and attention I am incredibly grateful for. And, for those Kiwis who took me out for great food, shopping and long walks along the pier in the sunshine — thank you so much for taking the time. I miss you all.

OpenSQLCamp was awesome!

Saturday schedule 11/14/09

Thanks to everyone who attended OpenSQLCamp this past weekend in Portland, OR! More than 100 people participated – developers, DBAs and hobbyists from all over the world. Database developers participated from PostgreSQL, MySQL, MariaDB, Drizzle, TokuDB, LucidDB, MongoDB, Cassandra, CouchDB and many more.

The great thing about these events is the opportunity to trade ideas, code and stories. One project I’m very excited about is coming from some Portland State University students and a capstone project to create a new, interactive database client that works with more than just one DBMS. Igal gave a review of non-relational datastores. We had lightning talks about: open source column store databases, a many-master replication system called Trainwreck, open source at Microsoft, how to translate between NoSQL and SQL and many more.

You can see the full list of talks and notes from sessions as people update the wiki.

Joking about NoSQL aside, I was very happy to see many non-relational database developers in attendance, sharing information and participating in interesting discussions about the data management ecosystem. One meme we were happy to spread is that every tool has a purpose and I was happy to see this tweet:

Best thing I learned at #opensqlcamp today: #nosql vs. #sql is a false duality. Different features for different problem domains.

I hope next time we can get a few more core Postgres developers to a Camp. Mark Callaghan expressed interest in a comparison of backend storage mechanisms, and several people were interested in detailed comparisons of replication strategies across many DBMSes.

Thank you to everyone who participated! (sorry I spelled your name wrong in the email, Mark. And left off your name in the list of GoDaddy road-trippers, Dan.) If you were there, please give us feedback!

We’re already looking forward to the next OpenSQL Camp. Some people thought we should do it again in Portland – and we’d be happy to host again next year! Baron also mentioned running an event in Washington, D.C.