|
|
|
|
|
|
by fragmede
698 days ago
|
|
|
Working with someone who's not pulling their weight and induces negative progress on a team is just demoralizing, no matter how much money you have or make. Working with a 1x or 10x engineer? How about working with a -10x engineer? It's better than being unhoused, sure, but managers, faced with the challenges of firing someone, along with a demoralized team, aren't going to go "y'know what? it sucks being unhoused, lemme hire more bad employees" and loosen up hiring recs. We can discuss at length how terrible it is to be unhoused, but it's not going to change that basic fact. |
|
|
What about trying to work with them to make them a better employee?
Sure, there are some who genuinely just want to take as much as they can and give as little as they can get away with, but they are, without a doubt, a tiny, tiny minority of people. By and large, people want to be able to contribute and do good work.
The problem is, the current system doesn't allow this. It says if you're not hitting the ground running day 1, you're a liability. It says no one will ever be trained on anything, so even if you know Java, PHP, and Kotlin, if you aren't also a several-year veteran of AWS, Kubernetes, and Agile, you have no chance. It says the one thing that matters is Line Go Up, always, and if we ever suspect you might not be contributing as much to Line Go Up as you could be—even if you're not actively making it go down—then you are a problem and need to be forcibly corrected or removed.
So instead of investing in a system where employees feel valued, and know that if they need to shift from one specialty to another, or come in without 100% of the skills expected of the position, they can take a little while and be trained to do what's needed, we treat people like things, and then justify it by saying they'll make everyone else's pay lower if they're allowed to stay.