I think at the very least we can agree that it is the employee's job to inform their superiors of feature creep, looming technical debt, and whatever bad practices they see.
If you're fixing bugs in production because your manager hasn't addressed longstanding technical debt, then yes, you shouldn't feel bad about the bugs that slipped through against your advice. In that case, I think your indignation at working extra hours without getting paid would be justified.
Ideally, we would do proper estimates upfront without being pushed to grossly underestimate features because so-and-so thinks it should only take a few minutes.
Pushy managers and bad employees are made for each other. It's a feedback loop.
"I think at the very least we can agree that it is the employee's job to inform their superiors of feature creep, looming technical debt, and whatever bad practices they see.
"
Yes, please yes. This is really where 1-1s come into their own. I can ask directly - is there any part of the code you're working on that truly sucks, and is going to break? I don't care who wrote it or when (it was probably me), I just need to know, so I can put it in the backlog
If you're fixing bugs in production because your manager hasn't addressed longstanding technical debt, then yes, you shouldn't feel bad about the bugs that slipped through against your advice. In that case, I think your indignation at working extra hours without getting paid would be justified.
Ideally, we would do proper estimates upfront without being pushed to grossly underestimate features because so-and-so thinks it should only take a few minutes.
Pushy managers and bad employees are made for each other. It's a feedback loop.