Remembering a geek feminist ally: David Notkin, 1955-2013

Featured

This is a guest post by Debbie Notkin, who is the chair of the James Tiptree, Jr. Award motherboard, a co-organizer of WisCon, and a science fiction and fantasy editor and reviewer. She is also the writer (with Laurie Toby Edison) of Women En Large: Images of Fat Nudes and (with Laurie Toby Edison and Richard F. Dutcher) of Familiar Men: A Book of Nudes. She blogs at Body Impolitic and on Dreamwidth.

No marginalized group can move forward without allies, and all of us have the opportunity to be allies as well as need allies. So it behooves us to look at what high-integrity, committed ally work looks like. And that’s why I want to tell you about my brother.

When David Notkin’s son Akiva was about two years old, he was fascinated by all games played with balls. (At 15, he still is.) We were on a family vacation together when David and I walked with the toddler past a ping-pong table, and Akiva instantly wanted to see what was up. I asked David why he thought Akiva was so much more interested in balls and ball games than his older sister Emma. David said, “I don’t know. We treated them exactly the same; it must just be something about him.” Having heard this from dozens of parents over the years, and rarely finding a productive response, I just let it go.

Years later, unprompted (if I recall correctly), David told me that he was no longer sure that was true. He had started to spend time with and pay attention to the serious feminists who advocate for more women in technology and the STEM fields, and he had done some listening and some reading. He said, “I think it’s perfectly possible that we responded to Akiva’s interest in balls differently than we would have if it had been Emma.” I had, and still have, very little experience with anyone changing their mind on these topics.

Melissa McEwen at Shakesville differentiates between what she calls the “Fixed State Ally Model” and the “Process Model,”

In the Process Model, the privileged person views hirself as someone engaged in ally work, but does not identify as an ally, rather viewing ally work as an ongoing process. Zie views being an ally as a fluid state, externally defined by individual members of the one or more marginalized populations on behalf zie leverages hir privilege.

The kind of shift that David made about his son’s interest in ball games is as good a step into the Process Model as any.

In this flash talk, given at the National Center for Women & Information Technology (NCWIT) Summit in Chicago in May of 2012, we see more commitment to process in ally work.

In this talk, David says nothing about what women want, how to bring women into the field, or really anything about anyone except David. Instead, he describes the reasons to take another step on an ally’s journey, and advocates a way for teachers and professors to take that step, by voluntarily stepping into a learning situation where they are in the minority. As he says in the opening frame, he’s in a room full of brilliant women. As he doesn’t say, he knows he has nothing to tell them about being female, or being female in the computer science world, or anything else about their lives. What he can share is his own efforts to understand what it’s like to be marginalized, without taking on the mantle of the marginalized.

The NCWIT talk came in a deceptively optimistic period for David; he had spent the end of 2010 and virtually all of 2011 in cancer treatment, and his scans were clean … until June. In February of 2013, a few months after David’s cancer had spread and he had been given a terminal diagnosis, his department held a celebration event for him. Notkinfest was a splendor of tie-dye, laughter, and professional and personal commemoration. I hadn’t really followed his trajectory as an ally and mentor to women and people of color, and I was amazed at how many of the speakers talked about his role in making space for marginalized groups.

Anne Condon, professor and head of the Department of Computer Science at the University of British Columbia told a longer story about Mary Lou Soffa, (Department of Computer Science, University of Michigan), who couldn’t be there. Dr. Condon said,

Mary Lou is a very prestigious researcher in compilers and software engineering, and probably the most outspoken person I know. Once a senior officer from a very prominent computing organization proudly unveiled a video about opportunities in computer science. Now in this video, all of the people profiled were white males, except for one little girl.

Mary Lou in true fashion stood up and she did not mince words as she told this senior official what she thought of that video. When she was done, there was total silence in the room. And then one voice spoke up, questioned the choice of profiles in that video and spoke to the importance of diversity as part of the vision of this organization.

And that person was David Notkin.

The speaker list at Notkinfest, aside from Dr. Condon, included somewhat of a Who’s Who in increasing diversity in computer science, including:

  • Martha Pollack, soon to be Provost for Academic and Budgetary Affairs, as well as Professor of Information and Professor of Computer Science and Engineering at the University of Michigan, who has received the Sarah Goddard Power Award in recognition of her efforts to increase the representation of and climate for women and underrepresented minorities in science and engineering.
  • Tapan Parikh, Associate Professor at the University of California at Berkeley, and the TR35 Humanitarian of the Year in 2007. (check out his TedX talk on representing your ethnic background).
  • Carla Ellis, member and past co-chair of CRA-W, CRA’s Committee on the Status of Women in Computing Research , past co-chair of the Academic Alliance of NCWIT. On her web page, Ellis says: “In my retirement, I will be pursuing two passions: (1) advocating for green computing and the role of computing in creating a sustainable society and (2) encouraging the participation of women in computing.”

Notkinfest was David’s next-to-last professional appearance. Here’s what he said at the open reception:

It’s important to remember that I’m a privileged guy. Debbie and – our parents, Isabell and Herbert, were children of poor Russian Jewish immigrants, and they were raised in the Depression and taught us the value of education and how to benefit from it.

Mom, especially, taught us the value of each and every person on earth. I still wake up and – You know, we have bad days, we have bad days, but we have plenty to eat and we have a substantive education, and we have to figure out how to give more back. Because anybody who thinks that we’re just here because we’re smart forgets that we’re also privileged, and we have to extend that farther. So we’ve got to educate and help every generation and we all have to keep it up in lots of ways.

