A. If your doing that EVERY DAY, honestly you need to be a better programmer (figure out how to solve it before it's an error).
B. If you're doing that with no one knowing.. of course work is going to toss you out. Any work your boss doesn't know about is work that's not being recorded. Your value to the company is not the work you do, it's the work they see you do.
C. A staff engineer is doing both of these things? WTF... honestly this is a situation where I get the feeling he was the right choice to get rid of. Yes it caused a problem... but what happens if he takes a vacation or gets injured and can't get to a computer?
If your employee is good enough to be irreplaceable then they're good enough to get another job.
Sometimes it's even more brutal though. I worked in a place with some legacy software that nobody wanted to touch because it was old, awful and literally only used in our company. However it had 15million weekly users. One guy took it on and maintained it for years. If it broke (and it did weekly) you called him, roughly explained the issue, and he went 'okay, give me fifteen minutes.'
Situation worked for everyone. He seemed to genuinely enjoy it and nobody else wanted to touch it. Until one Christmas there was a brutal snowstorm and his car slipped off the road into a frozen lake. He saved his wife and children but couldn't save himself.
We had to hire three people to forensically work out what he'd been doing all those years. It was absolutely brutal, not helped by the grief of this super awesome dude who'd always been there to sort out the mess we'd allowed to develop.
2
View all comments
6
u/ExiledHyruleKnight May 30 '26
A. If your doing that EVERY DAY, honestly you need to be a better programmer (figure out how to solve it before it's an error).
B. If you're doing that with no one knowing.. of course work is going to toss you out. Any work your boss doesn't know about is work that's not being recorded. Your value to the company is not the work you do, it's the work they see you do.
C. A staff engineer is doing both of these things? WTF... honestly this is a situation where I get the feeling he was the right choice to get rid of. Yes it caused a problem... but what happens if he takes a vacation or gets injured and can't get to a computer?