women in science on the Google memo (& this is important, guys….)

Recent Forum Topics Forums The Public House women in science on the Google memo (& this is important, guys….)

This topic contains 1 reply, has 1 voice, and was last updated by zn zn 4 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #72285

    Note: if you don’t know the infamous Google Memo, you need to know about it for this article to make any sense.

    I’m a woman in computer science. Let me ladysplain the Google memo to you.

    Cynthia Lee


    I’m a lecturer in computer science at Stanford. I’ve taught at least four different programming languages, including assembly. I’ve had a single-digit employee number in a startup. Yes, I’m a woman in tech.

    I have known, worked for, and taught countless men who could have written the now-infamous Google “manifesto” — or who are on some level persuaded by it. Given these facts, I’d like to treat it — and them — with some degree of charity and try to explain why it generated so much outrage.

    At the outset, it must be conceded that, despite what some of the commentary has implied, the manifesto is not an unhinged rant. Its quasi-professional tone is a big part of what makes it so beguiling (to some) and also so dangerous. Many defenders seem genuinely baffled that a document that works so hard to appear dispassionate and reasonable could provoke such an emotional response. (Of course, some see that apparent disconnect not as baffling, but as a reason to have contempt for women, who in their eyes are confirming the charge that they are more emotional and less quantitative in their thinking.)

    The memo, for instance, begins by listing “biases” of people on both the “left” (“compassion for the weak”) and “right” (“respect for the strong/authority”).

    And, indeed, the concerns the manifesto articulates about imbalance in political leanings at Google are easy enough to nod along to. (“Alienating conservatives is both non-inclusive and generally bad business”) Much of the science it cites, too, has at least some grounding in peer-reviewed research, even if the author’s conclusions are not justified by the findings, failing to adequately account for sociological and other factors.

    The author, James Damore, even precedes his now-notorious list of biologically driven “personality differences” with this caveat: “[Y]ou can’t say anything about an individual given these population level differences.”

    But then he continues: “Women generally … have a stronger interest in people rather than things, relative to men”; and that this may “in part explain why women relatively prefer jobs in social or artistic areas.” He suggests that female extraversion tends to be “expressed as gregariousness rather than assertiveness,” which helps explain why women have a harder time “asking for raises, speaking up, and leading.”

    Why do women report higher levels of anxiety at Google, according to the manifesto? Because of their gender’s higher levels of “neuroticism.” The stress of being a minority demographic in a sometimes-hostile environment is not acknowledged as a contributor.

    “Note that these are just average differences,” the manifesto reiterates, soothingly, “and there’s overlap between men and women.” Here again, this studious dispassion and showy air of reasonableness create cover for the memo’s defenders. They have been vociferously arguing online that women at Google are not “average” and so they should not be offended by the manifesto’s litany of citations to studies of the “average” woman’s deficiencies.

    So why all the outrage? A few reasons:

    1) Fatigue

    It’s important to appreciate the background of endless skepticism that every woman in tech faces, and the resulting exhaustion we feel as the legitimacy of our presence is constantly questioned. I could fill a memoir with examples just from my own life, but the manifesto led to a few more instances. After one man on Twitter repeated that it was irrational for any one woman to take offense at a discussion of women’s characteristics “on average,” I responded:

    Colonel 32 @ColThirtyTwo
    Yeah.. That’s it. Definitely not a cult-like ideology dismissing anyone with ideas that challenge their own. It’s just not worth the time.

    Cynthia Lee @cynthiablee
    I teach probability and statistics at Stanford. I understood the part about averages

    That tweet captures a lifetime of being a woman in tech. (A subsequent tweeter said that, my CV notwithstanding, the “jury’s still out” on whether I’m qualified.)

    To be a woman in tech is to know the thrill of participating in one of the most transformative revolutions humankind has known, to experience the crystalline satisfaction of finding an elegant solution to an algorithmic challenge, to want to throw the monitor out the window in frustration with a bug and, later, to do a happy dance in a chair while finally fixing it. To be a woman in tech is also to always and forever be faced with skepticism that I do and feel all those things authentically enough to truly belong. There is always a jury, and it’s always still out.

    When men in tech listen to the experiences of women in tech, they can come to understand how this manifesto was throwing a match into dry brush in fire season.

    2) Women’s resistance to the “divide and conquer” strategy

    The manifesto’s sleight-of-hand delineation between “women, on average” and the actual living, breathing women who have had to work alongside this guy failed to reassure many of those women — and failed to reassure me. That’s because the manifesto’s author overestimated the extent to which women are willing to be turned against their own gender.

    Speaking for myself, it doesn’t matter to me how soothingly a man coos that I’m not like most women, when those coos are accompanied by misogyny against most women. I am a woman. I do not stop being one during the parts of the day when I am practicing my craft. There can be no realistic chance of individual comfort for me in an environment where others in my demographic categories (or, really, any protected demographic categories) are subjected to skepticism and condescension.

    3) The author cites science about “averages.” But Google isn’t average.

    I called the manifesto’s citations to findings about “average” women a “sleight of hand” for a very specific reason: While he dutifully includes that limiting language when making the citations, the policies he goes on to advance in the memo have no mathematically rigorous connection to those averages. He is deploying these dispassionate facts to argue for ending Google’s attempts at creating a fair and broadly welcoming working environment.

    (I cannot judge what the author’s motives might be in adopting this rhetorical strategy: It could be cynical and strategic, or, as I suspect, the author may simply be very, very naïve.)

    The author was not simply listing various items of scientific news at random, for the reader’s information only. He was building a case for ending specific, real programs that affect very real people. If his proposals were adopted, it wouldn’t be some abstract concept of “average” that doesn’t get a scholarship, it would be an actual individual woman. It would be an actual female Googler who doesn’t get to attend the Grace Hopper Conference, which provides many women with their first experience of being in a majority-women tech conference space.

    If, as the manifesto’s defenders claim, the population averages do not have anything to say about individual Googlers, who are all exceptional, then why is Google the subject of the manifesto’s arguments at all? What do averages have to do with hiring practices at a company that famously hires fewer than one percent of applicants? In the name of the rational empiricism and quantitative rigor that the manifesto holds so dear, shouldn’t we insist that it only cite studies that specifically speak to the tails of the distribution — to the actual pool of women Google draws from?

    For example, we could look to the percentage of women majoring in computer science at highly selective colleges and universities. Women currently make up about 30 percent of the computer science majors at Stanford University, one key source of Google’s elite workforce. Harvey Mudd College, another elite program, has seen its numbers grow steadily for many years, and is currently at about 50 percent women in their computer science department.

    Yet Google’s workforce is just 19 percent female. So even if we imagine for a moment that the manifesto is correct and there is some biological ceiling on the percentage of women who will be suited to work at Google — less than 50 percent of their workforce — isn’t it the case that Google, and tech generally, is almost certainly not yet hitting that ceiling?

    In other words, it is clear that we are still operating in an environment where it is much more likely that women who are biologically able to work in tech are chased away from tech by sociological and other factors, than that biologically unsuited women are somehow brought in by overzealous diversity programs.

    4) Race

    It is striking to me that the manifesto author repeatedly lists race alongside gender when listing programs and preferences he thinks should be done away with, but, unlike gender, he never purports to have any scientific backing for this. The omission is telling. Would defenders of the memo still be comfortable if the author had casually summarized race and IQ studies to argue that purported biological differences — not discrimination or unequal access to education — explained Google’s shortage of African-American programmers?

    5) The author says he’s open to diversity, yet no real-world diversity-enhancing program meets his standards

    Many defenders of the manifesto have eagerly, and, as far as I can tell, earnestly, pointed me to the manifesto writer’s frequent claims to support diversity in the abstract, as if these are supposed to be reassuring. (“I value diversity and inclusion, am not denying that sexism exists. …”) They are not reassuring. The object of his memo is to end programs at Google that were designed, with input from a great many people who are educated and focused on this issue, to improve diversity. If those programs are killed, absent a commensurate effort to create replacement programs that have plausible ability to be at least as effective, the result is to harm diversity at Google.

    He does make some recommendations, but they range from impotent (“Make tech and leadership less stressful”) to hopelessly vague (“Allow those exhibiting cooperative behavior to thrive”) to outright hostile (“De-emphasize empathy”).

    In the end, focusing the conversation on the minutiae of the scientific claims in the manifesto is a red herring. Regardless of whether biological differences exist, there is no shortage of glaring evidence, in individual stories and in scientific studies, that women in tech experience bias and a general lack of a welcoming environment, as do underrepresented minorities. Until these problems are resolved, our focus should be on remedying that injustice. After that work is complete, we can reassess whether small effect size biological components have anything to do with lingering imbalances.

    For today — given what women in tech have had to deal with over the past week — try pouring a cup of coffee for a female coder in your office, and asking her about the most interesting bug she’s seen lately.


    ‘Dear Mr. Google Manifesto’: Epic Response From Chemical Engineer, Corp VP, Mom Of 5
    “Women in science and engineering fields need to start telling their stories,” she says.


    Melissa Aquino, a mother of five who’s been married for 26 years and also happens to be a chemical engineer who serves as a corporate vice president for a Fortune 200 company, saw the headlines this week sparked by a now-former Google engineer’s 10-page internal memo critiquing the Silicon Valley-based company’s diversity initiatives. As a female who battled discrimination in her education and early career, she knew the memo might upset her. She waited for a quiet moment alone to read and digest the entire document. What happened next was what you’ll read below.

    “I decided to pen this,” Aquino said about a Facebook post she wrote Tuesday and gave Patch permission to share, “because women in science and engineering fields need to start telling their stories, showing the real challenges they face in pursuing male-dominated fields.”

    While the memo written by male software engineer James Damore was directed at the tech industry — he said biological differences between men and women are significant and may explain some of the gender gaps at Google — Aquino said there are many parallels to her experiences and those of women in all fields of engineering and beyond.

    Dear Mr. Google Manifesto,
    I don’t know your name nor do I care to. But I do want you to know something about me. I was born in 1971, when women contributed 4% to household income. In 2018, in dual earning homes – it will be 51%.
    At 10 – I was told I was average at math by my male 4th grade teacher. I was not allowed to try and solve the cool new Rubik’s cubes. Those were reserved for the advanced kids – mostly boys.
    At 12 – I took a standardized state test and my math skills came in as “advanced.” I was put in honors math to start junior high.
    At 14 – I signed up for my first chemistry and physics course. I was told “boys usually take this class, but OK.”
    At 16 – I took my first business class as an elective and my teacher handed out grade slips showing I had a B. When I challenged him he told me “your face just looked like you deserved a B.” I fought that and won.
    At 18 – I graduated Valedictorian and earned a scholarship to an all engineering school where the ratio of men to women was 5:1. I started school and walked in the cafeteria where it was custom for the men to pound on the table whenever a woman walked through on her first day.
    At 19 – I had a stalker who put perverse notes on my dorm door or slipped them underneath. My dad was concerned for my safety and thought I might need to come home for a while. But I stayed.
    At 20 – I took my finals on a Thursday, I got married on a Saturday and started my internship with Conoco in the Texas oil fields on Monday morning. I worked amidst the tarantulas, rattle snakes and hot sun to sketch pipes and tanks. At the end of my summer – the executive doing my exit interview saw my wedding ring and commented – “That’s too bad. WE tend to look at our married ladies with less dedication.”
    At 22 – I graduated #1 in my class of chemical engineers and I walked across the stage to accept my diploma while pregnant with my first child.
    At 22 – I started my first job with Procter & Gamble pregnant. I was told I would be part of a plant start up – in 6 months. The lead technician asked my boss in front of me “Can she even do this job.” My first boss – Jeff – still matters to me. He said “Yes she can and you can’t ask her that.” I did that plant start up – 7 months pregnant, in my steel-toed boots, going up and down two flights of stairs to take samples all night during third shift at a St. Louis plant.
    At 24 – I was pregnant with my second son. At 7 months pregnant, I completed a pilot plant trial in the back woods of North Carolina using one of the most highly explosive chemicals on the planet. At one point we had to run up over the hills because we thought the plant might blow up. I have a patent on that work.
    At 26 – I was given one of most complex assignment in my department – going to the plant running 100,000 pounds an hour, do 3 formula switches, sack off 2,000 pounds of each and get it all done in one shift and on a truck. I was the only woman on my team. I found out later there was chatter among some of the men that my boss should never give that to a woman.
    I won’t bore you with the next 20 years. They are colorful. But I do want to share why today is very meaningful to me – August 8th. On this day in 2008 – I gave birth to my second daughter. On this day in 2012 – I gave birth to my third daughter. On this day in 2017 – I spent my time in São Paulo, Brazil, where I work for a company that provides me a platform to walk across the stage and say, “I’m a Corporate Vice President. I’m a Chemical Engineer. I’m a Mother of Five.”
    So I want you to answer just two questions for me regarding your manifesto:
    (1). You are a fellow scientist so I hope you can appreciate my request that you provide the sources for these precise, single variable social science studies that have isolated gender as the main reason girls tend not to choose math and science? If they do exist, they surely must have also invented a time machine. So I want them to go back and tell 10-year-old me I was actually good at math.
    (2). Which part of “high stress” do you attribute to tech jobs that women aren’t suited for? The actual work itself or possibly, could there be another source of stress in a non-diverse environment?If you could kindly extract yourself from your Google nap pod or step away from the ping pong table – mosey on over to get yourself a shot of wheat grass and go outside to the picnic tables and pen me an answer. Oh wait, you can’t because they fired you. Well anyhow, I don’t care about the answers to those questions. Let’s have a real intellectual debate – which discipline requires more toughness – chemical engineering or coding? (Hint: I still own my steel-toed boots, a collection of hard hats and my flame retardant jumper.)
    Best of Luck,
    Melissa Aquino, 46
    Chemical Engineer
    Mother of Five

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Comments are closed.