5 ms·
Certainly much better than a lot of the outrage that's been going on. A couple of nits: > I know most of Google’s work is people-centric. Hmmm...is that real
by mpweiher 9y ago
Certainly much better than a lot of the outrage that's been going on. A couple of nits:
> I know most of Google’s work is people-centric.
Hmmm...is that really so? Last I checked a lot of Google's code output and value-generation is backend-y, with very little interaction with humans. Google is also notoriously bad-mediocre at UX, though this has improved lately.
> Assuming that job skills and performance can be deduced from
> differences among demographic groups.
Hmm...he didn't do this, and in fact explicitly states that doing so is not correct.
> Damore naturally assumes the differences between
> typically female and male traits mean that men are more skilled.
I also didn't see that in the memo. At all. First, what he talks about is mostly preferences, not skills. Second, there is the whole "you can't draw conclusions about individuals from slight variations in populations"-thing. So you can't turn "women have slightly stronger preferences, statistically, for these things" into "men are more skilled". Third, and maybe least intuitively, this is almost entirely about the people who don't (yet) work at Google.
Finally, she brings up Northern Europe. I can relate, because I am also from Germany, and yes, the country finds, for example, having a female Chancellor simply not remarkable. So when people vote for or against her, it is largely (can't speak for everyone) because of what they think about her, her party and their policies (or in her specific case, lack thereof g), not because she is a woman or is not a man.
And I also believe this applies to other jobs as well.
However, what Sabine misses is that this has not had the effect of gender representation in the job market equalizing. Surprisingly, it has had the opposite effect, as has been documented many places. And yes, I want to stress again how utterly unexpected this is.
And so:
> I believe for example if it wasn’t for biases and unequal
> opportunities, then the higher ranks in science and politics
> would be dominated by women. Hence, aiming at a 50-50 representation
> gives men an unfair advantage. I challenge you to provide any
> evidence to the contrary.
Challenge accepted (although not for politics, that's a different subject)!
If it were obstacles, countries that (as we both agree) have fewer of those obstacles such as Northern Europeans ones would see more women in technical fields. The opposite is the case.
And of course there is the point that the question is not "why aren't there more women in these jobs", but "why are there any men that do them", because they generally suck if you want to have a life. See Jordan Peterson's excellent take on "Women in High Paying Jobs": https://www.youtube.com/watch?v=NV2yvI4Id9Q https://www.youtube.com/watch?v=NV2yvI4Id9Q
- mberning 9y agoI felt the same. But I think some of it can be forgiven. I don't think the author is a professional developer and doesn't seem to know just how much a development job could be "head down writing code".
- deleted 9y ago[deleted]
- danans 9y ago> Last I checked a lot of Google's code output and value-generation is backend-y, with very little interaction with humans. Honest question: When was the last time you checked Google's code output and how it was accomplished? Have you worked at Google for an extended period? I've worked at Google for many years, on more projects than one can count on 2 hands, and in my experience this commonly held stereotype about working here couldn't be more wrong. First, there is a ton of code written all over the stack from backend through UI, and most engineers are expected to be able to work on code from the UI through to the backend. This was true from the early days through today. It's been the case on every project I've worked on here: One quarter I work on the data pipeline, next quarter I work on an UI feature, sometimes both simultaneously. But even if you don't write a line of UI code, any non-trivial system created at Google requires a lot of human interaction for: - requirements gathering and design - code reviews - justifying resource requests - coordinating access to services that you depend on - suggesting, negotiating, and advocating for improvements to those services - etc, etc. It's very difficult, if not impossible, to leverage Google's environment to succeed without a lot of human interaction.
- peoplewindow 9y agoLots of Google's software is open source. It is easily checked. Regardless, I worked at Google for many years and agree with him. Implementing MapReduce, BigTable, MegaStore, even things like G+ or Teams is not a people oriented task. It involves long hours of working with machines, alone, punctuated with code reviews in which your code is systematically criticised by your co-workers but in a predictable and non personal way. There are occasional meetings but most engineers I knew there saw meetings as a necessary evil and got annoyed if they were too frequent. When I was a SWE the bulk of my work hours were spent working entirely with machines, or with processes that were run by people but were largely mechanical and formalised, like resource requests. I believe this sudden argument that coding is a highly social activity is motivated reasoning. The motivation being to try and arrive at the politically correct opinions required to survive in the modern Google workplace. If you tried to describe programming as a highly social and people-oriented activity to the average man on the street they would think you were bullshitting them, I have no doubt about that at all. Teaching is people oriented. Social care is people oriented. Most of your working hours are spent in front of people, talking to them. Programming is the opposite - most of your hours are spent in front of a machine. Talking to others is probably not the bulk of your job. If it is you probably aren't a developer, regardless of what you might think: you might be a tech lead manager at most.