When I spoke at his funeral, not three months after Notkinfest, the main thing I did was repeat that plea.

in another’s voice

This is a guest post by Katie, who divides her time among operating an interplanetary spacecraft, turning the gearwheels at her local hackerspace, practicing the Japanese Way of Tea, and an optimistic number of other things. It was originally posted to her blog.

When it comes to “geek culture,” my experience is slight—I’ve long thought of myself as a computers-and-engineering-and-hacking kind of geek, not a gaming/comics/fantasy kind of geek. There’s at least a post’s worth of potential self-reflection there, but my point is that despite currently showing few signs of involvement with the second kind of geekdom, I spent several of my high school and college years participating in tabletop role-playing games like D&D and Ars Magica. I probably would be now if I’d been invited into a group in the post-undergrad years before my plate filled with other things.

diceWhat I’m interested in exploring in this post is playing across gender lines—that is, role-playing a character of a different gender than your (the player’s) own. I don’t imagine this is entirely untrodden territory, but I hadn’t processed my own experience of being disallowed from doing it in the gaming group I spent the most and longest time in. Specifically, I hadn’t processed how bullshit that is. The GM‘s reason for the ban: verisimilitude. Fellow players would not be able to imagine the character accurately when that character’s words were coming from the mouth of a player of a different gender. Such a difference would overtax players’ ability to suspend disbelief; it would break the collective fantasy.

An obvious counterargument: if players can overcome the differences between a late-twentieth-century t-shirt-clad, Mountain Dew-chugging American teenager hanging out in a friend’s parents’ rec room and a pious sixteenth-century Saxon blacksmith trekking along thief-ridden roads, a difference of gender identity is barely material, let alone insurmountable. I may have expressed this argument to our GM, but I had no support from any other players, all of whom identified as male, so it was a take-it-or-leave-it situation. Since these were not only fellow players but friends, and I had a painfully hard time making friends, I took it. In retrospect, I wish I hadn’t, not because cross-playing was important to me, but because this absurd essentialism should have been a red flag.

None of the role-playing-game rule systems I’ve used have either banned cross-playing or discriminated among characters’ genders when it came to abilities or characteristics, as far as I remember. However problematic game publishers have been when it comes to issues like objectification, they weren’t the problem in this case. No, this was our GM’s own policy, informed of course by society-wide ideas about gender, and I’m curious how widespread that kind of thing was and is among GMs.

The one specific instance where I remember cross-playing was with a casual D&D group. To give you an idea of our silliness, I named my character Gillette just so that I could cap a victory by quipping that he was “The Best a Man Can Get.” There, though, we didn’t embody our characters so much as describe their actions in the third person. We moved figurines around a map of a dungeon. We did not often speak in our characters’ voices.

What have been your experiences with role-playing games and playing across genders? As a player and/or GM, have you encountered rules against it? Groups that encouraged it? Systems that imposed gender-based modifiers? Or supported non-binary character genders? And not just for creatures? Did the level of character embodiment make a difference? At the height of embodiment, have you had any experiences with live action role-playing across genders?

[For an overview of some feminist issues in tabletop role-playing games, see the Geek Feminism wiki.]

11 reasons we’re still not there yet: Women in science

Erin Hardee works in university STEM outreach and blogs at Let’s Talk About Science, where this was originally posted.

It is not uncommon, when reading articles about the difficulties that women in science face, to come across comments citing that female enrolment in undergraduate and masters programs has skyrocketed in recent years and thus, it is posited, the problem really isn’t a problem any more. While it is true that the number of female students in tertiary institutions has grown faster than men that is only one part of the picture and certainly not an indicator that equality has been attained.

Below I will highlight all the ways in which women in science are not yet equal to men in science and link to appropriate studies and articles for proof.

1. Women in science only outnumber men in undergraduate and masters degrees enrolments. When you look at number of graduates produced, undergraduate figures are balanced between male and female. When you look beyond that, “men surpass women in virtually all countries at the highest levels of education, accounting for 56% of all PhD graduates and 71% of researchers.” (study above) That means the people actually doing science (that is, research beyond undergraduate/masters level) are still overwhelmingly male.

2. It’s not just academia, either. In commercial work female scientists are woefully underrepresented, with no more than 10% of Science Advisory Boards made up by women (and this figure has dropped as time went on, not risen).

3. It’s projected that there will not be a 50/50 split of female and male scientists in STEM fields within the 21st century, perhaps because (among other reasons):

4. Women receive patents 40% as often as men;

5. And they also receive far less funding when they launch a new business than their male counterparts.

6. In terms of compensation, in the EU female scientists earned on average between 25% and 40% less than male scientists in the public sector

Now, some may argue that the reason for these figures are that female scientists just aren’t doing work that’s as good as male scientists, and rather than engage with that statement as an offensive opinion (which it surely is), I instead offer the following figures:

7. Both male and female scientists were more likely to hire a male candidate for a laboratory manager position over a female candidate. They also offered the male candidate a higher starting salary and were more likely to offer mentoring to a male candidate – despite the fact that the CVs were identical save for the candidate names.

8. Male candidates were also more likely to be rated as having done adequate amounts of teaching, research, and service experience than an identical female candidate.

9. Male authors were rated as producing work with greater scientific quality than female authors, especially when their work was deemed to be ‘male-typed’.

