Dyepot, Teapot

Entries categorized as ‘diversity’

Women in Technology: the book

September 28, 2007 · 1 Comment

We must be at the end of September, because today the last essays in O’Reilly’s Women in Technology series were posted. Mine was earlier in the week, found here if you missed it. Some very interesting perspectives were included. One big thing I noticed is that most women seemed to attribute their success to doing what they were interested in, whether or not anyone else thought they should. But the same people also benefited greatly from being around people who did support them. Maybe we need to keep talking about women’s participation in technology as both an individual effort and a group one.

If you’re interested in further supporting the goals of this series, or just having the whole collection in one handy package, a print edition will be available starting in mid-October, but you can pre-order now. All proceeds will be donated to the Alliance of Technology & Women scholarship fund.

Much thanks to Tatiana Apandi for being the organizer and editor of this project.

Categories: book · diversity · essays · o'reilly · technology · women · women in technology

You can’t wait a generation for change

May 22, 2007 · No Comments

One of the kinds of comments I keep running into goes like this: “The reason women aren’t in technology in large numbers is that they don’t have enough encouragement early on. If we help them get interested in grade school and high school, eventually we’ll have gender parity in the working world.” And on top of that, any other attempts to encourage diversity among existing adults get the blanket label of affirmative-action quota programs (even if all that’s been suggested is to find a way to acknowledge the presence of women in your field in a manner that does not make them feel like the subject of a scavenger hunt).

The problem with this is that it completely neglects the people who have the skills and the interest to be working in this field, but have chosen to do something else (even a support or management role rather than programming) because they don’t feel welcome. Encouraging young girls to play with computers is not going to fix the lack of an inclusive professional environment to move into. And I think the declining diversity that occurs as we go through the educational and career process is a strong indication that this particular problem exists. Do you really want to encourage more women to enroll in first-year CS classes just so even more of us can leave?

This doesn’t mean that I’m not in favor of technology initiatives for all children. I mostly talk about gender because I’m a white female and this is what I know, but I really am interested in more diversity in all directions. I actually think that everyone should know at least a little about how to program, create web pages, etc. This is an important kind of literacy in the modern world. Except that’s a different problem than what it’s like to work in the tech industry right now.

I also don’t think we should equate technological literacy with who graduates from CS programs, but I hope I covered that enough in the previous post.

Categories: diversity · gender · technology

Indirect routes

May 21, 2007 · 1 Comment

I keep thinking that I’ve already spit out everything I can think of on this topic, but a comment I saw on Tim Bray’s blog reminded me of something else. There’s a lot of focus on a particular route to working with technology, running from early childhood computer use, to high school programming classes or college CS studies, then finally getting a real world job in the field. It’s the formal path for this, right? So then when we talk about how to get minorities actively contributing in the world o’ tech, we focus on smoothing that specific route. But in reality, a lot of us actually studied or worked in other fields at some point, and came to technology from elsewhere. In my case, I learned BASIC in grade school, played with computers tons all the way up, but didn’t take a single computer class in high school, and in college I majored in geography instead. The particular kind of technology work I do now mostly involves things I didn’t pursue until I was away from formal education systems.

I’ve heard similar stories from a lot of other people, too. Many real live computer programmers have a background in something other than CS. And that’s wonderful. I think it’s much easier to learn computer skills on the side than to get an in-depth look at many other fields that way, and a background in something else can give you so much material for what questions technology is needed to solve. So when we’re thinking about how to increase the diversity of who works in technology fields, it’s really important not to neglect the indirect routes. Many modern jobs involve computers in some way. We need to think about how to help people become not just passive consumers of technology, but active contributors. Even if all they do is write their own web page or a small script. Even customization of existing tools or just a good understanding of how they work is part of this.

Not everyone will want to get into the nitty gritty details with tech, and that’s okay too. I wrote a post after Recent Changes Camp about how organizations can recognize and support involvement at many different levels. But while there are many great reasons to reach out to as diverse a pool of kids and students as possible, to facilitate their future involvement, I don’t want to forget the adults who are already out there using these technologies on a daily basis, who may just need a nudge in the right direction to take a more active role.

And maybe we should also be talking about expanding our definition of who counts as a technology worker in the first place. Shouldn’t this include anyone who creates or modifies tech for their own needs, whether or not they’re working under the umbrella of IT or programming at the time? Not to make the numbers and diversity ratios look better, but to reach out to people who may not realize there’s any kind of community or resources connected to those activities.

