Software breaking down at systemic level
lavx.hu

Software breaking down at systemic level

Archived — this story has rotated out of today’s deck. It is kept here in full.

The gist

Software engineer Jimmy Breck-McKye published an essay arguing software is breaking down at a systemic level.
It follows a Microsoft outage, an FAA ground stop and the PHP2Shell exploit.

Background

Jimmy Breck-McKye is a software engineer who writes about the industry on his blog. His essay argues that about a decade ago cloud computing (such as Amazon Web Services renting out virtual infrastructure instead of companies hiring system administrators) and open-source libraries reshaped how software is built, and that the work no longer scales safely. He says 2026's incidents share no single immediate cause but a common pattern of cascading dependency failures, and that the industry is only at the beginning of a painful phase.

How it unfolded

  1. May 2026The Shai Hulud attack compromised important JavaScript packages through npm, using a GitHub Actions misconfiguration that let anyone who forked a project inject code upstream and build scripts that stole secret tokens.
  2. Oct 21, 2026Security research firm Wiz published PHP2Shell, an exploit able to execute arbitrary code on any PHP website; the PHP runtime had hidden memory bookkeeping bugs for over a decade.
  3. About four weeks before Nov 16, 2026The PHP2Shell vulnerability took sites offline as engineers patched systems; PHP powers an estimated 70% of the world's websites.
  4. Weekend before Nov 16, 2026A two-day global Microsoft outage was followed by an FAA ground stop that halted all flights in the United States.
  5. Nov 16, 2026Breck-McKye published the essay "Software is breaking down at a systemic level" on breck-mckye.com; it was posted to Hacker News and shared on X, and daily.dev and LavX News summarized it.
  6. Nov 17, 2026Bostonmit.com published an article on 2026 software failures for small businesses citing Breck-McKye's essay.

Key terms

FAA ground stop
An air traffic control procedure requiring aircraft meeting certain criteria to stay on the ground, causing delays or cancellations.
PHP
An open-source general-purpose scripting language designed mainly for web development and embeddable in HTML.
npm
The default package manager and online repository for JavaScript packages, used with the Node.js runtime environment.

Source: Wikipedia

Who’s saying what

Author
Breck-McKye argues the internet is at a breaking point, the software is not legible enough for the responsibility placed on it, and this is the new normal rather than a blip.
Expert
Former Microsoft engineer Axel Rischin says Microsoft rushed Azure out under competitive pressure, cut corners and relied on quick fixes instead of tackling technical debt.
Analysts
Wiz says AI tools helped achieve exploits far beyond the skills of human attackers.
Caution
LavX News notes other technologists would dispute parts of Breck-McKye's picture, crediting cloud platforms, open-source libraries and AI coding tools with lowering barriers and improving productivity.

Still unverified

The exact cause and sequence of the Microsoft outage remain confidential; a network configuration failure that stopped data centers communicating is the likely origin, with a cascading failure preventing services from returning to a valid state. Reddit and Bluesky users speculated that even Microsoft engineers had no real handle on the outage's complexity. Whether the broken systems were built with AI is not divulged by companies like Microsoft.

Sources

See today’s stories in the app Gistline — free on the App Store