I’m not suggesting that the majority of people involved in those studies (or in STEM fields as a whole) are actively discriminating against women, but it is undeniable that there is an unconscious bias by both men and women against women going into these fields. Although more anecdotal, it’s also worth pointing out:

10. A woman who runs a popular science blog on Facebook who ‘revealed’ her gender was overrun with a deluge of comments ranging from shocked to misogynistic* – when her gender was never the focus of the initial post in the first place.

11. Reporting on female scientists focuses heavily on their families and domestic achievements in a way that male scientists would never be subjected to; while it may be important to highlight the challenges they faced in their time in science, what does it matter that she made a mean beef stroganoff?

Maybe taken individually any one of these statistics or stories might be explainable – a blip in the system or a quirk of circumstance. Taken together, however, they illustrate that things are not equal yet, and we have a long way to go until they are. It will take more than quotas or laws to put things right; men and women alike need to examine their actions and the reasoning behind them and strive to be as unbiased and fair as possible. The resulting equality for women won’t just help them, but everybody involved.

*as any internet-based feminist will tell you, read the comments at your own risk (both on the Facebook post and the Guardian article).

Interdisciplinary computer science at Mills College

This is a guest post by Ellen Spertus, who is a professor of computer science at Mills College and a senior research scientist at Google. She has been active in geek feminism since 1991, when she released a widely distributed report on women in computer science. Her many publications include a chapter in She’s Such a Geek, and she has contributed to several open source projects, including the software behind the Systers mailing list and App Inventor. She is perhaps best known, however, for being named Sexiest Geek Alive in 2001.

Everyone knows that the computer science pipeline leaks women. Once a young woman decides not to take computer science courses in high school or in college, it is hard for her to reenter the pipeline, and earning a PhD in computer science after a bachelor’s degree in sociology, for example, might seem impossible, even though an interdisciplinary background might make someone a better computer scientist.

In 1984, department head Lenore Blum (who has continued to be a leader in women and computer science) founded the New Horizons certificate program at Mills for women and men with bachelor’s degrees in other fields. (The graduate programs at Mills are coed.) It consists of eight undergraduate computer science courses and prepares students for either careers in industry or for graduate study in computer science. Certificate students have been admitted to computer science PhD programs at MIT, University of Virginia, University of Washington, and other schools.

The more revolutionary program, however, is the Master of Arts in Interdisciplinary Computer Science (ICS), founded a few years later, which aims to build on students’ past background and not just supplant it with computer science. In addition to more demanding coursework, ICS students need to complete an interdisciplinary thesis that combines computer science with another field, usually their prior one. For example, Erica Rios, who had a background in political activism, developed a technology-enhanced community organizing model to raise consciousness among Latinas over the value of their unpaid household work. Jeri Countryman developed and deployed a computer science curriculum for middle-school girls and went on to work for Techbridge and Iridescent on tech outreach programs for girls. Amy Dewey, whose undergraduate degree was in dance, developed a database to preserve swing dance moves and routines. Whenever a student proposes a thesis topic, I always ask two questions: First, what is the computer science content? Second, what about it couldn’t be done by someone trained only in computer science, like myself? I like to make the point that, rather than being deficient for not having an undergraduate CS background, their diverse experience enables them to accomplish things impossible for a more traditional computer scientist.

Appropriately, the Mills motto is “One destination, many paths”. Students have entered the program through various means and at various stages of life. Constance Conner had partied her way through college, ending up in low-paying dead-end secretarial jobs, where she became the expert on the dedicated word processing machine and early spreadsheets and databases. After a cocktail party conversation with a Mills graduate at age 30, she entered the ICS program part-time. Her first summer internship paid more than twice what she was making at her secretarial job ($15/hour vs. $7/hour). After graduating, she had five industry job interviews and got five offers. She accepted one, which paid well but that she found “uninspiring”. When an ICS alumnus, Allan Miller, remembered an interest she had once expressed in teaching and let her know about a part-time teaching position at College of San Mateo, she jumped at the chance to teach, something she had always wanted to do. In 1995, with the help of another ICS alumna, Dana Bass, she began working full-time at City College of San Francisco, one of the country’s largest community colleges, where she’s taught computer programming to an estimated 400 students/year.

One of Constance’s students, Karina Ivanetich was working in a bike shop after earning a BA in Anthropology and an MA in Sociology from the University of Virginia and pursuing her goal of mountain biking for a few years. She was planning to just learn programming but was so inspired by the material—especially compilers, which Constance frequently mentioned in the introductory programming class—that she entered the ICS program. ICS led to opportunities for her to participate in machine translation research at the University of Pittsburgh and to intern at Google and Wind River, where she implemented an instruction scheduler for their compiler. She is now a Senior Engineer in their compiler team.

Lisa Cowan learned to program as a kid and found it “super fun” but majored in Anthropology at UC Berkeley, not taking any computer science classes but “noodling around” on the pre-web Internet via dial-up. She found work at a start-up and realized she wanted a career in computing, so she entered the ICS program, where she appreciated the small class size and the camaraderie among the students — very different from Berkeley. After Mills, Lisa earned a PhD in computer science at UCSD, applying her anthropology background to studying mobile social media and human-computer interaction.

Alison Huml had planned to major in science at UC Berkeley but got off to a discouraging start. On the first day of her honors chemistry class, she was the only woman in the section. Before she could take a seat, the TA tried to redirect her to the general chemistry class down the hall. Alison stayed in the course but decided to major in English instead, graduating summa cum laude. She worked as a tech writer during the Internet boom but knew that she wouldn’t go far without an understanding of computer science, so she entered the ICS program. She has since co-authored books on the Java programming language and led writing and product management teams at Google, where she is now employed.