More to think about.

Categories: computers · diversity · technology · work

More thoughts on diversity in open source

May 21, 2007 · 4 Comments

Aside from the issue of community friendliness/hostility, there’s another set of structural reasons that affect who finds it easy to get involved in open source. At both BarCampPortland and RailsConf, I tried to pick people’s brains about why there are even fewer women involved with Ruby and Rails than with Java or Perl. I’ve also been poking around discussions on this online.

Many local tech events aren’t appealing or accessible to a wide range of people. By local I mean things you attend in your hometown, rather than conferences we travel to. A lot of these are most suited to people who are young, don’t have kids, and like to drink beer. That describes me. It does not describe my mother. Sometimes an event just needs to be publicized more widely, but often there are people who might be interested in the technology, but can’t go to a Tuesday night user group because there’s no one to watch the kids, or don’t have an interest in going because they anticipate a room full of socially-delayed young men. So if we want to build active, diverse tech communities, we need to create the means for a wider range of people to participate.

Not everyone can spend time learning new technologies when there isn’t support or compensation from their employer. It’s a pragmatic choice. If you can’t use it at work, why learn it? Especially if you have interests outside of IT, or family commitments and other obligations. Enterprise adoption of new tools and languages helps the diversity of the user base. Yes, there may be compelling reasons to learn new things even outside of work, particularly in the midst of outsourcing, but it’s not always possible to find the time, or scrape up money for books, workshops, etc. I think JRuby could be highly beneficial to the Ruby community in this respect, by allowing teams to deploy Ruby and Rails apps on top of their company’s existing Java setup. The attention from BusinessWeek and similar publications helps too. Unfortunately, many workers have to deal with IT decisions made by people who only read business & management publications, and have no personal involvement with any particular technology.

These things I’ve posted are really just a start, but I think we really need to get past arguing over whether lack of diversity is a problem (yes, it definitely is) and looking for the one true solution (let’s try some likely options and talk about the results), and actually get into action.

Categories: diversity · open source · technology

A few last thoughts on RailsConf

May 20, 2007 · 6 Comments

On the whole, my experience going out and talking to people from the conference was really positive. The Hackety Hack BoF was neat, and I’m looking forward to the Macintosh release so I can demo it for PDX.rb. I also think it’s awesome how many people are just using Rails to get things done, in this growing ecosystem of small Rails development shops. And initial reports on plans for the 2.0 release sound good. I like working with the RESTful resource system, so it’s great that they’re continuing in that direction.

However.

As the Rails community continues to grow, there is a lot of work to be done in order to keep this a useful, accessible, and relevant platform for development, and not all of that work is technical.

This really summarizes what’s wrong with the backchannel conversations that took place this weekend:

[12:06pm] Nevin: I hope the speakers don’t ever see the transscript of this chat
[12:06pm] Nevin: that would be awful

When people are spending the conference heckling speakers and playing ’spot the hot chick in row 2!!!’, that’s a serious problem. You can’t have a healthy open source community in that kind of environment. I don’t care if no one is saying these things out loud or to our faces, that people are willing to say it in the semi-anonymous environment of IRC and few call them on it is something the community has to address.

There’s a key rule at open space events like BarCamp, called the Law of Two Feet. If you aren’t getting any value from the presentation or discussion you’re in, then you need to go elsewhere and find something that is of more interest. And if there’s nothing on the schedule, you find other people in the halls and you get something started yourself. Commercial conferences like RailsConf are focused on the planned programming, but this is still an excellent rule to apply. If the speaker is boring you to death, if it’s not a topic you’re interested in, don’t sit there and complain about it behind their back. Get up and go elsewhere. It’s your responsibility to find or create the things that will make the event worthwhile.

One of the things that seemed to trigger at least some of the complaints was content at a lower skill level (or higher-level summary) than the attendees expected. O’Reilly could do a lot to help participants find the content they want, by asking speakers to grade the target level for their talk, then including that information in the schedule. That might also encourage the development of specific beginner, intermediate, and advanced level tracks for the event (which are also really important to helping people not just start working with Rails, but actually become advanced users or contributors over time).

