Hacker News new | ask | show | jobs
by praestigiare 3088 days ago
You claim that there is a pattern of bad diversity hires, but your anecdotes are just as easily explained by confirmation bias: You see an incompetent male engineer, and you write him off as an idiot and forget him. You see an incompetent woman, and she becomes evidence that there is a problem with diversity programs. You remember evidence that supports your narrative.

Obviously my statement is not evidence either. I only wanted to point it out because this is so often overlooked when it comes to these issues. This is an arena where our cognitive biases are especially pernicious, and any discussion needs to address them.

5 comments

It depends on whether the incompetent male engineers are just as incompetent as the incompetent female engineers. For instance, she mentioned a female developer who couldn't write SQL queries. Are the incompetent male developers at that same level of incompetence?

Of course taking this into account cannot completely eliminate selection bias, and the sample size either way is probably too small to be all that meaningful. It sounds like the attitude of her manager towards the incompetent developer is actually the most significant point here: this incompetent developer is being retained and in fact praised by her manager for diversity despite the obvious issues. Does the manager treat incompetent male developers the same way? The implication of the post is clearly "no", but again selection bias is possible.

Yes.

In deep corporate America, there are plenty of people who have virtually no responsibilities beyond a few basic configuration tasks. They are still unable to perform many of these tasks without significant help from coworkers. And we cover for them.

Every incompetent coworker I can think of was a man. I do not think this is confirmation bias, I think it's basic statistics, because most of the engineers those employers hired were men.

I meant for my question to be directed specifically towards the person making the claim about her specific coworkers at a specific company. This company has hiring practices that are not necessarily reflected across all of corporate America, and the claims being made are about those specific hiring practices and the effects that they have.
From what little the OP has said about her company I am willing to take a wild guess that she does indeed work for a large coproration (lip service paid to diversity, incompetent people hired to demonstrate it)- where you can expect this sort of thing to be very common.

I don't know about corporate America in particular, but corporate anything is a big pile of useless dipped in incompetent, where all the work is done by contractors who are also useless and incompetent. Because there is noone in the damn org that knows how to hire a competent techie in the first place.

So for me the OP's experience is more simply explained by working for an organisation that doesn't know how to hire engineers, not anything to do with diversity drives.

In a way that was my point, I just wasn't really good at relaying it. Of course there are many incompetent male engineers but it's more noticeable when they are a "diversity hire".

I don't present my situation as anything more than anecdotal, it's just what I've noticed. And to answer your question no the manager does not treat male developers the same way, they're held to a higher standard. In fact the "middle-aged white male" has to be above average at this particular company to be kept on.

> she mentioned a female developer who couldn't write SQL queries

I'd wager a third of the nodejs "developer community" could be described that way. The key thing is was she hired to write sql queries?

Yes, that is part of her job, but it wasn't covered in the interview process from what I've been told.
I've worked with plenty of tech and related people who didn't understand basic technologies we expect in a given field.

I tend to reserve judgement until their effort can be judged. If he or she is slow but learning and improving, I'd accept (and probably raise with a manager) that the hiring process is flawed and try to help him/her.

If its just utter idiocy, I'm less forgiving.

I literally had a business analyst come to me - the new guy at the time - on her last day after several years of working in the org and ask me what her email address is.

Or the BA who insisted she didnt need to write a clear and specific spec for a feature, because she could just open up dreamweaver and put some buttons on a page.

Those sorts of people I have zero fucking time for, and will drink merrily when they quit/are fired.

Unfortunately, they tend to be promoted quickly. For being so brilliant, you understand.

And then they're your boss. Or your boss's mate.

Does she even bother looking at the docs or would that also denote how useless she is?
Well, she is learning it now and I wouldn't call her "useless". But her level of experience and knowledge is far below "software engineer" and if she were a guy she couldn't get away with it.
you'd be surprised. i worked with people who would write simple json structures by creating a class in java and then serializing it and printing it to the console to copy and paste. most of them were promoted out to management
> and if she were a guy she couldn't get away with it

I think this is untrue. I know a lot of male "sofware engineers" who are totally incompetent and remain well employed.

The best C++ programmer (someone who does real magic in the machine) I know has said that they can't think in SQL. Different people have different skills and mindsets.
Strikes me as a distinction without a difference -- incompetence means you are incapable of performing a task.

One could speak of someone having more skill than another, but if both skillsets have no value, it doesn't really matter.

>> It depends on whether the incompetent male engineers are just as incompetent as the incompetent female engineers. For instance, she mentioned a female developer who couldn't write SQL queries. Are the incompetent male developers at that same level of incompetence?

Oh yes. Especially if you work in, say, a big financial corporation- the kind of large, monolithic organisation that isn't a technology company, per se, but uses technology (as only a large monolith would). In that kind of place, you can expect the majority of "technical" employees to be largely uninterested in, and therefore fairly clueless about, technology (i.e. they're just in it to jump over to tech management roles down the line). So, software engineers who can't write SQL queries are a thing. A common, inescepable fact of life, indeed.

I would not like to say whether I'm speaking of personal experience with such organisations. It wouldn't be proper.

