Seriously they make so many of the same arguments sometimes that I question whether or not .ml isnt a poe instance of some kind.
Seriously they make so many of the same arguments sometimes that I question whether or not .ml isnt a poe instance of some kind.
So I’m not fan of the tankie trolls, but I can see this one as valid. Someone could be hired for perfectly legit reasons but still have people think it was a mandate just because they fit one of the protected classes. A comment like this one in the middle could readily imply that they wouldn’t be hired if not for a DEI policy. It’s one of those damned if you do and damned if you don’t things, you’re going to have people making assumptions on why someone got hired or not, with or without a formal policy.
DEI, or as it used to be called affirmative action, is a tricky thing to balance in the business world. Theoretically a given workspace should resemble the community around it. If the applicant pool doesn’t match up to the population though that’s really hard to do. So when they ask those demographics questions on the app, in theory it should be that if half your applicants (assuming equal qualifications) are group X and half are group Y then so should your hired staff, regardless of the community makeup.
“we should get rid of DEI because our white employees are too stupid to understand that we don’t hire unqualified people.”
Did I summarize that properly?
There are no quotas. You don’t hire unqualified people. This is still capitalism. No one gets a handout.
But the comment in the middle doesn’t imply that they wouldn’t have been hired without DEI. It only implies that if you ignore the second half of the sentence, like the .ml poster did.
I can see how it’s worded a little awkwardly, but the part after the word hired is not a separate piece.
It’s not meaning “beacuse she didn’t get the job” it’s meaning “because the reason she got the job was not for DEI reasons”.
I can tell it’s not separate, rephrase it though and you can get “they can think she was a DEI hire, or they could not think of her (not know she exists) because she wasn’t hired because of some element of her racial background (in the event that they didn’t have a DEI policy)”.
I’m not seeing how one can read that differently. Is it supposed to be ‘they could think that or they could not think that’? Because while true, that’s just assuming people would change their thinking spontaneously.
Edit, I think a lack of punctuation is the problem. Two different reads depending on where you put a comma.
“Or they could not think of her at all, because she wasn’t hired due to some aspect…”
“Or they could not think of her at all, because she wasn’t hired, due to some aspect…”
The first comma isn’t there in the OOP either way, so mentally putting it in makes sense, the second one completely changes the context though if you mentally insert on there. So I’d call it very awkwardly written, heck I’m not attached to this person and I read it in the second way at first brush. Particularly easy to go that route since ‘not think of at all’ would make it sound like they’re not around to be thought of.