<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/software-is-breaking-down-at-a-systemic-level-qs5mihe6p" -->

---
title: Software is breaking down at a systemic level | daily.dev
description: Recent outages, exploits and certificate failures share a common feature: software is breaking down at a systemic level, Jimmy Breck-McKye argues. He points to...
canonical: https://daily.dev/posts/software-is-breaking-down-at-a-systemic-level-qs5mihe6p
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Software is breaking down at a systemic level | daily.dev
og:description: Recent outages, exploits and certificate failures share a common feature: software is breaking down at a systemic level, Jimmy Breck-McKye argues. He points to...
og:url: https://daily.dev/posts/software-is-breaking-down-at-a-systemic-level-qs5mihe6p
og:image: https://api.daily.dev/og/posts/qs5mIHE6p.png
og:image:alt: Software is breaking down at a systemic level
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Software is breaking down at a systemic level

**[Hacker News](https://daily.dev/sources/hn)** · 13 min read · 0 upvotes · 0 comments

## Summary

Recent outages, exploits and certificate failures share a common feature: software is breaking down at a systemic level, Jimmy Breck-McKye argues. He points to a 2 day global Microsoft outage, the PHP2Shell exploit in PHP, an FAA ground-stop, and the eMudhra weak-key SSL incident as signs of overly complex systems. He traces the problem to cloud computing and open source, then argues AI accelerates this through 'decoherence', a term from Kristen Maevyn describing locally valid but mutually incompatible changes piling up faster than teams can reconcile them. He warns tech companies risk losing their 'organisational cognition'.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.breck-mckye.com/blog/2026/11/software-is-breaking-down-at-a-systemic-level>

## Questions this post answers

### what is the PHP2Shell vulnerability

PHP2Shell is a critical remote code execution exploit disclosed by security research firm Wiz on October 21st, affecting the PHP runtime used by an estimated 70% of the world's websites, including many WordPress sites. It stemmed from complex memory bookkeeping bugs hidden in PHP for over a decade, and sites went completely offline as engineers scrambled to patch it.

_Developers tracking critical runtime vulnerabilities like this follow patch timelines on daily.dev._

### what is software decoherence in the context of AI coding

Decoherence, a term coined by Kristen Maevyn, describes the accumulation of locally valid but mutually incompatible or redundant models within a software system, where the cost of change comes from reconciling those models and avoiding unintended side effects. It grows relative to a system's rate of change and compounds exponentially, and widespread AI-generated code is producing it at an unsustainable rate.

_Anyone weighing how far to hand coding work to AI agents can follow this debate on daily.dev._

### what caused the Shai Hulud npm supply chain attack in May 2026

Attackers compromised important JavaScript packages after exploiting a GitHub Actions CI misconfiguration that let anyone forking the projects insert compromised code upstream. When the next CI build pulled cached libraries, npm's support for install scripts let attackers hijack the projects' secret tokens, exposing how deep npm dependency chains create single points of failure.

_Teams hardening their CI pipelines against dependency attacks can track incidents like this on daily.dev._

## Community take

How the wider developer community reacted, aggregated from 1 discussion and 155 comments across hackernews (as of 2026-11-16).

**TL;DR:** Commenters are split: many dismiss the essay as nostalgic, poorly researched, or 'AI slop' that misattributes decades-old problems to AI and open source, while others find the 'decoherence' framing compelling and point to documentation, dependency sprawl, and management incentives as real root causes.

**Sentiment:** 10% positive · 35% mixed · 55% skeptical

**The case for**

- Some find the decoherence/organisational cognition framing a genuinely useful way to describe how incompatible changes pile up faster than teams can reconcile them.
- A few agree that AI accelerates existing fragility by making code and exploits cheap to produce at scale.
- Several argue the real fix is better technical documentation and 'scaffolding' so AI agents don't introduce incoherent changes.

**The pushback**

- Many say the timeline is wrong or confused—cloud computing and open source dependency culture predate the article's 10-15 year framing by decades.
- Several argue software has always been broken/complex and this is just nostalgia for a golden age that never existed.
- Critics say the cited incidents (FAA grounding, cert issue) had mundane, human/operational causes unrelated to AI or systemic decoherence.
- Some view the piece as a tangentially AI-related essay written to farm anxious upvotes rather than offer rigorous analysis.
- A recurring complaint is that business pressure for speed and cost-cutting, not AI or open source per se, is the real root cause of fragility.

**By community**

- hackernews (heated): Discussion splits sharply between those who find the decoherence thesis compelling and a large contingent calling the essay's history and causal claims sloppy or hyperbolic.

**Hottest debate:** Whether the chain of incidents and the 10-15 year timeline genuinely reflect an accelerating systemic breakdown, or whether this is nostalgic, historically inaccurate hand-wringing about problems that have always existed.

**Open questions**

- If human code review can't scale with AI-generated code volume, what alternative verification process actually works?
- Does more documentation and 'scaffolding' genuinely fix the problem, or just shift the failure mode elsewhere?
- Will AI models ever 'learn' from mistakes rather than requiring the same explicit corrections repeatedly?

**Highlights**

> The timeline is very confused, but the arc is mostly right. 1. Consolidating internet-dependent projects to a few winning cloud vendors and a dozen winning SaaS providers, made all of those project have coincident failure points. Which is great for corporate accountability ("it's Amazon's issue, not ours!") but bad for end users ("shit, EVERYTHING is down today") 2. The movement to migrate fat local-first projects towards thin internet-dependent or server-hosted ones made almost all software share those same coincident failure paths. This was good for entrenching a subscription business model and brought some end user conveniences, but meant everything being down meant everything being down. 3. Anxious and lazy dependency-first development culture ("you could never write that as well as some github rando") meant projects now had an order of magnitude more contributors but only reviewed and owned code for a surface level, making all these projects extremely vulnerable to supply chain failures and subject to constant maintenance churn. 4. Employment and team tenure continually fell so that most projects no longer have experienced owners and instead just temporary custodians. You can find the seeds of many those problems in the 1990's and earlier and you can even argue that some of them were inevitable (and even worthwhile) destinations for the industry as it evolved without an engineering guild to slow it down and insist on rigor or evidenced safety. But anybody who's been around for a few decades can attest to how these risky patterns rapidly grew into norms over the past 20 years and shifted the industry from one where any given software had some idiosyncratic bugs that users could learn to work around to one where all software had lots of bugs, many of them correlated across apps, whete failures would wash through and shut down (or make vulnerable) whole industries for hours or days, with effecrively nobody in particular to hold to account for any of it. Software has never been in a pristine "golden age", but the last 20 years built almost everything on one giant, shared house of cards that's now teetering on the brink of collapse. Better or wose, it's indisputably different than it was before.
> — [swatcoder on hackernews · 6 comments](https://news.ycombinator.com/item?id=50521616)

> I don't even know if there are decent points. This flails around in a way that's just...not super useful to spend the time trying to digest. Some things happened. AI is also happening, therefore AI is to blame (in the way that some people really believe a problem isn't a problem unless you test for it) and here's a lesson about organizational coherence or something. These essays are the real AI slop of 2026. Not authored by AI, but always trying to get attention by tangentially being related to AI and getting the anxious upvotes of the "can I turn back the clock?" crowd. And there's a humorous commonality to all of these pieces that they all start with some sort of "don't think I'm not with it. I'm with it! I hand slung an LLM off the shoulder of Orion. I watched C-beams glitter in the dark near the Tannhäuser Gate." call to authority, then pivoting to the "everything has gone to shit" spiel. We've always had a tenuously connected, barely operated network of systems. We've always had bugs and engineers doing shitty things. Every organization goes through periods of upheaval where all of the institutional knowledge is invalidated or discarded regardless. None of this is new.
> — [llm\_nerd on hackernews](https://news.ycombinator.com/item?id=50521105)

> I agree.  In my life time there hasn't been a minute of software reliability.  There's nothing special about this year or even this month. I remember the first time I installed Linux in the early 2000s and was and owned within 5 minutes of putting it on the Internet.  Desktop computers of any OS crashed regularly.  Servers crashed and needed total rebuilds. If anything software is way more reliable than it appears because the scale of computers and software is thousands of times larger than it was 20 years ago.  More things can fail because there are just more things.
> — [wvenable on hackernews](https://news.ycombinator.com/item?id=50521163)

> I don't think the point was to blame AI for PHP2Shell. It is that we've built up gigantic systems on shaky foundations: "a highly complex system made of low quality parts, where a single error can compromise everything" Of course the shaky foundations were there before AI. And before the widespread proliferation of NPM packages etc... But those increase the ease and pace at which we can build on top of the shaky foundations, they increase the rate of so-called decoherence. And there are economic and organizational incentives to keep increasing that ease and pace. That makes it more and more likely that a problem in one of the shaky foundations (whether AI-created or not) causes a system-wide failure, and at the same time results in a more and more generalist tech workforce, making it harder and harder for an organization to respond appropriately when that happens: > I believe that tech companies risk losing their “organisational cognition” - their ability to think and respond as a coherent unit. > This is the real threat: a scenario where nothing in the system is done with intent, and nobody in the system has control. We generate complexity faster than we can tame it.
> — [flufluflufluffy on hackernews](https://news.ycombinator.com/item?id=50522601)

> 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.
> — [doug\_durham on hackernews · 8 comments](https://news.ycombinator.com/item?id=50521157)

**Source threads**

- [hackernews](https://news.ycombinator.com/item?id=50520866) · 243 points · 155 comments

## Similar posts on daily.dev

- [Omnipresent availability risks in cloud software](https://daily.dev/posts/omnipresent-availability-risks-in-cloud-software-hut9n2cxk) · Surfing Complexity · 3 upvotes · 2 comments
- [Why cloud outages are becoming normal](https://daily.dev/posts/why-cloud-outages-are-becoming-normal-v2f1hpmgh) · InfoWorld · 0 upvotes · 0 comments
- [The Pulse: Time to rethink software security because of AI?](https://daily.dev/posts/the-pulse-time-to-rethink-software-security-because-of-ai--gu0kj0fef) · The Pragmatic Engineer · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#open-source](https://daily.dev/tags/open-source), [#architecture](https://daily.dev/tags/architecture), [#ai-coding](https://daily.dev/tags/ai-coding)

[View this post on daily.dev](https://daily.dev/posts/software-is-breaking-down-at-a-systemic-level-qs5mihe6p)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Software is breaking down at a systemic level","url":"https://daily.dev/posts/software-is-breaking-down-at-a-systemic-level-qs5mihe6p","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/software-is-breaking-down-at-a-systemic-level-qs5mihe6p"},"datePublished":"2026-11-16T19:18:34.046Z","dateModified":"2026-11-16T21:18:31.897Z","description":"Recent outages, exploits and certificate failures share a common feature: software is breaking down at a systemic level, Jimmy Breck-McKye argues. He points to...","image":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","thumbnailUrl":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/software-is-breaking-down-at-a-systemic-level-qs5mihe6p","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,open-source,architecture,ai-coding","timeRequired":"PT13M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Software is breaking down at a systemic level"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/software-is-breaking-down-at-a-systemic-level-qs5mihe6p#faq","mainEntity":[{"@type":"Question","name":"what is the PHP2Shell vulnerability","acceptedAnswer":{"@type":"Answer","text":"PHP2Shell is a critical remote code execution exploit disclosed by security research firm Wiz on October 21st, affecting the PHP runtime used by an estimated 70% of the world's websites, including many WordPress sites. It stemmed from complex memory bookkeeping bugs hidden in PHP for over a decade, and sites went completely offline as engineers scrambled to patch it. Developers tracking critical runtime vulnerabilities like this follow patch timelines on daily.dev."}},{"@type":"Question","name":"what is software decoherence in the context of AI coding","acceptedAnswer":{"@type":"Answer","text":"Decoherence, a term coined by Kristen Maevyn, describes the accumulation of locally valid but mutually incompatible or redundant models within a software system, where the cost of change comes from reconciling those models and avoiding unintended side effects. It grows relative to a system's rate of change and compounds exponentially, and widespread AI-generated code is producing it at an unsustainable rate. Anyone weighing how far to hand coding work to AI agents can follow this debate on daily.dev."}},{"@type":"Question","name":"what caused the Shai Hulud npm supply chain attack in May 2026","acceptedAnswer":{"@type":"Answer","text":"Attackers compromised important JavaScript packages after exploiting a GitHub Actions CI misconfiguration that let anyone forking the projects insert compromised code upstream. When the next CI build pulled cached libraries, npm's support for install scripts let attackers hijack the projects' secret tokens, exposing how deep npm dependency chains create single points of failure. Teams hardening their CI pipelines against dependency attacks can track incidents like this on daily.dev."}}]}
```

