Hacker News new | ask | show | jobs
by PakG1 518 days ago
People for some reason have an inability to separate the goals of DEI/EDI from the practice. It's possible that the goals are important and correct, but the implementation sucks. I am of this belief for many DEI programs I've seen. But I'm still pro-DEI. It just gets implemented often too simplistically and naively, enabling the creation of more controversy and also likely many poor outcomes in organizations. As for what percentage of DEI programs result in such poor outcomes, I dare not guess, I have too little data.

However, the comments that Zuckerberg is making makes me think he really thinks that the goals of DEI are themselves intrinsically bad. He seems to be leaning into the stereotypical type of thinking that causes the issues that DEI is trying to address in the first place.

I'm disappointed. I would have hoped that he'd be capable of diving into more nuance.

2 comments

The goals of most DEI programs can't be achieved without discrimination on the basis of protected class. If software developers are 18% women how can a company achieve 40% women software developers without discrimination? And that was a DEI goal a previous employer used. In fact they had the same goal for electrical engineer too despite being 10% women.

Ambiguous goals like "make people feel welcome" doesn't require discrimination. But those are not the DEI goals people object to. 3 out of the 4 companies I've worked at implemented DEI goals in the form of numeric thresholds, and used discrimination to achieve them. Only one carried out DEI in the innocuous manner.

I'd argue if you're looking to achieve DEI goals in the short-term rather than over decades, you're going to fail because the backlash and other consequences will destroy any progress you think you made. And I think that's what we're seeing. You can work towards DEI goals without achieving them in the short-term and still look to make good changes over the long run. But it requires a systems view of everything, including helping kids from various backgrounds to get access to the education they need and then helping them to be in an environment where they can actually successfully learn stuff. That's a multi-generational multi-decade problem, not a corporate fiscal year problem.
This is sort of no-true-scotsman argument. Sure, there is "DEI" that doesn't amount to a dog whistle for discrimination. That was the case at 1 out of the 4 companies I've worked at. But it's the exception to the norm in my experience, and in that of my peers. It sounds like Meta has reached the same conclusion.
You seem to be an example of what I'm saying. There are very few people that are able to separate the goals of DEI from the practice when doing their analysis. If we're able to do that, we'll be able to find better solutions. And the solutions can't be found by or within individual corporations IMHO. It's much more complicated than that.

It's also possible that you and I have a different idea of what the goals of DEI are and should be.

Fallacy aside, nobody has successfully proven that holding a few spots at Harvard each year is enough to bring the likes of American Blacks back to socioeconomic parity.

It's a flawed means to an end.

You say that 3/4 of companies you are familiar with used discrimination to achieve numeric thresholds of 40% women software developers. I can't name a single medium or large tech company that is 40% women software developers. Can you?
Only one company had 40% threshold, the others had 33% and 30% respectively. They also didn't always hit those thresholds. But yes, the recruiters explicitly had 40% women in tech roles as one of their OKRs at one of my previous employers.

The only company I know of that has over 40% women software developers is ThoughtWorks. But they are an Australian company and it is legal for them to discriminate against men in that country. They are transparent about their use of a strict 1:1 gender quota: https://www.thoughtworks.com/en-es/insights/blog/beyond-quot...

furthermore, he is blaming the company's decision on his COO and not on himself as CEO. more than almost any other founder, he maintained control over his company and for better or worse it is clear that he alone bears the responsibility for what the company does as a result of that control. blaming one of his most trusted, respected, and successful deputies for what he now describes as a failure does not reflect well on him as a leader in my esteem.
I think he did her dirty. Don't think he is where he is today without her being by his side back then. She was and remains a fantastic operator.