I think it’s great that people who work with technology enjoy it so much that they build friendships and communities around it. This is actually a large part of why I stick around even though I have complaints. But the downside is that it can create a cliquish environment that’s actively hostile to outsiders, particularly women and other minorities. There are some specific things that need to be addressed if Rails wants to really kick ass in the long run:
* Make it easy to get started. That means beginner tutorials (we’re actually doing really well on this one), in addition to friendly resources for asking questions (mailing lists, IRC channels, user groups).
* Have clear expectations for community members. This includes documentation on how to report a bug, how to submit a patch, etc. but also how we expect people to behave toward each other. If hostile behavior is treated as a joke, or harmless, or all in good fun, that’s a clear sign that this has not been addressed.
* Value the contributions of all participants. Being a Rails core contributor is not the only important role here. We need people doing documentation. We need active collaboration with designers. We need support resources like people who answer beginner questions on #rubyonrails. And we need users. Who cares about a web development framework that doesn’t have users?

I want to get people talking about these things, because I think Rails is an amazing tool, and we’re still early in its development. There is a huge opportunity here to make it something that fully lives up to the promise of open source.

Categories: community · diversity · rails · railsconf · railsconf07 · technology

RailsConf notes so far

May 19, 2007 · 7 Comments

I’d read complaints before about the meanness of commenters on the irc backchannel at conferences, but this is the first time I’ve really experienced it for myself. Right now the mob is tearing into Cyndi Mitchell’s keynote on Enterprise Ruby. They’re making cracks about her being the Rachel Ray of code. I’m wondering, if they think it sucks so much, why is everyone still in there? Yesterday it certainly sounded like there was at least one mass exodus from a presentation that was putting the crowd to sleep.

I think O’Reilly should really look at options for moderating the backchannel. Aren’t they supposed to be interested in healthy communities?

Last night, Desi coordinated a Thoughtworks-sponsored party at Rock Bottom Brewery. She’s been a huge help in going around and introducing the female attendees to each other. I had a great time wandering around and talking to people. Tonight the same thing will be happening again, this time sponsored by Pivotal Labs. There’s also a Hackety Hack & User Groups BoF tonight that will be open to the public, and RejectConf at FreeGeek (though now that I’m reading about the “Gong Show” format, I’m actually not that interested in seeing this).

I have a lot of concerns about elitism and cliquishness in the Ruby and Rails communities. But talking to people last night, I felt reassured that there are a lot of people who really only care about what they’re able to do with this technology, and aren’t part of some kind of social game. That was good.

On the other hand, #railsconf makes me think the worst again:

[09:23am] lectrick: if we wanted women we would have become nurses [actual name: Peter Marreck]
[09:23am] deadprogrammer: mars need women [Ron Evans]
[09:23am] NetNeutrality: lack of women is not rails specific, all software eng is like that [unknown]

Someone set up a RubyChicks site. I’m not really sure what to make of this. But hey, photographic evidence that we exist. I’m in picture #16 [edit: the site owner seems to be taking pictures down as they're added. Not sure why that and not disabling uploads as well].

Categories: diversity · rails · railsconf · railsconf07 · women

Rebuilding the architecture of the space

March 1, 2007 · No Comments

Anne had a thought-provoking post Wednesday about her experiences at Adobe Engage, which is a show-and-tell event where Adobe demos interesting things they’re working on. She relayed a quote from one of the VPs there, about needing to “fight against the architecture of the space” because the event was held in a formal lecture-style room, instead of one where the participants face each other and are able to interact more easily.

Then Anne says, “As the only non-Adobe woman in attendance, I felt like I was fighting against two architectures: the physical space, arranged auditorium style, and the social space, a monoculture of mainly white and Asian men.”

I like this way of describing things. It appeals to my inner geographer. Blogging is a space. The tech industry is a space. They are structures with particular characteristics. And like I was saying in my last post, once you know how something is put together, you can start looking for the place to push to enact change.

(As an aside, my attempts to analyze the structure of things sometimes get away from me. This morning I decided that work reminds me of playing in a Camarilla LARP in college. If anyone from work is reading this and thinking “WTF?” ask me and I’ll try to explain. I can’t say that it’s useful information, though, just really funny inside my own head.)

Anyhow, to get back to the topic, Anne also says, “The world of technology blogging is an architecture of non-participation for women.” As in, the way people gain prestige and attention (and income) through blogging seems to be constructed in a way that tends to work against how women (often) do things.

I’m not going to argue nature vs. nurture on the gender and technology issue, because I think it’s a stupid argument and completely pointless. I don’t have any issue with the idea that I experience the world differently than Robert Scoble, and for all sorts of reasons. (No link. Google it if you don’t know who he is.)

