Comment by pixl97
Companies: "your testing is costing us thousands of dollars"
Devs: "So how much does an a few hours of outages cost again?"
Companies: "your testing is costing us thousands of dollars"
Devs: "So how much does an a few hours of outages cost again?"
Wow. Ignoring the proximate cause of leaving that code in there, imagine being the poor schmuck that forgets to deploy a code update to 1 of 8 servers, causing $440 million in damages, basically destroying a company overnight. It's so far outside of comprehension at that scale.
Answer: "Not as much as you think"
The reason is that most potential customers will come back later, and that's assuming that the system that went down even had any real money attached to it.
I see a lot of multi-region, multi-zone architectures deployed for government websites that get maybe a couple of unique users per day. These could be down for many hours and chances are that no human would notice.
In at least one case, a test routine activated in production created a terrible loss
https://www.henricodolfing.com/2019/06/project-failure-case-...