6 ms·
That's a fair point, and I agree that (if so; those of us who don't work at Google don't really know what's going on) the argument that he should have expected
by geofft 9y ago
That's a fair point, and I agree that (if so; those of us who don't work at Google don't really know what's going on) the argument that he should have expected not to talk about this at all is invalid. That's useful context, thanks.
However, I don't think this necessarily excuses him entirely. If there's a company-wide discussion group for future directions on tech stacks inviting input, and I write a long post arguing, in complete seriousness, that the best long-term tech stack for the company is to use Classic ASP on Windows NT 4.0, and I pull some stats about successful companies in the dot-com boom that used ASP, I think it is entirely reasonable for the company to re-evaluate whether they badly misjudged my critical thinking skills. I am not excused simply because they invited feedback from the whole company.
Whether this particular post is a comparable situation is certainly debatable, but I think that we cannot simply excuse it by saying that feedback was requested.
- cderwin 9y agoI don't really think it is debatable. Just the fact the the memo and the firing were so controversial, in both directions, implies that a number of strong critical thinkers are on both sides of this issue. Assuming that is the case, it's not reasonable to use the memo as evidence of a lack of critical thinking. And I think we all know Google didn't fire him because they believed him to be incompetent. In fact, Google didn't even claim as much, they fired him for "advancing harmful gender stereotypes." How can we ever have a genuine conversation about the under-representation of women in tech if people with a certain "undesirable" opinion get fired for expressing it?
- jacalata 9y agoClimate change is controversial. That doesn't indicate that there are strong critical thinkers on either side.
- moduspol 9y agoApparently the idea that there are biological differences between men and women that could result in unequal outcomes is also controversial. Although, to your point, that doesn't really require critical thinking. It just requires impressive mental gymnastics to dispute.
- geofft 9y agoI don't think anyone is disputing that there are biological differences between men and women (on the average) that result in unequal distributions of some outcomes. An easy example is "fastest marathon" or "number of babies". The dispute is that there are biological differences between men and women that are relevant to qualification to work at Google in software engineering.
- cderwin 9y agoThat's the argument alt-right folk who actually deserve our hostility are trying to use Damore to make. Damore, however, is instead arguing that those biological differences make women less likely to pursue engineering as a field, not that those difference make them inferior.
- geofft 9y agoThen why are the programs he's criticizing all about either successfully hiring or retaining women who are already interested in working at Google? He also explicitly mentions ability: "Note, I’m not saying that all men differ from all women in the following ways or that these differences are “just.” I’m simply stating that the distribution of preferences and abilities of men and women differ in part due to biological causes and that these differences may explain why we don’t see equal representation of women in tech and leadership." (Also, let's be clear, someone who seeks out the support of Stefan Molyneux to advocate his viewpoint cannot be meaningfully distinguished from alt-right folks who supposedly want to distort his viewpoint.)
- Aapjes 9y agoPeople's qualifications are not all the same. Imagine that Google wants to hire 1,000 people, but 10,000 people apply for a job. Then Google logically ought to take the best 1,000 people that apply. With diversity quota's, the company may decide to hire a less able woman in favor of a more able man.
- geofft 9y ago> How can we ever have a genuine conversation about the under-representation of women in tech if people with a certain "undesirable" opinion get fired for expressing it? The same way we can have a genuine conversation about the best web stack to use if people with a certain "undesirable" opinion get fired for expressing it. (I don't think the fact that other Google employees supported the document is strong evidence that you can think critically and reach the same conclusions. If Google reached one mishire in James Damore, they almost certainly reached many others. If you listen to the YouTube interview with him that was flagkilled off the front page earlier today, he says he was recruited for his puzzle-solving skills and ability to code; presumably Google recruits lots of people that way, and none of them have ever been examined for critical thinking in the interview process. I can certainly attest that at no point in my Google interview earlier this year was I asked to do anything that evaluated whether I could combine a couple of sources and reach a defensible conclusion and defend it, which is a pretty common engineering skill.) The very meaning of "advancing harmful gender stereotypes" is that he said things about gender that were so wrong that they have only the most tangential connection to reality and would seriously harm the business if time were spent to even demonstrate that they're wrong. That's exactly the same reason that if I advocate for Classic ASP on NT Server, you don't spend the time and effort to set up a test network and benchmark if IIS is getting you better performance.
- danarmak 9y ago> The same way we can have a genuine conversation about the best web stack to use if people with a certain "undesirable" opinion get fired for expressing it. If a bunch of people fired for pro-ASP opinions got together, started their own company that used ASP, and produced a successful product, they would get a lot of money, everyone involved would be happy including Google who would sell them ad services, and perhaps the market would shift in favor of ASP. If a bunch of people fired for anti-"diversity" opinions got together, started their own company that did not discriminate in favor of women and minorities in hiring, and produced a successful product, there would be a media storm and probably a boycott and demands for the company to not be allowed to use the Google Ad network. This is why I think you're wrong when you say the reasons for firing are "exactly the same" in both cases.
- 9y ago
- danarmak 9y agoIf an employee argues for ASP, you might fire him because this implies he's a really bad technical worker. But you wouldn't (have to) fire him because, in arguing for ASP, he hurt the feelings of the PHP proponents in the company and made them feel they have to justify themselves, provoking some to say they would not be willing to work with him in the future even on PHP projects, and that if he wasn't fired they would resign. With PHP vs ASP, we trust people to behave civilly and allow space for debate. With men vs. women, we don't. One man's modus ponens is another's modus tollens; draw your own conclusions...
- geofft 9y agoNope, a "civil debate" about PHP vs. ASP is a waste of time. No reasonable employer will give you space for debate between the two. If there were a company-wide week-long debate about PHP vs. ASP at my employer, I would seriously question whether I should be at a company where these sorts of questions are considered debate-worthy, whether I have to justify every decision I make about common-sense things (why am I writing shell scripts in sh instead of tcl? why am I using UTF-8 instead of EBCDIC?), and definitely whether I want to work with all the people on the wrong side of the debate - and maybe some of those on the right side, who are considering the matter debate-worthy - in the future, lest they pick apart every PR I make because of their lack of critical reasoning skills. I would certainly threaten to resign if forced to work with these people. The fact is, the primary reason someone is a bad technical worker in this era is that they're a poor coworker. Almost no projects of any significant merit are developed by a lone hero in a corner.
- danarmak 9y agoThere's an important difference between silencing opinions that (you think) are very stupid for practical engineering reasons, and not wanting to work with the fools who hold them; and between silencing opinions because you think they are morally abhorrent and harmful just by being expressed, and punishing people for holding or expressing them. Morality is a psychologically distinct category. Being morally wrong is not the same, is not treated the same, as being factually wrong. A core part of the problem here is that something we'd want to be discussed factually, like choice of programming language, instead became a moral issue. If a programmer advocates for ASP in a PHP company, it's reasonable he'd be fired, although I'd hope he'd be given a warning and a second chance first. However, thousands of people across the company would not get involved, the CEO of a megacorp would not cancel his family vacation to make a personal statement, the news media would not give it prominent coverage. Nobody much would care about a not-very-senior employee turning out to have a foolish or wrong factual opinion and being fired for it. But everyone cares about an employee making a moral stand that some (including other employees) may agree with, and being fired for that. To repeat my earlier point: advocacy of ASP, here standing for any technical or factual matter, might be very wrong factually; but advocating for ASP would not hurt people's emotions and feelings of safety.