This can definitely be the case. There are lots of sh--ty white male programmers working in the industry.

I have met plenty of white men who have masters level CS education, have worked for Google and other top name companies, and can't produce a line of useful working code to save their lives.

The reasons why corporations frequently hire people who don't actually produce anything are varied and complex, but it happens, a lot.

If someone is incompetent and also happens to be from a minority group then everyone starts complaining about how they are a "diversity hire" but with incompetent white males they just shrug and go "that's the way it is." In other words, it is so common with white males that no one even notices.

>If someone is incompetent and also happens to be from a minority group then everyone starts complaining about how they are a "diversity hire" but with incompetent white males they just shrug and go "that's the way it is." In other words, it is so common with white males that no one even notices.

You could be right this is definitely a possibility. I did not intend to suggest that all white male programmers are awesome, certainly not the case.

And I'd add that there's evidence (and plenty of anecdote) that the men who most object to diversity are not so good at what they do. Which makes sense; they are the ones who have the most to lose from an increased talent pool. [1]

Personally, I'd be very interested to see Damore's code. We already know that he lied about both a PhD and being a chess master. [2] I would not be shocked at all to find out that he's not good at programming.

[1] http://journals.plos.org/plosone/article?id=10.1371%2Fjourna...

[2] https://chess.stackexchange.com/questions/18271/is-james-dam...

From the complaint:

"23. Damore was diligent and loyal, and received substantial praise for the quality of his work. Damore received the highest possible rating twice, including in his most recent performance review, and consistently received high performance ratings, placing him in the top few percentile of Google employees. Throughout the course of his employment with Google, Damore received approximately eight performance bonuses, the most recent of which was approximately 20% of his annual salary. Damore also received stock bonuses from the Google amounting to approximately $150,000 per year.

24. Damore was never disciplined or suspended during his entire tenure at Google.

25. Based on Damore’s excellent work, Damore was promoted to Senior Software Engineer in or around January 2017—just eight months before his unlawful termination by Google."

Sounds like he was pretty good, but I wonder about this part:

> Damore received the highest possible rating twice, including in his most recent performance review, and consistently received high performance

How are these ratings done, by the team/manager or externally? IME when it's done by the same team then reviews are more about politics than performance.

so let me get this staright: when Damore is being rated politics have an effect on ratings and promotions

when Damore speaks out against politics affecting hiring and promotion, he is wrong

I'm fascinated how one can reconcile both beliefs

Sorry that was terribly worded, I meant politics/political in the personal sense, who's friends with who, etc.
Yes, I'm sure Damore claims he was excellent. But claims of excellence do not correlate perfectly with actual excellence. And neither do promotion packets; I'm sure we've all worked with somebody who did better on paper than was justified.

So I'd still like to see his code. And talk with some of his coworkers.

You're just mining for something by now. It is clear that you implication that Damore was a sore loser that covered his lack of performance by blaming diversity has no connection to reality. Damore had performance completely satisfactory by Google's standards, and achieved significant praise from his peers, so whatever would be your evaluation of it, he was not in a loser position, had no reason to be sore for anything and had no reason to blame diversity for anything related to performance or its perception by others. Time to leave this horse, it's dead.
The guy appears to have lied about a PhD and being a chess master. So it's entirely reasonable for me to be skeptical of his claims in a lawsuit that he was an A+++ top performer. And even if those claims are correct, I still would like to look at his code and hear from his coworkers. He wouldn't be the first person to get promoted beyond his actual accomplishments.

Also, sweeping assertions like "had no reason" assume facts not in evidence. We mainly don't know what happened at Google. Or why he didn't complete his PhD. We have only heard his side of the story, and only part of that.

> We already know that he lied about a PhD

No, he did not lie about this. You are lying about it. His linkedin listed him as having been part of a PhD program and people took it to mean he had a PhD. There is absolutely no evidence he ever intended to mislead anyone about this.

So, please stop spreading lies.

    ====
PS I know because I actually saw the linkedin profile before he edited it. It did not say he had a PhD. It clearly listed that he was in the program for 2 years, which any person reasonably familiar with PhD programs would immediately suspect meant that he had not finished. And indeed, I followed up by looking up what publications he had, and while his name was on a couple of papers he had clearly not published a dissertation. So, to anyone who wasn't deliberately looking to discredit him for malicious or self-interested reasons, as Business Insider's Natasha Tiku almost certainly was, would not have been fooled for a second by his profile nor would they have believed that Damore intended to fool them.

Note the business insider article you linked uses these weasel words:

James Damore, the fired Google engineer who wrote the now-infamous memo on diversity at the company, has removed mention of PhD studies in biology from his LinkedIn profile.

The removal comes after Wired writer Nitasha Tiku confirmed with Harvard that Damore has not completed his PhD.

He then goes on to call out the "Right-wing argument" appealing to his credibility because he had a PhD.

If you read carefully, you'll see that they frame as if it was this embarassing thing that they'd shamed him into doing, to encourage lazy, non-critical readers to reach the same conclusion that you did, while using the technically correct words to avoid defamation liability. But, careful analysis of the facts shows that I am correct. He did not lie about the PhD, others either lied on his behalf without his knowledge; or were confused by careless/overly-optimistic reading of the LinkedIn profile.

