Earlier quoted context omitted.
At a certain level of complexity, necessary to support everything a large company does at their scale, simply mindlessly churning out more code actually makes things worse not better. The big question is how to do something and not the actual work of doing it. Bringing down Facebook for a day due to a bad config is going to cost more money than a century of someone writing code.
>Facebook for a day due to a bad config is going to cost more money than a century of someone writing code. I simply don't believe this is true. Its one of those things that has become "fact" through repetition. I don't think there is even a way it could be proven if you wanted to. I don't think amazon loses $X millions if the site is down for an hour. I think people just say oh its down and come back later and buy e…
That being said if your service went down for 24 hours because of a bad code change, it probably means and your service goes down a lot. Because whatever caused that 24hr outage probably points to a systemic lack of process and discipline within the organization.