I’m also willing to accept the idea that women tend to blog differently than men (we post less often. We’re less willing to post unless we feel we have something new to add to the conversation. I saw something today about similar gender differences in the publication of academic articles). And if we experience the world differently (in general, on average, etc) it makes sense that we encounter technology from a different angle too. I like to code because I like to build things, but I wouldn’t write code unless I cared about the end result. I think maybe this is what Kathy Sierra is trying to explain when she talks about her daughter and peers, about wanting to play with the product, not be stuck working on the low-level machinery.

Then, if we agree this far: it’s not a leap to say that environments that foster only one way of engaging with technology have a negative impact on diversity. I experience this, I believe it. And I don’t think we need to work with the architecture of the space, I think we need to rebuild it. Maybe not the whole thing all at once. But I’m looking at my own projects, and trying to find clues to what an inclusive architecture looks like. Does everything associated with blogging have to be built like a search engine, complete with page rank? After spending the last several weeks on magazine layout, I’m starting to wonder why everyone’s in such a hurry to ditch print–there’s a lot you can do with the publication as a whole product that’s diminished when you break it up into searchable text online. I’m involved with several local user groups, and I think there’s a lot of opportunity there. I’m sure I could come up with a whole list if I were more awake.

Maybe it’s enough of a starting point just to say “environments without diversity are toxic. What can we build that works differently?” But I’ve been poking at this long enough that I don’t want to just ‘work with’ the space. I want to create something else.

Back to Anne one more time: “I do want to work within this space of blogging and technology and influence. I don’t want to fight against it and be labeled shrill or out of touch or difficult.” This is perfectly reasonable. I think it’s stupid beyond belief that it can reduce one’s opportunities and access to say ‘hey, I’m having an unpleasant experience over here’, but that’s not her fault, and I’ve encountered it plenty myself (not just on the gender issue). What I’m trying to say is that working on a zine has started me thinking about how to carve out my own space. Could I build my own little area of change?

Categories: blogging · diversity · feminism · geography · spaces · technology · things I write while half-asleep · women · yes I'm being an idealist but there's nothing wrong wit

Recent Changes Camp

February 3, 2007 · 5 Comments

I spent yesterday and part of today at Recent Changes Camp, which is an unconference about wikis.
Part of how an unconference works is that the participants are encouraged to bring topics they’d like to present on or discuss. So when it came time to put topics on the schedule, I did two: “Building Diverse Communities”, which I combined with Dawn Foster’s community building discussion, and a photography thing that didn’t attract any participants (oh well).Some really interesting thoughts on communities, openness, and access came up in the session with Dawn. One was the idea of having a formal process to guide newcomers, either by assigning community greeters, building an intro tutorial to walk people through the basic steps needed to participate (Second Life was given as an example here), or creating some other process to welcome people and help them get involved.

We talked a bit about hooks, about entry-level activities that get people interested or demonstrate that this is something individuals can become a part of. Afterward, I started thinking about how to recognize participation a multi-level process.

Here’s an example:

Organization Free Geek Personal Telco OPB Linux (or other open source project Wikipedia
Level One donating old computer equipment accessing a wifi node listening to a radio program using Linux on a computer anonymously editing a spelling error on a page
Level Two volunteering to sort recyclable donations installing a wifi access point at home or work donating during the pledge drive reporting a bug adding content as a registered user
Level Three building computers for others helping maintain the network and access points volunteering to answer phones during a pledge drive contributing a patch helping moderate discussions about content and editing

…and so on.

The table format suggests that it’s a linear process, but there could easily be all sorts of activities at each level. What I like is that it recognizes that even casual participants are still part of the community, and that not everyone will want to be on the leadership committee or learn to program for the Linux kernel. These different levels of involvement are natural and healthy.

If a community wants to continue to grow or even just stay alive, it needs to have opportunities for a variety of people to get involved. How broad of a group you want to target will depend on the community or project, but I don’t think you can succeed in the long run without some diversity, and the ability to accommodate individual time commitments and levels of interest.

I think the discussion tapped into a lot of things people were already thinking about, because we went at least half an hour beyond our scheduled time slot. There were many other interesting ideas from the participants, and you can find detailed notes on the RCC wiki.

Categories: access · communities · diversity · open culture · openness · rcc2007 · recent changes camp

Gray + Rainy = Fall

October 7, 2006 · No Comments

Yesterday was overcast, misty, and the sort of day when I miss Seattle. In Seattle, the weather remains exactly like that from November-March, never too cold, rarely sunny or dry. I love it. But I’m also missing Seattle because that’s where I went to college, and right now I’d love to return to that kind of atmosphere. I don’t think anyone realizes until afterward just how lucky they are to get 4+ years of reading and learning with few responsibilities and the ability to follow odd ideas for hours on end without having to earn money at the same time. It’s worth every cent of the debt that results, but that’s also why you don’t get to go back. Too expensive to do twice, unless it’s grad school and you’ve come to terms with the idea of paying off student loans until you’re 80.

Paul Graham is a well known writer and speaker on the subject of tech startups, and he frequently encourages college students and recent grads to consider starting their own instead of going to work for someone else. I like a lot of what he has to say about the general topic, but the “students of America, you don’t need a corporate job” parts get under my skin after a while, because I feel like he’s only talking to privileged MIT or Stanford kids who can ask their parents to bail them out if it turns out they’re about to be evicted because they’ve been writing code for their own business idea without a paycheck.

I didn’t have steady work for a year after I graduated from college, and it was a miserable experience. I did freelance work during that time, but always with the expectation that I was looking for a full time job, because I didn’t have enough money in the bank to handle any kind of emergency or unexpected situation. So I don’t see how anyone can possibly go straight from college to their own startup without a nice little graduation present of enough cash to not worry about food or rent for 6-12 months. It’s difficult to focus on anything when you’re trying to decide if you’re desperate enough to apply for food stamps.

Thus, we come back to the job market. I think most companies do a lousy job of seeking out qualified people [1], but we’ve been over that topic. So I’ll just point out a change to the 37Signals job board: they’re raising the cost of listing a job so they’ll have fewer listings. The comments on this announcement are mostly a big lovefest, with only a few of us wondering how this is good for the job seeker.

Clearly price does not ensure quality in this setting. And because this is a national job board, limiting the number of postings really hurts anyone who isn’t in NYC, SF, or maybe Boston. There’s no reason other cities can’t have interesting tech businesses, except for the difficulty of connecting people with companies that want them. But this was supposed to get easier, thanks to the wonders of modern communications technology, and I think limiting the number of job posts on this board is a step in the wrong direction.

I know there’s a certain crowd that says “traditional hiring is dead!” and “word of mouth/personal contact is everything!”. This is great in a lot of ways, because the best way to find out someone’s true skills and ability is to work with them or talk to people who have. But I think it can also reinforce certain biases and kinds of discrimination. Open source projects are often suggested as a great way to demonstrate coding skill and ability to work with a group, but far fewer women than men participate in these, for reasons that have been actively discussed elsewhere (this might be a good place to start if you’re new to the discussion). And other kinds of groups that one might use for networking face similar problems.

At Lucky Lab after the last Portland Ruby meeting, I was sitting across the table from a guy who had recently moved from elsewhere. He mentioned that there was a Rails development group in his previous town, but no women attended regularly. One showed up for a single meeting and didn’t return.

Everyone has heard jokes about how the guy who plays golf with the boss gets promoted over a more qualified worker who isn’t in on those outings. Kissing up to the boss aside, there’s some truth in the joke–of course you’re going to receive more consideration from people who have spent time with you. Personal connections are really important.

When groups that might provide opportunities to meet other people in your field are very homogeneous, that can shut a lot of people out of the benefits of those interactions. I know from experience that it can be very intimidating and awkward to be the only woman in a room full of men, especially if they already know each other. This is a problem even in a friendly, welcoming group. There is a lot of cultural baggage that affects how women and men talk to each other, and settings that are somewhere between professional and social can make that even more difficult.

My point here is that you can’t assume that social networks will bring you a wide pool of qualified people. They might, they might not. But an employer (or really any kind of organization) that wants a diverse representation of talent in their field may have to dig a little more. This is getting a lot of attention right now with respect to how conference attendees are selected. I’ll refer you to other people for more on that one.

[1] Not that this is an easy thing to get right. I did the hiring for my group at my last job, and the number of people who apply with terrible resumes and no relevant skills is amazing. But the way most job ads are written, it’s no wonder a lot of people give up and apply at random. My current job was a complete mystery based on their ad on Craigslist. I only applied because it sounded vaguely like something I could do, and I already knew someone who worked there.

Tags: , , , ,

Categories: business · discrimination · diversity · jobs · startups