Other graduates (and drop-outs) of the program have gone on to work at Apple, Disney, Google, IBM Research, Microsoft, Salesforce, and Splunk, as well as many smaller companies. Marianne Marck is currently Senior VP of Software Engineering for Starbucks. It is tremendously rewarding as a faculty member to help students go from unfulfilling jobs to creative, high-paying ones, even if their starting salary sometimes exceeds mine as a
professor.

My ulterior motive in writing this guest post is to reach Geek Feminism readers and their friends who might be interested in entering the program or applying for our visiting industry faculty position. I can honestly say that feminism is front and center at Mills, a women’s college. Most of the Mills administrators and faculty, including the president, provost, and all of the full-time computer science faculty are women (by happenstance, not design); male faculty are equally committed to women’s advancement. The school is diverse in race, national origin, and sexual orientation, and has a growing awareness of issues faced by transgender and gender non-conforming students and advocacy for their full inclusion. (Editor’s note: Current students at Mills who have questioned administrators about policy have alleged that Mills continues to have an unofficial policy of rejecting women undergraduate applicants whose government-issued identification documents have a male gender marker.) Our biggest problems are (1) finding potential students, since they don’t know that a program like ours exists and (2) keeping them after they get great job offers before finishing the program.

Statement of support for Adria Richards

This post is issued collectively by Geek Feminism contributors.

The Geek Feminism bloggers would like to state our support for and solidarity with Adria Richards, who spoke up against inappropriate behaviour at the PyCon 2013 conference, and the organizers of PyCon 2013, who responded by promptly enforcing their policy with a warning.

The harassment and abuse campaign directed at Adria Richards disgusts, horrifies and scares us. We are very sorry this is happening to Adria and her supporters and are dismayed by SendGrid’s decision to end Adria’s employment there. We condemn the racism directed at Adria, which has been amply demonstrating that women of color are particularly unwelcome and vulnerable in the technical community. We continue to hope for and to work for a technical and wider geek community where women, especially women of color and other oppressed women, can voice their concerns about being unwelcome without being widely abused and threatened and thereby silenced.

Comments on this post are closed, and comments left on any other post, including linkspam submissions, on this topic will be deleted. Unfortunately the level of vitriol directed at Adria and her supporters in discussion spaces elsewhere on the Internet is beyond our ability to moderate.

We deeply apologise to members of our community who would like to add their support, de-brief, or co-sign this statement for our inability to host their comments.

Anita’s Quilt

This is a guest post by Gail Carmichael. Gail is a PhD student in computer science at Carleton University in Ottawa, Canada. She is passionate about computer science education and outreach, and is on the Advisory Board for the Anita Borg Institute. She blogs regularly at The Female Perspective of Computer Science.

'fraction quilt --- two rows to go' by r0ssie

“fraction quilt — two rows to go” by r0ssie

One of the big hurdles of getting more women into tech is making sure they know the job exists and providing more visible role models. Like my newest high school mentee recently said: “You hear women talk about becoming doctors, lawyers, and that sort of thing. Nobody ever talks about becoming a computer scientist!”

Enter Anita’s Quilt. A project of the Advisory Board of the Anita Borg Institute (of which I’m a member), Anita’s Quilt is an ongoing dialog of inspirational stories from women in tech supporting each other and individually striving to have more impact as technologists. We know things aren’t perfect for women in our industry; the Quilt is about giving people enough concrete ideas so they feel capable of taking actions.

We believe a personal story has the power to inspire, transform and shape others’ stories. With that in mind, Anita’s Quilt features a wide range of stories coming from undergraduate students to Turing Award winners (the Turing Award is the top prize for computer scientists). Stories are organized into campaigns. The Systers collection that came first showcased stories from some of the very first Systers (members of the technical-women-only Systers mailing list) as well as more recent members. The next campaign was all about the Grace Hopper Celebration of Women in Computing, and included stories about how the conference started and the impact it has had on attendees. The current cycle is called Legends and Visionaries, and includes a story featuring Anita Borg herself as well as one of those aforementioned Turing Award winners, Barbara Liskov.

So here we have a powerful tool to inform and inspire women around the world about careers in computer science and engineering. But we need your help. We need you to share the Anita’s Quilt website with your communities both online and in real life. We also need you to share individual stories. Read a few, pick your favourites, and tweet a line about why you liked it. Help draw attention to the women you found most inspiring. Hopefully, with your help, we can help the Quilt grow along with its impact!

not a beard

