Isn’t this your employer’s problem? From your description, it sounds like you’ve collectively isolated Lutz from causing problems for you guys. Has your supervisor asked your opinion?
this post was submitted on 20 Jul 2023
2 points (60.0% liked)
Programming
17492 readers
45 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
I feel your pain because as you say these Lutzes are everywhere but I think you hit the nail on the head when you say, "simply paying the person until they choose to leave and tank some other team's / company's productivity is less risky than firing them and potentially having to deal with a lawsuit." This absolutely is the reason why it's so hard to get rid of these people.
We've managed to get rid of two such Lutzes on our team in the years I've been in my current job and on the first occasion it took over six months for the managers to build a sufficient case to just put the Lutz on a Performance Improvement Plan. The hope was that said Lutz would take the hint and jump rather than be pushed and luckily for us that's exactly what happened and the second occasion was just luck as not long after we started complaining about them the mass layoffs in tech started happening and we got rid of them as part of that (though we sadly also lost some good devs in the process).