[notahacker]

Yeah, I'd agree with the OP's reasoning about why the idea wasn't very good, but if that mistaken attempt to help is grounds for quitting, they're going to really struggle at a corporation that's less interested in identity politics.

[mikestew]

As ksenzee alludes to in a parallel reply, it could be (to use an American cliche) the straw that broke the camel's back, coming on the heels of a whole host of stupid decisions. I've been there, where no single decision or behavior is enough to quit over, but enough of those add up and one starts looking for the door.

[notahacker]

Sure, it's also possible that said VP arrogantly insisted his idea was a panacea and/or vetoed the OP's other ideas to help. We weren't in the meeting.

But I can only go by the arguments the poster who was in the meeting made, and he seemed insistent that Dorsey is sincere about diversity, and decided to focus on why the "tech visionary" VP's idea was notionally sensible but had practical limitations rather than lambast their general attitude. And it's not an idea that ranks particularly high on an ignorance scale, or particularly shocking that a "tech visionary" not expected to have any particular expertise in the area of diversity might gravitate towards a tech solution. Ironically, it sounds like precisely the sort of misguided suggestion a VP is likely to propose after reading articles about name-based studies of hiring biases and being shocked by their findings them rather than the sort of idea that gets proposed out of ignorance or dismissive attitudes towards diverse hiring policies. Certainly sounds like a better response than "go and talk to HR about it. After finishing your work, obviously" that he might find all too common a response elsewhere...

Normally when we're discussing quitting over straws that broke the camel's back it's allegations of subtle workplace bullying rather than not thinking an engineer's idea would work...