|
|
|
|
|
|
by st3v3r
3489 days ago
|
|
|
"I this had happened at any of the companies I started, I would have fired several people in the aftermath." And then no one would ever try to block a code review ever, and your code quality would go in the toilet. Then, something like this would happen again, except with a much less benign change, and your servers blow up (not literally). "1.) priority is not just high, it is critical" Priority is always critical for whatever little changes management wants. |
|
|
Which is why in an actual emergency, management needs to actually communicate with the people involved in the development pipeline, not just hope the normal flow will magically work faster.
This used to happen constantly at my office:
Boss: I made a ticket to [change thing]. It's urgent, and please let [coworker I pass tickets to] know that it's urgent too.
...
Me: Coworker, I just sent you a ticket, [boss] says it's urgent.
Coworker: Everything is urgent. Shrugs and goes back to working from the top of his ticket list, all of which have the same high-priority flag as the one I just sent him.