In fact, With the exception of 2011, in 14 years of Code Jam, no Female has ever made it to the finals. Google's own non-discriminatory machine tool that evaluates codes, which doesn't take into account one's age, gender, nationality or skin color into account, has shed some light on some embarrassing outcomes.
How? Assume for the sake of argument that discrimination is the only factor influencing the gender distribution among CS professionals. From kindergarten onwards the numbers are slowly winnowed down to 80% men and 20% women.
But now this 80/20 population enters a highly selective but objective contest and comes out with 349/1 (assuming there have always been 25 finalists in the 14 years of the competition and there was only this one woman I can't see in the photo proof). Surely this means that men are just better at programming?
But in fact men are just better at being outliers. The effect is not very strong at small deviations (i.e. the difference between an average person and an average programmer), but can absolutely become significant when you only look at the extreme ends of the distribution. (I have written a comment about that here https://news.ycombinator.com/item?id=14997524) When you only look at the 25 top performers, that is bound to influence the result.
Again, I don't think things are nearly so black-and-white, but pointing at one extreme case of men performing better wouldn't be enough to completely validate Damore's memo, if anyone were so stupid to make that argument.
I agree on your point that the discrimination begins very early on.
The aforementioned article, although, bolsters the point that females may aspire to adopt different career options. Therefore, the organizations can't be held responsible for creating the gap/divide. And I seem to agree with Damores's memo because he mentions solutions to the problem of gender-ratio-gap by suggesting programs to attract women to tech.
In conclusion, complaining about the gender ratio alone won't fetch us equality but collectively attacking the root of the problem may.
And so the further assumption was that if we do what other fields have done, make evaluations "blind" (the way it was done in Orchestras) those biases would not be able to express themselves and we would get equal outcomes. Or at least more equal outcomes.
Easy peasy!
The problem is it doesn't seem to be working out that way in tech. In fact, when we "blind" the processes, the needle appears to move the other way. Suggesting that, yes, there was bias, but not the bias we thought.
But that's not in the set of politically permissible answers/outcomes.
So companies are scrambling and trying their best to somehow bend reality to fit the accepted parameters. Which, well, leads to a lot of bending. Of rules, laws, reality.
http://valleywag.gawker.com/google-drops-i-o-ticket-prices-f...
Not only making a version of the competition where males are excluded (lowering the bar) but also tying it to financial rewards that men are not eligible for (free Google IO tickets with travel).
This is Google's problem in a nutshell. When one step removed from the the legally constrained hiring process, they openly and publicly engage in sexism against men. The game is rigged to ensure women win even though they can't compete, and women are granted special privileges that men are denied simply because of their chromosomes.
If Google wants to spend its money that way, it can. But its management can't then turn around and be shocked, SHOCKED, to discover that male employees are drawing the obvious conclusions: women are less interested in coding and there seem to be fewer of them at the top levels of skill.
Also note the hilariously misleading way Valleywag reported this: "Now the tech giant has a meritocratic pricing plan to encourage more women to attend their banner Google I/O conference ... the company is going to cover ticket and travel costs to Google I/O for women who performed well in its "CodeJam" coding competition."
1. Preventing men from competing is not meritocratic almost by definition.
2. They disguise this fact by making the link be "CodeJam" although it doesn't go to CodeJam, it goes to the separate "CodeJam to I/O for Women" site.
Followup edit
Clicking a link from the ValleyWag story brings me to madewithcode.com which seems to be some website designed by Google to encourage girls to code. This website is astounding. It essentially buys into Damore's view of the science wholesale. The top featured project is "Design a ZAC Zac Posen dress that turns heads", other projects are "Accessorizer: take your selfies to the next level", "Help Riley from Pixar's Inside Out solve some of life's problems", "Help a robot", "Code a heart to bring people together", "Dance visualiser" ... all on a bright pink background.
These projects are very clearly designed to appeal to teenage girls. They're about clothes, helping people, relationships etc. It seems to me like an open admission that girls do have different interests to boys, before they got anywhere near a hiring pipeline with "unconscious biases".
However, I'm very concerned about ideological denial of reality, in any field and every form. It's scary to realise that people can basically convince themselves to see anything they want, to the point of deeming any other view as unacceptable, if there is enough peer pressure to do so.
Google does not have and has never had infinite headcount. Even at times when Google's revenue was way ahead of its ability to spend it, there was always a limit looming somewhere in the future.
What's more, the bar is not an objective thing. Companies that find themselves the belle of the ball can raise their bar until the numbers who are passing match the companies ability to absorb them. Google is notorious for this; lots of people there who are overqualified for the work they're doing.
So it isn't possible to tip the hiring pipeline towards women without causing men to lose out. It might not seem like that at the time when it's go go go, but eventually, headcount limits appear.
Does it mean that I violated any policy? And what'll be the consequences of it - will it lead to account suspension or something?
It's only attached to the individual thread, not to your account, so no worries.