This is a guest post by Mari Huertas (@marihuertas).  She is an Obama for America Technology (#ofatech) alumna and instructor at the University of Chicago. She currently is working on an idea to shift self-publishing with fellow OFA alum Nick Leeper (@lucky33). She lives in Chicago with her husband, bossy cat, and an ever-rotating supply of tea. This post originally appeared on her blog.

It was a tongue-in-cheek joke on the campaign trail, and I smiled about it for a while – the recurring meme about the “bearded” Obama Technology team, a group of dudes who wore flannels and didn’t shave and didn’t care at all about either, thankyouverymuch. I smiled about it because it was true, to a point, and I felt we were a family, and family made jokes like that, even if not everyone was into it.

Then came the post-election press, some of which picked up the “beards” gag and, fawning over its delicious cleverness, wrapped it into numerous mentions of the Technology team’s accomplishments. Andrew Sullivan even wrote a post that referred to the Technology team as “Obama’s Bears”.

Now, let us be clear about a few things:

  1. I was on that team.
  2. I’m not at all bearded.
  3. I’m definitely not a bear.
  4. Nerdy? Sure. I’ll own that one.

And other women were on that Technology team, too – smart, savvy women. One managed the creation of an incredible system that our vendor integration and other technology components all could hit so we could operate as synced as possible (Carol Davidsen). One trained an entire digital SWAT team of interns and volunteers to handle Dashboard support (Brady Kriss). One spearheaded the development of our voter outreach and GOTV technologies (Winnie Lam). One reached into the tech community and rallied volunteers to help us build certain pieces of our infrastructure (Catherine Bracy).

Yet some articles skipped mentioning women almost entirely. Rolling Stonenamed one; Mother Jones listed zero before backpedaling under scrutiny and adding a handful at the bottom of the article. Both were chided and scorned for it. It was surprising but not unexpected that so few of my sex were included in articles about winning the election – recognizing women has been a historical, long-standing problem. But these women in particular had done outstanding, difficult work – they had just re-elected a president, for heaven’s sake – so if not now, when should they expect to be recognized for their contributions?

I write this now, in the waning halo of winning the election, because in the past few months, I’ve come to see in a painfully clear light how important it remains to rally and recognize women working in technology. From the dearth of women as speakers and panel members to the lack of diversity on development, IT, and product teams, we have a serious listing that needs to be righted. As I wrote at the end of 2012, we need to elevate the profiles of successful women so that others will see them and want to work alongside them – so they will know what roles are available and what roles they can make.

I want other females, young and old, to feel encouraged by the women who worked on this re-election campaign and in technology, civics, and government as a whole. I want girls and young professionals to find their way by the determined wakes we leave. We’re doing important, satisfying, fun work – we should broaden and extend our purview so more can wade into the fray.

Now, I want to make this next point as clear as the glass ceiling beyond which many women in technology have yet to climb: I love, support, and cheer on my tech brethren, bearded or bare-faced, because they are completely, indisputably awesome and deserve every word of the recognition they receive. I have sat in the front row of the conferences at which they presented and beamed and clapped hard while they stood and spoke. I have touted them publicly on social channels and privately in emails and discussions with others. I wish them every success and am fantastically proud to call them friends and co-workers.

But equal consideration and recognition for the work, contributions, and fur-free faces of the ladies who rocked alongside them?

We need that – not just for this campaign or election, but for all we do. Let’s make that happen.

Resources:

Re-post: When sex and porn are on-topic at conferences: Keeping it women-friendly

During December and January, Geek Feminism is republishing some of our 2012 posts for the benefit of new and existing readers. This post originally appeared on October 1, 2012.

This is a cross-post from the Ada Initiative blog. Discussion is extremely welcome!

We’d like to start a discussion: How can the Ada Initiative extend the example anti-harassment conference policy to explicitly allow respectful, woman-positive discussion of topics like sex and pornography when it is on-topic, without creating loopholes for sexist and exclusionary behavior to creep back in?

First, let’s be clear: harassment and unwelcoming behavior at open tech/culture conferences are far from over. For example, one recent conference tried to “break the ice” using slides with sexual messages and/or animals mating and ended up getting racism and prison rape jokes (unsurprisingly – see this list of higher risk activities for conferences to avoid). That’s why the Ada Initiative’s advice on including pornography or sexual discussion at technology conferences is “don’t.”

A brief explanation of why pornography and sex are off-putting to women and LGBTQ people of any gender: Most pornography shown in this situation assumes that the audience is male and heterosexual, and sends the message that everyone who is not a heterosexual man is not the intended audience. Also, shifting people’s minds towards sex often triggers people to view women as sexual objects, in a context in which women want to be treated as humans with a shared interest.

Cindy Gallop

Cindy Gallop speaking

But showing pornography and talking about sex in public are not necessarily a “women not wanted” sign. Women are using open tech/culture to create erotica by and for women, and to have open discussions about sexuality in general.

For example, Archive of Our Own is a “fan-created, fan-run, non-profit, non-commercial archive for transformative fanworks,” designed and created by a majority women community, and hosts erotic fan fiction written by women among many other fan works. At the Open Video conference, Cindy Gallop talked about ways to change pornography to be more women-friendly, as well as more “open source” (and launched a startup actually doing it). for women in open tech/culture also need to speak about what keeps women out of their communities, which requires talking about pornography and sex.

Valerie Aurora speaking at AdaCamp DC

Valerie Aurora speaking at AdaCamp

What we want to do is support conferences that have organizers, speakers, and attendees who are sufficiently aware of sexism, homophobia, racism, and other forms of harassment in order to distinguish between, e.g., trying to “spice up” a presentation with a little off-topic pornography, and a discussion of ways to change pornography to be more women-positive. Our own AdaCamp is an example of a conference in which sex and pornography are on-topic.

The Ada Initiative’s current anti-harassment policy includes the following paragraph:

Exception: Discussion or images related to sex, pornography, discriminatory language, or similar is welcome if it meets all of the following criteria: (a) the organizers have specifically granted permission in writing, (b) it is necessary to the topic of discussion and no alternative exists, (c) it is presented in a respectful manner, especially towards women and LGBTQ people, (d) attendees are warned in advance in the program and respectfully given ample warning and opportunity to leave beforehand. This exception specifically does not allow use of gratuitous sexual images as attention-getting devices or unnecessary examples.

We then add a blanket provision approving discussion about topics that are appropriate for the specific conference.

What do you think? Comments are open (but heavily moderated).

Food for discussion: A few examples of anti-harassment policies from conferences where sex and pornography are on-topic: BiCon, Open SF, and Open Video Conference.

Women in Tech and Empathy Work

A veteran online strategist, web designer, and front-end coder, Lauren co-founded a successful digital agency and ran it for 12 years. She wrote a book for women entrepreneurs called The Boss of You, of which she’s rather proud. These days, she advises tech startups, coaches entrepreneurs, and writes about business, tech, women, & other things on her blog.

I’ve written before on my blog about the ongoing puzzle of improving the ratio of women to men in the tech sector. It’s an issue with many angles. There’s an acknowledged “pipeline problem” — a lack of women graduating from university with technical degrees (or emerging from the equally prevalent & valued ranks of self-taught programming); earlier-in-the-lifecycle challenges around how girls are encouraged (or not) to study science, tech & math; questions around how to make hiring processes more inclusive of diversity, gender & otherwise; and issues around promotions, board diversity, and leadership positions.

Frankly, sometimes that seems like such a long list I hardly know where to start. And that’s not including many, many related and embedded issues, like conference speaker lineups, objectifying photos in slide decks, the investor landscape, et cetera. But at the risk of triggering fatigue on the part of those wrestling with these challenges, I want to shine a light on another aspect of the gender-in-tech problem that I rarely see acknowledged: the heavily gendered casting of roles within companies — or in other words, the way that tech companies with female employees tend to place them in “people” roles, while men dominate in technical positions.

Now, don’t get me wrong — I know this comes into the conversation from time to time, but it’s often framed as part & parcel of the pipeline issue: “There aren’t enough women programmers on the market.” While that’s true, I want to talk about the dynamics — and economics — that result from having male-dominated tech departments and women managing non-technical work.

In a recent (and utterly fantastic) piece in Dissent magazine, Melissa Gira Grant writes about how this played out at Facebook, according to a memoir by Facebook employee #51, Katherine Losse. Ms. Grant writes:

From my time in and around Silicon Valley in the mid-2000s, creating gossip product for the benefit of Gawker Media’s tech blog called Valleywag, I came away understanding Facebook as a machine for creating wealth for nerds. Which it is. But the unpaid and underpaid labor of women is essential to making that machine go, to making it so irresistible. Women and their representations are as intentional a part of Facebook as Mark Zuckerberg’s post-collegiate fraternity of star brogrammers.

[...] While [Mark Zuckerberg's] net worth shot upward with each injection of venture capital into Facebook, support employees like Losse scraped by with twenty dollars an hour. Facebook’s most valued employees—software engineers—relied on customer support staff largely in order to avoid direct contact with Facebook’s users. Rather than valuing their work as vital to operations, Facebook’s technical staff looked down on the support team, as if they were not much better than users themselves. “Personal contact with customers,” Losse writes, was viewed by the engineers as something “that couldn’t be automated, a dim reminder of the pre-industrial era…”

Though they pretend not to see difference, Losse, through her co-workers’ eyes, is meant to function as a kind of domestic worker, a nanny, housemaid, and hostess, performing emotional labor that is at once essential and invisible. [Emphasis mine.]

I was struck by Ms. Grant’s articulation of customer-facing and intra-company work as “emotional labour.” That phrase helps me put my finger on something that’s bugged me as long as I’ve worked in tech, which is the way women are frequently cast as caregivers in the workplace — and how the work associated with that aspect of their roles is valued (or not) and compensated (or not) compared to the work performed primarily by men (i.e. coding and other heavily technical labour).

Let me share a personal example. I once spoke on a panel at a tech event; the panel was comprised of digital agency principals, and I was the only woman alongside three men. Afterward, one of my co-panelists told me excitedly that he’d recently hired his first female employee. He was really fired up about it, because… wait for it… “Now we all actually talk to each other! And we break for lunch, because she makes us eat. It’s so much better than before, when it was just dudes.”

(Insert big, giant sigh.)

Now, the thing is, looking back on it, I can see that he genuinely wanted his workplace to have those things, and he didn’t know how to do that himself, so he hired someone (female) to do it for him. I think he really did value her emotional labour, in his way. He just didn’t have the awareness to appreciate that a) women don’t want to have all the emotional needs of a workplace delegated to them; b) emotional rapport cannot be the sole responsibility of one person (or gender); c) I’ll bet you dollars to doughnuts that woman didn’t have “coordinate everyone’s lunches and facilitate office conversations” in her job description; and d) I feel pretty confident she was not given significant financial compensation for those aspects of her work (even though it sounds like those skills were rare gems indeed amongst her coworkers).

