this post was submitted on 30 Apr 2025
79 points (100.0% liked)
CSCareerQuestions
1187 readers
5 users here now
A community to ask questions about the tech industry!
Rules/Guidelines
- Follow the programming.dev site rules
- Please only post questions here, not articles to avoid the discussion being about the article instead of the question
Related Communities
- [email protected] - a general programming community
- [email protected] - general question community
- [email protected] - for questions targeted towards experienced developers
Credits
Icon base by Skoll under CC BY 3.0 with modifications to add a gradient
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I know everyone is focusing on the external issues, but serious question: could it be you? What have you done about working with your manager on code reviews and 1:1s for feedback around your performance? It’s entirely possible you’ve just managed to land in shitty companies, but it’s also possible you’re doing something wrong without knowing it and without fixing it and this is their way of being nice.
That's not being nice, being nice would be pulling him into meetings or going on a PIP to tell him what he's fucking up and how to improve. Letting an employee go for not doing something right is asinine, assuming there isn't a proper reason like misconduct or something, because (from the company perspective), you're pissing away time and money already spent on the employee without trying to improve the investment before throwing it away.
I know that sunk cost fallacy comes into play here, but there's a large spot before that's relevant where you can try to spend $ to improve an existing employee instead of spending $$$ to hire and train a new employee.
True but a lot of businesses lack that maturity and don’t realize the cost differences even when spelled out. They don’t want to put in the effort around training and correct coaching.
Bot
Wut?