←back to thread

1080 points cbcowans | 2 comments | | HN request time: 0s | source
Show context
hedgew ◴[] No.15021772[source]
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.

replies(31): >>15021858 #>>15021871 #>>15021893 #>>15021907 #>>15021914 #>>15021963 #>>15021998 #>>15022264 #>>15022369 #>>15022372 #>>15022389 #>>15022448 #>>15022883 #>>15022898 #>>15022932 #>>15022997 #>>15023149 #>>15023177 #>>15023435 #>>15023742 #>>15023755 #>>15023819 #>>15023909 #>>15024938 #>>15025044 #>>15025144 #>>15025251 #>>15026052 #>>15026111 #>>15027621 #>>15028052 #
ryanbrunner ◴[] No.15021858[source]
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.

replies(17): >>15021879 #>>15021892 #>>15022000 #>>15022018 #>>15022073 #>>15022588 #>>15022780 #>>15022931 #>>15023041 #>>15023358 #>>15023561 #>>15023702 #>>15024459 #>>15024944 #>>15024964 #>>15027097 #>>15028521 #
nicolashahn ◴[] No.15022073[source]
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.

replies(15): >>15022166 #>>15022241 #>>15022251 #>>15022252 #>>15022290 #>>15022356 #>>15022677 #>>15023037 #>>15023069 #>>15023120 #>>15023315 #>>15023353 #>>15023493 #>>15024899 #>>15025581 #
Blackthorn ◴[] No.15022166[source]
> 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.

replies(12): >>15022234 #>>15022276 #>>15022376 #>>15022416 #>>15022543 #>>15022548 #>>15022583 #>>15023201 #>>15023485 #>>15023808 #>>15024677 #>>15025432 #
nicolashahn ◴[] No.15022376[source]
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.

replies(10): >>15022684 #>>15022864 #>>15023060 #>>15024367 #>>15025203 #>>15025395 #>>15026342 #>>15026667 #>>15026784 #>>15027020 #
richmarr ◴[] No.15022864[source]
> You can't dismiss his points just because you're tired of talking about them

You can, and some people have, and that's okay. It's not clear whether you're making the implication here, but commonly it's implied that "if you walk away from the debate therefore you are wrong", which is fallacious. Nobody owes you a debate.

> I'm talking about handling what Damore claimed in an intellectually honest way

Then the initial argument needs to start from a place of "intellectual honesty".

Damore presented evidence to support his claim that women are on average less able than men in areas relevant to engineering. He didn't discuss veracity, or contradictory evidence. That's textbook confirmation bias, not intellectual honesty.

Damore then started making HR policy proposals. We use a 50/50 gender ratio as an indicator that a particular field is free from bias. It's one thing to propose that 50/50 is not the natural ratio to end up with, but until Damore can propose a model that predicts another number then proposing HR policy changes put the cart before the horse. This indicates that the policy changes are what James in interested in, not the evidence. More confirmation bias.

Further, Damore's proposals discuss diversity as a whole (race not just gender) without a single word of justification, let alone evidence. That's either more confirmation bias or conscious sleight-of-hand, either way, it's certainly not intellectual honesty.

I don't bear Damore any ill will, he should be forgiven, but this memo was a mistake and showed poor judgement and more than a little bias. These studies may be good science, but stringing them together to confirm a conclusion you'd already set your sights in making is bad science.

replies(9): >>15023061 #>>15023083 #>>15023320 #>>15023524 #>>15023583 #>>15023637 #>>15023672 #>>15023725 #>>15024169 #
barrkel ◴[] No.15023320[source]
Damore then started making HR policy proposals. We use a 50/50 gender ratio as an indicator that a particular field is free from bias. It's one thing to propose that 50/50 is not the natural ratio to end up with, but until Damore can propose a model that predicts another number then proposing HR policy changes put the cart before the horse.

I deeply disagree with this approach. You're essentially saying that unless you can come up with an alternative scientific theory, complete with predictions, it's not possible to criticise an existing theory about the world.

There's many plausible explanations why an absence of a 50:50 gender representation could be caused for reasons other than bias or average ability. That's enough to put a nail in that model of discovering bias. Coming up with a way of predicting what the right ratio is, isn't necessary to discard that metric.

replies(2): >>15024107 #>>15025252 #
richmarr ◴[] No.15025252[source]
> I deeply disagree with this approach. You're essentially saying that unless you can come up with an alternative scientific theory, complete with predictions, it's not possible to criticise an existing theory about the world.

That's a straw man. You're suggesting I disapprove of criticism, which is not so. I disapprove of demands for policy change when you don't even have a hypothesis for what your target should be.

Unless Damore (or someone else) can reasonably estimate whether their theory around 'biological' differences result in a natural 10/90 ratio or a natural 49.9/51.1 ratio then there isn't really a case to be made to change actual real-world HR policies on that basis.

Being able to reasonably estimate that 'natural' ratio is a massive task. You'd need to account for parenting, education, popular culture, socio-economic group, dozens of biasing factors. I'd expect that model to go well beyond what's possible.

Yes, that may impose a high hurdle on criticism of HR policy via this argument, but that's also the intellectual leap that Damore has claimed to have made from the evidence presented. How exactly he's managed that leap is problematic. He certainly hasn't demonstrated full knowledge of all of the factors involved.

> There's many plausible explanations why an absence of a 50:50 gender representation could be caused for reasons other than bias or average ability. That's enough to put a nail in that model of discovering bias. Coming up with a way of predicting what the right ratio is, isn't necessary to discard that metric.

Of course, and it's certain to be a combination of factors, some historical, some current that pushes representation away from 50:50. I don't think anyone is pretending that bias alone is responsible. But there's a mountain of direct evidence that bias is a significant problem. On the other hand the chasm between this biological source evidence and an actual hypothesised effect on representation is vast.

replies(2): >>15025493 #>>15025630 #
1. bluecalm ◴[] No.15025493{5}[source]
It was pointed out in this thread many times: one good way to approximate what the ratio should be at the point of hire is the ratio among CS graduates. It's 80-20 so it's natural it's also 80-20 among Google employees. If you force it to be say 70-30 then you are discriminating against men based on sex.
replies(1): >>15025903 #
2. richmarr ◴[] No.15025903[source]
> It was pointed out in this thread many times: one good way to approximate what the ratio should be at the point of hire is the ratio among CS graduates.

While this sounds reasonable on the face of it the reality is different.

Where are you sourcing these graduates from? In the USA computer science departments are barely above 10% women faculty, in China it's closer to 40%. Student numbers tell a similar story... so it matters where your graduates are coming from. For a multinational like Google this is a real question.

> If you force it to be say 70-30 then you are discriminating against men based on sex.

This is a loaded statement, based on the assumpions that (a) hiring if left alone is broadly meritocratic and (b) quotas are the only game in town. There's enough evidence to say that neither of those assumptions is true.

First of all, it's been proven many times that bias in hiring is a real problem and has a large effect. Hiring is not meritocratic. Second, Google doesn't use quotas, no bar-lowering occurs (Damore hinted at this but gave no specifics and no evidence... we have to reasonably discount it unless someone can prove otherwise). Instead diversity programs mainly exist around sourcing and trying to avoid false negatives in order to counteract systemic biases.

(Disclaimer, I work in this field and have written on this topic before: https://medium.com/finding-needles-in-haystacks/we-need-to-t...)

[edited to remove some text from parent post accidentally left at the end]