Without those steps there's another article waiting to be written: "Rogue developer brings down business for six days with a seemingly innocuous 1-line change"
Without those steps there's another article waiting to be written: "Rogue developer brings down business for six days with a seemingly innocuous 1-line change"
Of the two, I've had to unexpectedly work nights, weekends or even vacations at only one kind.
Guess which one I decided I'd rather work at.
It can be annoying to go past code reviews and yet there are fire everywhere all the time.
One of the methods I found had a cyclomatic complexity of 200+ and a single test, verifying that the result was not null.
I was told "no, you can't fix that, the NY office wrote it and they'll get angry with us if we change their code and refuse to help".
Things are worse than you think :)
This seems to be a pretty clear example of not making the process work for you. Unwritten policies. Having to escalate twice because of silly reasons. Hot fixes being miscategorized as features. Is a very urgent fix really the place to be fixing a bunch of other tech debt?