The problem is that while the outputs (better communication, better self-care, a stronger team) are valued in their way, they aren’t valued in visible ways that afford women prestige. The parallels with women’s un(der)paid & often-invisible labour in the domestic sphere are perhaps too obvious to warrant spelling out, but I’ll go ahead anyway: Because we live in a culture that undervalues emotional and domestic labour, a significant portion of “women’s work” (like childcare, food preparation, housekeeping, elder care, and social planning) is uncompensated. And as a result, if you want your company to have someone on staff to ensure everyone is happy, well fed, and comfortable, you will likely hire an “office mom”; that person is overwhelmingly likely to be female; and she is almost certainly underpaid (and afforded less prestige & power) compared to her technical colleagues.

I’ve long engaged in a hobby where, whenever I visit a tech company’s website, I head straight to their “Team” page, and scan for the women. More often than not, I have to scroll past four or more men before I see a woman — and very frequently, her title places her in one of the “people” roles: human resources, communications, project or client management, user experience, customer service, or office administration. (One could almost — if one were feeling cheeky — rename these roles employee empathy, customer empathy, team empathy, user empathy, and boss empathy: all of them require deep skills in emotional intelligence, verbal and written communications, and putting oneself in the shoes of others.)

While I haven’t seen hard data on how this plays out across the industry (can anyone point to some?), my personal experience has been that women in tech are primarily found in these emotional labour-heavy departments, even in the tiniest companies.

