Software engineer Jimmy Breck-McKye published an essay this month arguing that software is breaking down at a systemic level. His point is that this year’s outages and breaches are not a run of bad luck. They come from systems built out of so many borrowed parts that nobody fully understands them anymore, and AI coding tools are speeding that up. We think he is mostly right. For a small business in Boston, the practical answer is not to panic or to stop using the cloud. It is to know what you depend on, assume parts of it will fail, and make sure someone can explain how your own setup works.
Key takeaways
- Most of the software a small business runs is assembled from other companies’ code, services and updates. A failure several layers away can still stop your office.
- 2026 has had several examples: a Microsoft 365 email outage across the Americas, critical PHP flaws that sat in code for years, and a supply chain worm that spread through developer tools.
- You can’t fix the industry, but you can list what you depend on, plan for each piece being down for a day, and patch quickly when it matters.
- Documentation and a person who understands your environment are worth more now, not less, as more code is written with AI help.
What is the argument?
Breck-McKye’s essay makes three claims. First, modern software is stacked on cloud platforms and open source packages that each depend on dozens of others, so a single mistake can cascade. Second, fewer people hold the whole picture of a system in their heads, because the work has been flattened into generalist roles and handed to tools. Third, AI makes this worse in a quiet way: each AI-written change can look reasonable on its own while the system as a whole stops making sense. He calls that decoherence.
You don’t have to agree with every part of it to see the pattern in the news this year.
What has actually broken in 2026?
A few incidents from the last several months show the same shape.
- Microsoft 365, November 12. Outlook and Exchange Online went down for a large part of the day across the Americas, with Teams and Copilot also affected. We wrote up what happened and what to do next. Nothing was wrong with anyone’s office network. It was a problem inside Microsoft’s infrastructure.
- PHP2Shell, October. Two critical flaws in PHP, the language that runs a large share of websites including most WordPress sites, allowed attackers to run code on web servers without logging in. PHP shipped emergency patches on October 21 and the flaws were being exploited in the wild within days.
- Mini Shai-Hulud, May. Attackers got into the automated build pipeline of a popular open source project and used it to publish poisoned versions of over 170 npm and PyPI packages, according to the Cloud Security Alliance. The malware stole cloud and GitHub credentials from developer machines. Because the packages were published from the real pipeline, they passed the usual authenticity checks.
- eMudhra, October. A certificate authority that browsers trusted turned out to have created eight intermediate certificates with private keys weak enough to guess. Browsers and the company pulled trust, and the company has since left the public certificate business.
None of these were caused by a small business doing something wrong. All of them could still reach a small business through its email, its website, its software vendors or the tools its developers use.
What does this mean for a small business?
Your company runs on a long chain of other people’s work: Microsoft 365 or Google Workspace, a line-of-business app, a website on WordPress, a payroll service, a phone system, maybe an accounting package hosted somewhere else. Each of those runs on its own chain. You will never see most of it, and you don’t need to. What you need is to know which links would stop your business if they broke, and what you would do for a day without each one.
This is also where AI comes in for a typical office. Staff are already using AI tools to write scripts, build spreadsheets with formulas nobody checks, and set up automations between apps. Those can save real time. They also create small pieces of your operation that nobody actually understands. If the person who set it up leaves, or the AI output was subtly wrong, you find out at the worst moment.
What should you do about it?
- Write down what you depend on. List the ten services your business can’t run without, who the vendor is, who at your company owns the relationship, and where the admin login lives. One page is enough.
- Plan for each one being down for a day. For email, that might mean a phone tree and a shared contact list stored outside Microsoft 365. For your line-of-business app, it might mean a printed schedule or a read-only export. Our outage write-up has a short version of this plan.
- Patch fast when it matters. PHP2Shell went from patch to active attacks in under a week. If your website host or developer can’t tell you within a day whether a critical flaw affects you, that is worth fixing before the next one.
- Keep backups you control. Microsoft and Google keep your data available. They don’t promise to give you back last Tuesday’s version of a file someone deleted. A separate backup of mail, OneDrive and SharePoint is cheap insurance.
- Know what your own AI-built tools do. If someone on your team built a script, macro or automation with AI help, have them write two sentences on what it does and where it runs. Review anything that touches money, customer data or permissions.
- Make sure someone understands your setup. That can be an internal IT person, an outside provider or both. What matters is that your environment is documented well enough that a competent person could pick it up tomorrow.
Frequently asked questions
Should we move off the cloud because of outages like this?
For most small businesses, no. Microsoft and Google still run email more reliably than a server in a closet would. The better move is to plan for the rare day they are down and keep your own backup of the data.
Does PHP2Shell affect our website?
If your site runs on WordPress or another PHP application and your host has not updated PHP since October 21, 2026, it may. Ask your host or developer which PHP version the site runs and whether it is a patched release.
Is it safe for our staff to use AI to write scripts or automations?
It can be, with rules. Keep AI-built tools away from payments, permissions and customer data unless someone who understands the code has reviewed them, and keep a short note of what each one does and who owns it.
Not sure what your business depends on?
That list of critical services, owners and backup plans is part of our free 30-minute IT assessment. We go through it with you and give you the findings in writing, whether or not you work with us afterward. Book a free assessment or call us at (617) 322-5155.
— Boston Managed IT