In anticipation of a December/January slowdown, I’m reposting some of my writing from earlier in 2010, for the benefit of new (and nostalgic!) readers. This piece originally appeared on the 9th April 2010.
Code Anthem’s Donâ€™t Judge a Developer by Open Source (via Meg in the Open Thread) argues that companies that rely on Open Source coding contributions as a hiring criterion are both demanding a lot of their hiree’s free time and are sexist:
Open source is a culture. There are plenty of smart and passionate developers out there who are not part of that culture. And certainly there are plenty of dumb and curmudgeonly developers out there participating in open source…. There are there smarter ways to spend your time. The stereotypical open source developer works for a bumbling corporate during the day, doing dull work (but necessary to make money) and then comes home to work on his passion, OpenOKHRWUJ Framework…
Requiring open source contributions is sexist… Open source is dominated by men even more so than the programming community as a whole… itâ€™s irresponsible to require your new hire developers to come from a male-oriented pool. Alasâ€¦ â€œUnderrepresentation breeds underrepresentationâ€.
I have a comment in moderation there in which I say that I think the stereotype is incorrect: that Open Source developers in my experience are either university students or other young people with a lot of free time, or they’re paid Open Source developers. (I know hobbyist Open Source coders with unrelated dev or other full-time jobs too, yes, but not nearly so many and their contributions are for obvious reasons usually not as significant. If nothing else, this group has a really high incidence of typing injuries.)
But that’s a side-note: I think the core point of the post stands. Open Source is very male-dominated, is known for being unpleasantly sexist, and is also a subculture whose norms (even where neutral as regards sexism) don’t fit everyone. Requiring these norms feeds right into the problem talked about in Being Inclusive vs Not Being Exclusive:
People who come from underprivileged minorities are usually very experienced in the art of being excluded. Sometimes it’s overt – “we don’t like your kind” – but many times it’s subtle. They’re told that they’re “not quite right”, or they “don’t have the right look”, or “don’t have the right experience”, or just aren’t told anything. At the same time, they are surrounded by all sorts of imagery and communique about how they don’t quite belong, about how they have to change themselves to fit in, about how they are undesirable. They do not see a lot of examples they can relate to; even the ones that come close tend to stick out for being “Exotic”, being a token. They already have a lot of barriers against them and are already of the mind that they’ll more likely be rejected than accepted.
If you insist on a lot of experience in a particular male-dominated sub-culture as a prerequisite for a job, that reads as “we prefer [a subset of] men, basically, or at least people willing to work hard to minimise all the ways in which they aren’t [part of the subset of] men” even if you didn’t intend it to and even if you didn’t want it to.
Code Anthem isn’t, as far as I can tell, thinking about Open Source paid jobs in that post, but they of course have this problem magnified. It seems vastly reasonable on the face of it: hiring existing Open Source contributors, ideally people from your very own community, means you hire people who are well-versed in the particular mode of development you do, in particular, the use of text-based mediums for communicating among a distributed team. Since Open Source (or more to the point Free Software) projects are at least sometimes associated with particular non-commercial goals and philosophies agreement with those seems desirable. But since most long-term Open Source developers need to be paid for it, it strongly feeds into this cycle of long-term Open Source developers continuing to be male and of a particular kind of culture, and continuing to overtly or subtly signal that that’s who is welcome in Open Source development.
Possible other posts of interest:
- Terri’s Want more women in open source? Try paying them.
- Dorothea Salo’s Sexism and group formation:
A woman can be an honorary guy, sure, with all the perquisites and privileges pertaining to that statusâ€”as long as she never lets anything disturb the guy faÃ§ade.
Itâ€™s good to be an honorary guy, donâ€™t get me wrong. Guys are fun to be around. Guys know stuff. Guys help out other guys. Guys trust other guys. And in my experience, they donâ€™t treat honorary guys any differently from how they treat regular guys. Itâ€™s really great to be an honorary guy.
The only problem is that part of the way that guys distinguish themselves from not-guys is by contrasting themselves with women.