> Honestly if a junior made a mistake that costed one month, there is some issue with the process and I REALLY hope they're not blaming you for it.
Ideally yes. But realistically no.
Ideally there would be management available and coaching on any junior SWE, or at least you'd hope so. Realistically he may be looking at the business end of a PIP.
Ideally there would be blameless post mortems. Realistically there's no such thing, if you fuck up bad enough you're going to be shown the door.
Ideally if you're a great software engineer you would be with a company for the life of the company. Realistically, the politics and toxicity of workplaces limit the career of any employee.
So I've seen people be hired who were expected to perform poorly but then were fired when layoffs happened to protect the core workers -- because stack ranking and all that.
It's kind of like poker. The moral is: if you can't see the sucker they're going to fire next, it's probably you. Basically, don't be the sucker at any work environment.
At the very least there should be two people to blame for the one-month delay problem, the person (junior) who suggested the bad change and the person (more senior) who approved it.
And of course the manager or whoever is replacing him. But as people have said I don't know how a junior could delay the project by a month in any sane company, isn't the code reviewed? Don't they have some kind of process for changes?
Ideally yes. But realistically no.
Ideally there would be management available and coaching on any junior SWE, or at least you'd hope so. Realistically he may be looking at the business end of a PIP.
Ideally there would be blameless post mortems. Realistically there's no such thing, if you fuck up bad enough you're going to be shown the door.
Ideally if you're a great software engineer you would be with a company for the life of the company. Realistically, the politics and toxicity of workplaces limit the career of any employee.