Software Is Breaking Down at a Systemic Level
A global Microsoft outage, an FAA ground stop, the PHP2Shell exploit, and the eMudhra weak-key fiasco all point to a deeper problem: software isn't just buggy, the way we build it is broken. The author traces this to cloud computing, open-source dependency chains, and now AI, which produces locally valid code that coheres into nothing. Engineers can no longer hold systems in their heads, and the result is cascading, systemic failure.
Decoherence: the accumulation of locally valid but mutually incompatible or redundant models within a system, such that the cost of change is dominated by translating among those models and preventing unintended side-effects.
- doug_durham
This narrative isn't consistent with reality. Cloud computing is much older than 10 years ago. We were doing production grade cloud computing over 16 years ago. The OSS revolution dates to the late 90's. The author seems to think that SWE was in a golden age 10 years ago. Sorry, but it's about the same. We have the same problems in SWE as we had 40 years ago. The scale and ambition of the problems we are solving have increased as compute capabilities have increased.
- CharlieDigital
It doesn't have to be this way.
AI is great at following patterns. AI is great at writing tests. AI is great at doing work that humans would consider drudgery and then applying "enough" judgement to it.
The problem is that most software teams and most engineers are very, very bad at the thing that AI needs to succeed: technical writing. Documenting the patterns, the rules, the heuristics, the SOP, the judgement; developers could barely be bothered to write comments before (which in the AI age are free, infrastructure-less memory that is always "line-of-sight" for the agent and can be used to enrich with keywords).
It's not that AI is the problem, it's that we humans are good at resolving these constraints in the real world at a human pace. AI makes that pace impossible for a human to keep up as a trailing activity. Rather teams need to invest more in technical writing and producing the corpus that AI relies on to learn the operational constraints and rules.
- illuminator83
Software is not really being more broken today than it was 10 or 20 years ago. It actually has gotten better.
I've seen the codebase of a dozen companies and worked with hundreds of peers.
There is plenty of horrific bugs and bad software outside. The reasons are plentiful too and include everything like budget constraints, management failures and engineering skill issues.
Today, the average code that even a product manager or junior engineer submits is actually excellent overall - if your processes, harness and CI etc are well designed. It is actually super easy to author software well now. Whether you build something that is actually needed and is tasteful is another matter.
99% of the security vulnerabilities being found and exploited today were created by people. Cutting most of them out of the technical details is actually good.
- rglover
Imo: the way we make software is breaking down at a systemic level.
The harsh reality is that some people/systems are adapting just fine to the new way of doing things, others are making a mess of things by rushing via vibe coding and not checking the work (either by choice or by circumstance at work). The results won't be (and shouldn't be expected to be) linear.
The 2010s brought on a very groupthinky dynamic to software dev. This led to a culture where the majority of developers just ask "what is everyone else doing." Now that we're past the blog era of development, that shared reality appears to be breaking down. Now the answer really is "whatever makes sense for/to you," but I think (anecdotally) that's freaking a lot of people and teams out.
For the first time in a long time, a "best practice" doesn't really exist.
- MiroslavPokorny
Systems are failing because everything is getting more and more complex with more dependencies on other systems.
The recent shutdown of the US airports is a perfect example of this. The current system is old, with old computers and i believe old analog networks. They worked but one small change installing a routers and some other new systems caused something bad to happen.
In Australia not that long ago, there was a overhead power line that fell and this caused the trains on that line to stop. This then had the ripple effect of causing other lines that feed the initial broken line. Traffic on roads now also drastically became worse because more people were trying to drive or catch buses and all that.
Everything is more complex and connected.
The cloud is a part of the problem, its just another layer that can and does go wrong. Previously when teams deployed to their own servers, they didnt have to also configure the cloud. They were also not a passenger on the nuances and possible failures of the cloud system from its own management technical and otherwise.
- ljm
Software wasn't exactly hard 12 years ago either, the barriers to entry were being lowered at a rapid pace. 2014 was the dawn of the software bootcamp where JS became more and more pronounced in web architecture.
I feel this piece is either more alarmist than it deserves to be, or it is late to the party.
It uses various incidents in 2026 to prove a point while dismissing those that did take place in the decade or so previous. For example, heartbleed, the log4j RCE, Rails' mass assignment DOS, Cloudflare updating a WAF rule and breaking the internet, Atlassian deleting almost 1000 of its customers' accounts and data, the Ashley Madison breach, Crowdstrike bricking their customers computers, Okta getting owned multiple times, etc.
My own point is that software became like this when we started becoming pragmatic. Nothing to do with AI or management really, we just realised, especially with web tech, that you can release something and then fix it. In the old age of getting CDs or floppies printed and distributed, that was not even remotely feasible. A similar incident in the 90s would involve a product recall or a way to get updated media from a retailer with the fix. Very expensive.
Standards have dropped and continue to do so, because we can also fix fast. It's not suddenly breaking down. If anything, it's just too centralised.
- j2kun
> This changed the balance of power between workers and management.
I think this is the core insight that I keep coming back to: technological advances always entail a transfer of political power.
We would all be better off, when evaluating new technologies and listening to their evangelists, thinking hard about who gains power and who loses power as a result of adopting that technology.
- LPisGood
Software has always been broken at a systemic level. It’s a complicated continuously changing web of abstractions and abstraction breaking hacks attempting to survive prolonged contact with reality.