Doubting the Daubing Philosophy

Melissa Draper is a manager, a web geek, an Ubuntu contributor and Pad Thai addict. She was our first guest poster, and is now a recidivist offender.

As a woman involved with several projects that aim to encourage women (and other marginalised groups) to get involved in Open Source, I often come across the concept that nothing needs to actually change within our projects to achieve better gender balance, we just bait and blackmail as many women and girls as is humanly possible to try something such as Ubuntu. The philosophy behind this is that some of these women and girls will stay and conquer the gender divide to much rejoicing.

Basically; If you throw enough mud at the wall, some of it will stick.

To a tinkering community, this may sound logical; If you try enough at something, you’ll get some successes eventually. In fact, the philosophy is thought to be based around the wattle and daub method of construction.

I have an issue with applying this to the Women-as-a-minority issue. My apprehension with applying this philosophy to potential contributors is that humans have remarkable abilities that wet dirt does not. Humans are able to remember things. No elephants or knots of string required. Humans are also able to make decisions about what they do and prioritise good experiences above bad ones.

If I take 50 women and successfully encourage them to join a project because everyone is nice and they will feel like they are frolicking with bunnies, but they actually have a contradictory experience — then this is bad.

I cannot magically take away the bad experience that they had. I cannot turn back time and make the sexist joke or come-on go away. I cannot turn back time and make the negative stereotyping alienation non-existent.

Basic sales and customer service training will tell you (right after “keeping customers is cheaper than getting them” (pdf)) that it only takes one bad experience to turn a customer in to an ex-customer. If it is the first experience, then it is more or less permanent. First impressions really do count.

As an example, it took until this millennium to convince my mother to use garlic in her cooking. She got turned off the taste from eating pizza totally smothered in it at an Italian restaurant in the mid 70s. That single bad experience took 25 years to overcome.

So, back to our 50 women. Lets say that after this bad experience, of these 50 women, 1 stayed. I have then achieved a 2% hitrate.

(A note about customer satisfaction statistics: the “customer to ex-customer” conversion is typically in the order of 80-90%. The worse the bad experience, the higher the conversion. For the purposes of this article, I am using a commonly accepted ballpark figure of women in open source.)

The other 98%? I would not hold my breath waiting for them to come back for a second helping. Once burned, twice shy, as they say. Actively try to lure them back, you say? Good luck. In the real world, you probably don’t even know that (or why) they’ve gone.

Ironically, had I been honest with these women from the start, then it would likely have been different. Had I said that it can be a challenge; that bad things can happen, and why it is a challenge; but that there’s a support base they can fall back on, then I’d not have been ‘tricking’ them. I would not be misrepresenting the project, and they’d not be buying in to it expecting a utopia. I’d not be breaching their trust.

If I can illustrate how the available social support bases and safe spaces such as (<project>_women, <industry>chix for example) have been used in situations in the past, then I’m giving them the power of knowledge to be prepared for reacting to a bad experience. It will ensure that they know what to do, who they can turn to and so forth. It will ensure that they are many times less likely to feel like they’re the only person ever made to feel alien within the project community.

The bad experience would be put down to the challenge they were warned about. The warning made it expected enough that the response to the experience would be much less likely to be the reflexive fleeing. The overall level of hurt after support from the group they were told about would be many times less.

We don’t want to only ever achieve a 2% hit rate. We cannot afford to. If we are to get half of the world’s computer users to use a non-proprietary operating system as is the desire behind things such as Ubuntu’s Bug #1 then we cannot afford to scare away 98% of the women and girls (you know, half of the world’s human population) who are exposed to the alternative. Doing so means we need to achieve a conversion rate of 98% of the male half of the population.

To achieve a useful sticking rate, then we are going to need to do something other than throwing every woman and girl we come across in the general direction of the nearest project in the hope she does not get repelled for the next 25 years by the experience.

Looking for opportunities for change within your project is a pretty good start.

Invisibility or the spotlight?

Our first actual guest post! Melissa Draper may well have been the first woman on the planet, well, Planet Ubuntu. She is a web developer by trade, and has more F/LOSS hats than she cares to admit. Her regular blog can be found at geekosophical.net.

These days, most girls and women in westernised societies get to choose her own destiny, and there is little doubt that this is a far cry from the world of only half a century ago.

As a broad and sweeping generalisation, people these days are not dictated in to or out of certain careers based on the number of X chromosomes their DNA profiles have. In sufficiently balanced legal systems there are even laws to provide justice for when certain interpretations of sexual discrimination occurs.

One could easily be led to believe that this taboo on sexual discrimination eliminates all obstacles.

With this perceived fair playing field, we often find ourselves asking how we can get girls and women to choose to be involved in fields which are perceived as “historically male-dominated”. One field that this question is often asked of, is that of software development.

Sadly, we are asking the wrong question.

We are failing to recognise that historically, computer languages and software development were female-dominated.

Asking this question, in this manner, inadvertently highlights one of the obstacles which girls and women still face in spite of the applauded taboo on sexual discrimination. It highlights that many of the potential role models for girls and women today, the women pioneers of computing history, are invisible.

Invisibility does not limit itself to history either. The founder of the Free Software movement, Richard Stallman, has previously failed to identify women that have played important roles in the GCC project.

This feminine invisibility (including the “honorary guy” culture) is hurting our budding female software developers. It is robbing them of their inspiration, and creating an atmosphere in which they feel even more like an anomaly than they deserve to.

Because these women of computing past are invisible, the women of modern computing are often put in the spotlight in an attempt to fill the motivational void. Women in software development do not become ‘just a software developer’ like the male super-majority do, they become software developers who must carry the extra burden that being a role model brings, simply because they are so rare.

This spotlight is not always a flattering one. It can draw additional attention, and opens women up to a level of scrutiny that men are generally not subject to.

Being in this spotlight is akin to walking into a saloon in the old west and having every eye turn to watch you. It is like having someone watch over your shoulder as you type. In some cases, especially for women of low self-esteem, it can be as intimidating as having someone follow you into the bathroom to watch you pee. It is an extra pressure, it is an extra stress, and for some women, it is too much.

Women in software development can choose to avoid the spotlight, and many do. Women can avoid the spotlight by assuming a neutral or male identity. Women can avoid the spotlight by telecommuting or avoiding face-to-face events such as LUG meetings where their femininity will be obvious.

Women can avoid the spotlight, by not being women.

Women can choose to be a women and a role model to the girls and women who will follow in their footsteps — at the risk of extra pressures. Alternatively, they can choose to lose part of their identity and the ability to claim credit for what they achieve.

For women, it is not as simple as choosing to develop software, or deciding to be interested in software development. Women must also choose how they will be represented.

Or, they can just not bother.