3 ms·
HR is exactly the worst approach to deal with organizational and process problems like this. What do you do? Fire the entire dev team involved with the decision
by paxys 7y ago
HR is exactly the worst approach to deal with organizational and process problems like this. What do you do? Fire the entire dev team involved with the decision? Fire their managers who failed to set the right expectations? Fire the product team for setting deadlines that were too aggressive? Fire the CEO because hey, ultimately they are the one responsible for everything?
Even if you do all that, you're not going to go back in time and fix things for your customers, and you're definitely not going to prevent the replacement developers from making the exact same mistakes.
It takes really good leadership to build an engineering culture where good practices are valued and people learn from mistakes, which is why filling those positions is so hard and expensive. A company whose solution for every outage is to fire people isn't going to last very long.
- deleted 7y ago[deleted]
- AnimalMuppet 7y agoGP said: >> That's easy: HR. By all means start by being nice, but if people refuse to be careful then they can burn down someone else's prod. If people refuse to be careful. If they make a mistake once, teach them. If they make a mistake again, that happens. But if they make a mistake regularly, warn them, then warn them sternly, then fire them.
- compiler-guy 7y agoMaybe so, but then you still have the problem, because in a big organization, some newbie is always present and going to make that first mistake. So you still need to make it hard for people to make mistakes.
- csours 7y agoTo amplify: think about road signs when you are trying to get somewhere new, especially in places with weird parking or entrances. After you've figured it out, it's easy, but everyone is a first timer at some point.
- perl4ever 7y agoThat's simple; you just make sure nobody ever leaves and then you don't have to hire new people...
- engineeringwoke 7y agoFive years ago, I never would have believed you. But this is sage advice. It is unbelievable how important these technical leaders are, and you don't know how important they are until they're gone.