Ask a Female Engineer: Thoughts on the Google Memo

Many of the more reasonable criticisms of the memo say that it wasn't written well enough; it could've been more considerate, it should have used better language, or better presentation. In this particular link, Scott Alexander is used as an example of better writing, and he certainly is one of the best and most persuasive modern writers I've found. However, I can not imagine ever matching his talent and output, even if I practiced for years to try and catch up.

I do not think that anyone's ability to write should disbar them from discussion. We can not expect perfection from others. Instead we should try to understand them as human beings, and interpret them with generosity and kindness.

I think one thing that struck me from the linked article was the point that the memo wasn't structured to invite discussion. It wasn't "let's have a chat", it was "here's an evidence bomb of how you're all wrong".

I think advancing points is fine, but if you're after productive discussion rather than an adversarial debate, you need to proactively invite discussion. And if an adversarial debate was what he was after, that does strike me as inappropriate work communication.

Then the correct way to handle it is to drop another refutational evidence bomb attacking his primary points instead of picking the low hanging fruit of claiming it's "too confrontational," "poorly written," "naive," or whatever other secondary problems exist (this is aside from wilfully misrepresenting his claims, which is definitely a bigger problem). Plenty of far more aggressive articles and essays have been written from the opposite side that have not been criticized in the same way.

And for the record, I did not get any aggressive tone from his paper. I thought he was as polite as he needed to be and made the necessary caveats. I think many people were just so unprepared to hear any argument from an opposing viewpoint that they read into it what they wanted to.

> Then the correct way to handle it is to drop another refutational evidence bomb attacking his primary points instead of picking the low hanging fruit of claiming it's "too confrontational," "poorly written," "naive," or whatever other secondary problems exist (this is aside from wilfully misrepresenting his claims, which is definitely a bigger problem).

This was addressed in the article. This burden has fallen on women since they were teenagers. To expect them to do it yet again, to have to defend themselves at work this time, is ridiculous.

I'm not talking about a woman having to prove her technical ability to her male coworkers at work because of their prejudices. I know that that's bullshit and I'm sorry they have to do so.

I'm talking about handling what Damore claimed in an intellectually honest way. You can't dismiss his points just because you're tired of talking about them (or what you think are the same points you've always been talking about, but I think Damore's comments on each gender's preference and pressures for picking careers had something worth discussing). What he said had at least some spark of originality and insight, otherwise it wouldn't have gotten nearly the attention it did. Consider, would we be talking about the memo if it were about how he thought Sundar Pichai was a lizard man?

Those who disagreed with Damore already won the battle. They kicked him out of Google and doubled down on their diversity initiatives/echo chamber. We should be able to talk about his arguments honestly and rationally without falling back on gendered reasons at this point at least.

> We should be able to talk about his arguments honestly and rationally without falling back on gendered reasons at this point at least.

We are and lots of people are doing so, but another point made in this post is that the workplace isn't the venue for this.

I'm still making up my mind on this one, but for the sake of argument, I'll disagree with you.

The workplace was the venue for this, because 'this' was evidence was that Google(his workplace)'s diversity initiatives and censorship were harming the company. He attempted to go through the proper channels (HR) as discussed in another part of the comment section for this very article.

Completely ignored by HR, and after some watercooler discussion in which he received confirmation that he was not the only one to have such thoughts, he decided to organize his thoughts into a memo, which from his perspective, introduced ideas that could explain the gender employment gap at Google and help make the company better by erasing the notion of being a 'diversity hire' among other things.

What it did not do was claim that his female coworkers were inferior. I feel the need to reiterate that because that seems to be the disinformation that many take home with them and use for their arguments against him. With it, they vilified and ousted him.

Going back and reading it now, it's hard to believe such a seemingly harmless claim (women aren't as well represented in tech because they're not as interested in it) has created such outrage. I blame this mainly on Gizmodo, and those who piggybacked their original article (that blatantly lied about what he wrote and presented his memo which they had quietly edited). Some credit also needs to go to whoever leaked the memo, which Damore probably did not mean to leave the relatively small group of people he originally introduced it to, at least at that point in time.

Really, what he presented and how he presented it were not very controversial. It easily could have been addressed internally by HR, or discussed within the company by its employees without the dishonesty and witch hunting. My point is, what he presented should have been acceptable in the way he did it especially given Google's claims of free speech and the historical precedent of memos like these, but dishonesty and close-mindedness distorted it until it looked like he was calling for repealing women's suffrage.

> Going back and reading it now, it's hard to believe such a seemingly harmless claim (women aren't as well represented in tech because they're not as interested in it) has created such outrage.

It is only hard to believe if you are entirely unfamiliar with the history of this discussion.

Let's take a more obvious example: the common racist claim that black people are lazy. It is possible to dress this up in neutral, scientific-sounding language. Someone ignorant of the history of racism in America could be fooled into saying, "Gosh, we should consider that as an explanation for why tech is disproportionately white." (That someone could harbor racial bias, but that need not be true.)

That would correctly generate outrage, because a) one should not be ignorant about the history of these things when jumping into a discussion with such impact on people's lives, and b) there is a long, long history of virulent racists edging their way into the mainstream by dressing up their prejudices just enough to sound reasonable to the ignorant.

Returning to Damore, the fact that a bunch of white men ignorant of the history of gender bias can't spot the patterns does not mean the patterns aren't there. The benefit of the doubt only applies to educated doubt, not the doubt that comes from not knowing what's going on.

That you were surprised by the outrage only means you haven't been paying attention.

And these are all points that apologists don't seem to understand. Why we can't just have rational discourse, debate about these issues, come to a middle ground. You know middle ground and compromise means in issues like gender and race inequality? That at the end of the day, the minority is still treated as less than. Hey there's been some progress, isn't that good enough? No, of course not.

We've been discussing these issues for generations. At some point the discussion has been had. No one is saying anything new. But every new group of people believe they have something worthwhile to say about it and until they get to regurgitate their own brand of ignorance they'll whine and cry about how they're being oppressed for not being able to maintain the status quo.