I saw the LinkedIn profile too; I looked him up when the story first broke. I saw it and said, "Damn, a PhD in systems biology, he should know better than this." People who don't finish their PhDs either a) don't list the PhD, just leaving it as a Master's, or b) are explicit that they don't have the PhD. (E.g., "ABD in Systems Biology.)

So at the very best, his resume was misleading because he was incompetent at putting together a resume. That doesn't jibe with the theory that he's so very brilliant. The fact that he quickly edited it when called out confirms even he saw it as misleading; that he didn't comment or apologize suggests it was not a simple mistake.

Ah, and now that I go look for images, it did not list him as being part of a PhD *program". it just said "PhD, Systems Biology" under education:

http://static6.businessinsider.com/image/598b0f3776084a30198...

I'm glad to hear you weren't misled by that thanks to your expertise, but there's no denying that is misleading to a general-audience reader.

So your argument goes like this:

1. Damore truthfully specified he's a PhD student

2. You (I assume innocently) and others (some innocently, some maliciously) misconstrued this as a claim that he has a PhD degree

3. Despite Linkedin information being completely true and whole error being contained in your bad reading alone, you and others called Damore a liar.

4. Damore removed that true information to avoid further confusion

5. You construe it as a proof that Damore was a liar, since if he removed completely truthful information that some people misread and used it against him, he must have intended to mislead from the start, and that's why he specified his PhD student status exactly as it truly was.

6. This also proves Damore was incompetent, since he wrote his Linkedin page in a way that a hostile or inattentive reader was able to misunderstand his page where it suited his preexisting notions, which would never happen if Damore was any good at writing Linkedin pages, as it is known that well-written (or merely competently written) Linkedin page is impossible to misread or misinterpret, no matter how much you try.

7. This is further proven by the image, since Linkedin design and forms do not allow to distinguish incomplete PhD study in progress from a finished one and display merely a length of the study but not the completion status, clearly Damore intended to mislead by using the only options available in the Linkedin interface.

This sounds like extremely tortured logic aimed at arriving at predetermined conclusion that Damore is a bad person. Looks like you're continuing to mine for something that explains why Damore is a bad person (failing at the premise he's a bad programmer above), to avoid addressing what he said on merits - since if he's a bad person, he can't be right on merits, obviously, no bad person has ever said anything true.

Note, you don't have to address it if you don't want to, but if you do, personal attack is not the best way to go, even if a very common one.

That is not my argument.

My argument is that if in LinkedIn's education section you list a school and a degree -- which he did -- people take that to mean you have the degree. Ergo, he falsely claimed to have a degree he didn't.

Could that be an accident? Might it just be incompetence? Maybe. But given that he also falsely claimed on his resume to be a chess master, I think the simple explanation is that he lied about both.

That he then quickly removed things when called out with neither explanation nor apology fits in with the "lies to make himself look good" narrative. A person who had made an innocent error generally feels bad about the error and says so.

Your thing about LinkedIn form design seems to be pure fiction. I just checked: you can enter any text you like, including no text at all. People without a degree don't have to put a degree in. I spent an entire 3 minutes looking at examples, and people fill in all sorts of things, including "PhD Candidate" and "PhD Student (incomplete)" to make it clear they are not claiming the degree.

This is not a personal attack; this is me pointing out facts of his behavior and reasonable inferences.

>You claim that there is a pattern of bad diversity hires, but your anecdotes are just as easily explained by confirmation bias: You see an incompetent male engineer, and you write him off as an idiot and forget him. You see an incompetent woman, and she becomes evidence that there is a problem with diversity programs. You remember evidence that supports your narrative.

If you just base it on what you see, yes. But if you're partial to top brass interviews and conversations about getting this or that person to pad diversity, and of talk about overlooking skills since "we need more X", then no (of course that would still be partial knowledge of the overall state of the market).

Googles hiring process has had books written on it. People study for it. When you see someone there that is incompetent you are going to ask why they got through. Diversity hire is one obvious possibility.
> you write him off as an idiot and forget him

Not really. I have a lot of faith in our engineering staff so I wonder how he got hired and how he avoids getting fired. The uncomfortable truth is that if he was an employee that "looked good" I would know the answer to those questions.

As I said before, my response is not data, I know that. But what you just wrote is exactly how confirmation bias works: If he fit your narrative, he would confirm your narrative. That is why these discussions need to be about data, and not "what everyone sees and no one talks about."
My point is more that the anecdotal stuff matters -- by being ham-fisted in your attempts to address diversity you reduce inclusiveness.
Your faith in your engineering staff is beside the point. Bias is human nature. Unless you're actively structuring your processes to exclude or minimise it then you're certainly suffering from it, the only question is how.

It's not specifically gender or racial bias either. We ran a study of 700 candidates for a role, running regular hiring against blind assessment and found that the major difference for that role in that organisation was socio-economic... they'd been excluding great candidates who went to less prestigious universities.