Usually this is also how a company becomes woke. It's a chicken and egg scenario, or a feedback loop situation, but I'm pretty sure overhiring/underfiring is how it starts.
My theory: company grows big enough to hire an HR department. HR departments now screen applicants based on degrees, weeding out truly brilliant coders who just aren't credentialed in favor of morons with degrees. HR tends to also make it incredibly difficult to fire anyone, forcing managers to show very objective criteria. In most companies, the only real way to get someone fired is hoping for a a streak of tardiness or no-call-no-shows, after multiple warnings.
This means that people who just aren't good coders (usually due to a lack of natural talent, not any fault of their own) get hired more easily, and cannot be fired. HR would never let you fire someone for a vague "he's just not good." And it's very, very difficult to objectively prove "he's just not good" because HR isn't technical, so even trying to explain instances the employee lacked is difficult.
You can code the same thing a million different ways. All of the ways can be acceptable in certain circumstances. And what is "right" is always incredibly subjective, even if it is truly obvious to a good programmer which method is superior and which are unacceptable given the circumstances. There will always be an argument for the other approach, though. So if an employee is just stupid and consistently takes bad approaches, how do you pitch that to HR? Answer: you can't. Even if you diligently track times the employee has taken poor approaches to programming puzzles over months, that will fall completely flat to HR.
So now you're stuck with employees who can't do shit. What do you do with them? You create new positions for them in hopes that you'll be allowed to hire someone else to fill his/her place, who may actually be good. Repeat the cycle forever. Even when you find a good person, eventually his work load (since he is doing the work of now 10s of people by himself) will overwhelm him and he will need help. So you get to repeat the process again, which repeats forever.
How does this lead companies to becoming woke? For one: the field of HR typically attracts liberals, so you have a huge bias in your hiring. But, even if they don't let that affect their hiring/firing, the people with degrees who HR tends to hire who also aren't good employees tend to be liberal, whereas people who actually get work done tend to be conservative.
My friend's BIL was an early Twitter employee - I think one of the first 100. It paid for his house, but it was the worst place to work. Classic case of too many chiefs. He would bring up issues, but they were never addressed. They would contact him in the middle of the night all the time.
He left several years ago, but for a long time after he left, he would freeze up when his phone buzzed. He didn't realize he was even doing it until my friend pointed it out to him.
all useless women and indians "managing" the one white guy doing all the coding.
I wish I could buy you a beer for that comment. Fucking love it.
That is Woke company 101. Pay a bunch of worthless people to watch the few workers.. 80/20 rule.
True.
Usually this is also how a company becomes woke. It's a chicken and egg scenario, or a feedback loop situation, but I'm pretty sure overhiring/underfiring is how it starts.
My theory: company grows big enough to hire an HR department. HR departments now screen applicants based on degrees, weeding out truly brilliant coders who just aren't credentialed in favor of morons with degrees. HR tends to also make it incredibly difficult to fire anyone, forcing managers to show very objective criteria. In most companies, the only real way to get someone fired is hoping for a a streak of tardiness or no-call-no-shows, after multiple warnings.
This means that people who just aren't good coders (usually due to a lack of natural talent, not any fault of their own) get hired more easily, and cannot be fired. HR would never let you fire someone for a vague "he's just not good." And it's very, very difficult to objectively prove "he's just not good" because HR isn't technical, so even trying to explain instances the employee lacked is difficult.
You can code the same thing a million different ways. All of the ways can be acceptable in certain circumstances. And what is "right" is always incredibly subjective, even if it is truly obvious to a good programmer which method is superior and which are unacceptable given the circumstances. There will always be an argument for the other approach, though. So if an employee is just stupid and consistently takes bad approaches, how do you pitch that to HR? Answer: you can't. Even if you diligently track times the employee has taken poor approaches to programming puzzles over months, that will fall completely flat to HR.
So now you're stuck with employees who can't do shit. What do you do with them? You create new positions for them in hopes that you'll be allowed to hire someone else to fill his/her place, who may actually be good. Repeat the cycle forever. Even when you find a good person, eventually his work load (since he is doing the work of now 10s of people by himself) will overwhelm him and he will need help. So you get to repeat the process again, which repeats forever.
How does this lead companies to becoming woke? For one: the field of HR typically attracts liberals, so you have a huge bias in your hiring. But, even if they don't let that affect their hiring/firing, the people with degrees who HR tends to hire who also aren't good employees tend to be liberal, whereas people who actually get work done tend to be conservative.
My friend's BIL was an early Twitter employee - I think one of the first 100. It paid for his house, but it was the worst place to work. Classic case of too many chiefs. He would bring up issues, but they were never addressed. They would contact him in the middle of the night all the time. He left several years ago, but for a long time after he left, he would freeze up when his phone buzzed. He didn't realize he was even doing it until my friend pointed it out to him.
Now we know why he asked people to print out their recent 30 days of coding commits. I wonder how many have nothing to print.
I hope all those pajeets get deported.