(Let me add here that of course there are exceptions — men in HR and communications and customer service and so on, and women coders. I’m speaking here of the gendered way we perceive the roles (caregiver defaults to female, in our culture) and of the broad numbers (about 75% of professional programmers are men).)

This wouldn’t be a problem in and of itself — and I’ll be the first to admit that it is damned hard to hire women into technical roles, as I learned first-hand when hiring coders myself — except that there are a couple of complicating factors:

  1. Coders are lionized in the tech sector, and are compensated for their technical skills with higher wages and positional power — so women without coding chops are automatically less likely to advance to senior positions or command the highest salaries.
  2. There is a culture in tech companies that simultaneously reveres the “user” (at least as a source of revenue and data) and places low expectations on coders to empathize with users (or colleagues, for that matter) — creating a disconnect that can only be bridged by assigning user (and team) empathy responsibilities to another department. An extreme example of this is the frequent labeling of brilliant coders as having Asperger’s Syndrome — and the simultaneous absolution of unskillful communication as par for the course.

So long as we accept these as givens, we will continue to see women in tech struggle in underpaid & under-respected roles while men in tech earn far higher wages and prestige. And we will continue to talk about the challenges of communicating “between departments” without acknowledging that those departments are heavily gendered — and that the paycheques are, too.

I want to add, here, that I know this is complex, and in some ways uncomfortable to talk about, because it touches on topics that are hard to discuss — such as the question of why women don’t seem to be pursuing technical skills at the same rate as men, and are more often drawn to the people roles. Hell, I myself started out as what you might call a technical co-founder (I coded websites) for the company I ran, but at a certain point I hired developers to take that work off my plate because it was important for me to focus on the client relationships, business development, and running-the-company stuff. (That fork in the road will be a familiar one to most founders.) And the developers I hired were mostly men, despite intense efforts to recruit for diversity. I console myself with the fact that as a tech company with two women at the helm, we were definitely challenging norms (and we paid ourselves well, which I believe is important to this conversation), but part of me wishes I’d kept my coding skills up if only so that I could keep up my side of a tech-centric conversation, and so that I could stop having dark nights of the soul thinking that I’m playing into cliches and conventions about women in tech.

What I’d really love to see is for companies to start by having a more conscious awareness of how this dynamic plays out. There’s absolutely nothing wrong with hiring male programmers, or women, um, empathizers-of-various-stripes. But we do need to shift the culture, expectations, and compensation if we want to end the power discrepancies that result from gendered hiring practices.

If you work in tech, you can begin by asking yourself how your company fares on these fronts:

  • Are coders encouraged to develop their people skills (communication with colleagues and customers, user empathy, etc.), or are those skills offloaded to other departments?
  • Who coordinates workplace social events and other team building activities? Is that in someone’s job description, or has it simply defaulted to being someone’s unspoken responsibility?
  • Who mediates challenging conversations between colleagues? Is everyone encouraged to increase their skills in negotiation and conflict resolution?
  • How do you determine the pay grades for the various roles and departments in your company? Do compensation levels reflect any unconscious assumptions about the respective value of different skill sets? How do you value your team’s “empathizers”?
  • Who is responsible for managing intra-departmental communication? Are they accorded appropriate levels of compensation and prestige for their leadership and emotional labour?
  • If employees are expected to represent your company in their off-hours (as in the example of Facebook’s customer service team posting photos to their profiles outside of work time), are they compensated appropriately (e.g. with overtime pay, “on call” hours, a bonus structure of some kind, or simply with a higher flat salary)? Do you compensate people-facing roles for this “overtime” in the same way you compensate your coders for long coding sessions leading up to a launch?
  • How do expectations around external communication & branding (e.g. posting about work-relevant topics on personal social media profiles) vary across departments? To what degree are employees expected to update their social media profiles for the purpose (spoken or unspoken) of making the company look good? Is this work included in job descriptions? Is it paid labour?

I would love to hear others’ thoughts on this — my thinking on the subject is evolving, and there’s lots to unpack here. And I know I have my own biases on the matter, so observations on blind spots, etc. are most welcome.

How can I tell if my outreach to women is effective?

This is an Ask a Geek Feminist question answered by guest poster Erin Hardee, who works in university STEM outreach and blogs at Let’s Talk About Science.

How do you know that volunteer work you’re doing to encourage women to enter technology is effective? I get asked fairly often to volunteer from programs such as technology summer camps, mentoring, promotional websites and science fairs, and I’ve often wondered whether they are worthwhile.

