I work on a consulting company. We have extremely aggressive deadlines, and work with less than capable people on both sides of the table. This means sometimes

I work on a consulting company. We have extremely aggressive deadlines, and work with less than capable people on both sides of the table. This means sometimes that takes a usual programmer a few minutes to change a line of code and promote it to UAT. Forget the number of bugs that happens after this. Yeah, the number is VERY high, but is subjective. Think about the overall state of the program. When all that matters is velocity, people takes all forms of shortcuts. OO is out of the window. Hardcode? What about things that should've been parameters and are not only hard-coded, but spread along many files? TL;DR OP case seems contrived, or at least the other extreme. Processes should be followed. If the factory stopped because of that single line - or any other, someone would ask: all this to save 6 man days?