That's only true some times. Unless the data is mission critical, or you introduce a really major bug, the company in question could be losing customer's and /

That's only true some times. Unless the data is mission critical, or you introduce a really major bug, the company in question could be losing customer's and / or significant revenue due to the slow down of the application. I'm not saying you're wrong, I'm just saying there's no hard rule on this. I've had to push code many many times without any outside testing and while occasionally it's been detrimental (but fixed quick, because I didn't have to go through QA), the large majority of times has been beneficial. A large and formal QA process can kill a product / project just a quickly as cowboy code.