While I like to think that every little bit helps, the fact is that programs targeted towards youth often have unintended consequences. Take the example of “girls in technology summer camp”. Maybe girls that attend technology summer camp would rather spend their vacation doing other things, and walk away annoyed and less inclined towards careers in technology than they were before. Maybe the girls that choose to attend are all girls that were planning to enter [science, technology, engineering and mathematics (STEM)] careers in the first place, and it has no effect. Even worse, maybe summer camps cause girls to make poorly-informed decisions to go into technical careers. Maybe they present an incomplete view which causes attendees to pursue STEM degrees, only to drop out when they realize what the degree is really about. Maybe they don’t realistically present the aptitudes required, and encourage attendees who are unlikely to succeed to pursue certain careers.

While the outcomes above might not be likely, they are possible, and as I do more of this type of work, I’d like to better understand its impact. As a minimum, I’d like to make sure that my work isn’t actually discouraging girls from entering the field, and at best I’d like to figure out what type of activity, per hour spent, has the most impact.

Does anyone know of any research on this subject, or have any thoughts in general?

Firstly, kudos for getting involved in outreach work – it’s great that you’re so committed to helping encourage the next generation of women into exciting and rewarding STEM careers!

Secondly, this is an interesting question. One of my favourite things about science in general and scientists in particular is the desire for evidence to support their stances. It’s perfectly reasonable to inquire about effective outreach and indeed, any outreach programme worth its salt should be asking the questions ‘is this effective?’ and ‘how do we make it more so?’. Unfortunately, those questions then lead to the meta-questions of ‘how do we define effectiveness?’ and ‘how do we measure it?’, which are far more woolly and hard to pin down.

From your question it seems like you have several different criteria for what could make a programme effective, and none of these are invalid. It could be that it provides an accurate, well-rounded view of what a particular degree is like in order to appeal to the ‘right kind’ of person, or it encourages everybody regardless of pre-existing interest to consider STEM subjects. These of course are two different aims, and it’s important to consider which we want our outreach to achieve when we’re planning and executing it. Is one necessarily better than the other?

Add to the mix the fact that there are so many types of outreach you could be doing and that they all link to different intended outcomes and it becomes very hard to measure them all to one standard. An outreach programme for a particular engineering school within a university may consider ‘success’ to be an increase in women applying for their school, whereas a wider-reaching, more generalised outreach programme may measure success in the number of woman who tick ‘I am more interested in science than I was before’ after attending an activity. The outcomes are also rather self-selecting; a summer camp may look more successful at recruiting young people into STEM subjects, but usually because the people who choose to attend them are already interested in those subjects to begin with. So unfortunately the question about which activity has the most impact per hour spent is nearly impossible to answer, at least when considering the wide range of possible outreach activities and the huge range of audiences and goals.

It is possible to reflect a little on why women choose to study STEM subjects and reverse-engineer the sort of outreach which would provide those influences. In this article a variety of factors are highlighted that show things like spending time outdoors and doing math problems and logic games were more positively influential for girls than boys. These are things that could possibly be worked into an outreach programme to make STEM subjects even more enticing to women. An even bigger influence seems to be classes and teachers – something I will touch upon a little later.

The good news is that even without rigorous data it’s possible to make sure your work is not in vain; instead of worrying about trying to find the most effective outreach activity, I’d recommend instead maximising effectiveness with the outreach you’re already doing by following these steps:

Remember what drew you to STEM in the first place and share your passion and enthusiasm.

The best spokespeople for STEM subjects will always be the people who are passionate about what they do and are able to share that with the people around them. Make sure you communicate that passion well, also — work on your presentation and communication skills so you can get your message across clearly and enjoyably for your audience.

Work with a programme whose methods and aims you agree with/enjoy.

There are lots of different outreach approaches out there run by a variety of groups and people*. Find the one you enjoy most; as above, you’re going to be most effective when you’re having fun. It’s better to have a positive impact on a smaller group (for example) than to force yourself to work with large crowds and to be miserable the whole time.

Evaluate your programme and look for ways to improve it.

Good outreach programmes should always have a clearly-defined evaluation programme to monitor effectiveness and give means for improvement. If the programme you’re working with doesn’t have this, work with them to create one!

Talk to the people you’re working with and ask their opinions.

The best way of figuring out how effective you’re being is to ask the people you’re communicating with, right then and there. Talk to them about what they find interesting about science (or maths, or engineering, or technology) and how you can help them explore that. Ask them what they feel the barriers are, what sort of support would help them, and what sort of things they’d like to see or do in the future. Feedback like that can be immediate and very helpful, especially when paired with effective formal evaluation.

Outreach can be effective on an individual level; aim for that as much as a general effectiveness.

While there’s a lot to be said about raising the awareness of the importance of STEM with the general public, when it comes down to it you’re really trying to affect individuals. Try and connect with the people you’re working with, find out what makes them tick and share your experiences. If someone is swithering or unsure about their options all it might take is one good personal experience to encourage them to pursue technology over another option.

Consider other options you might not have thought of.

We all know that working with young people is an effective way of encouraging more people into STEM, but think about other ways you might be able to positively influence their experiences. It’s been shown that good classroom experiences positively affect the uptake of STEM subjects later in life, so providing science and technology teachers with training which gives them more confidence in the classroom might actually positively affect a whole class. Providing equipment for clubs or access to journals for students can also contribute to a better experience in schools and an increased likelihood of STEM uptake.

Lastly, all the outreach in the world is only worth so much if the environment that recruits are entering is unwelcoming or toxic to them.

Therefore it’s also incredibly important to improve the STEM environment for women in order to retain them after they’ve entered. Work with your company or university to support women entering the area and make sure your voice is heard on important matters of monitoring and equality!

Outreach resources

UK

US

Australia

Further reading