The World’s Biggest Coincidence

I’ve been reflecting on the spate of outages we’ve experienced over the last week or so. Outlook. Apple. Various banks. As one politician is said to have remarked, if they’re all a coincidence, they’re the biggest coincidence in world history.

I’ve considered a scenario which would not only explain the outages but also the explanations being given for them. My conjecture is that continuous deployment of the sort Amazon, for example, has been doing for years and vibe-coding are not felicitous companions. Consider that Microsoft described its Microsoft 365 outage last week as caused by a “latent software bug”. Microsoft’s explanation is consistent with my conjecture. Public incident reports are unlikely to provide enough information to confirm or refute it.

What is worthy of consideration is that vendors will not voluntarily use some of the gains they achieve from vibe-coding by the extended testing it requires. They would just shrug their shoulders and say “Things happen”. The vendor has an incentive to minimize its own expected costs not necessarily the total social costs of its failures.

I suggest changing that calculation via regulation. I propose establishing reliability requirements and imposing penalties for failures exceeding specified thresholds. Reliability standards should include factors like the duration of the interruption, the number of users affected, and the criticality of the service. Further, I think that vendors should bear some responsibility for the losses their negligence or defective systems cause. This gives them a direct economic incentive to prevent failures while leaving vendors free to determine how to achieve the required reliability. It also avoids micromanagement. I don’t propose telling vendors how to develop software. I propose making them bear more of the costs when their software fails.

One last word. Care should be taken in the regulation to avoid allowing a regulation intended to discipline dominant vendors inadvertently to protect them from competition.

0 comments… add one

Leave a Comment