4 ms·
They're not interested in your email trail. They just want a scapegoat. You're not put on trial first before you're fired; you're just summarily shown the door.
by pjlegato 10y ago
They're not interested in your email trail. They just want a scapegoat. You're not put on trial first before you're fired; you're just summarily shown the door. Since you're not given any chance to defend yourself, your documentation doesn't matter.
Blaming an engineer for supposedly poor engineering is a lot more politically viable than blaming management for poor management -- because they're higher on the chain of command than you are.
- mi100hael 10y ago¯\_(ツ)_/¯ It's worked for me thus far. Actually, most of the time the situations have improved. If you go about raising your concerns tactfully, people start taking your opinions more seriously because you accurately forecasted problems in the past. It can also work to just take a little longer on a feature and do some cleanup/fixing without getting permission. If anyone bothers you about it, just say "I noticed this issue and wanted to avoid running into problem xyz again since it took us offline last week." Again, most of this boils down to tact. Project managers don't like looking bad to upper management. Usually you just have to point out (tactfully!) how dumb they will look if something crashes in prod on a weekend.