SCWorld.com reported that “AI has changed how quickly we can now write, revise, and prepare software for release. Coding agents can draft code, update dependencies and propose changes across repositories in minutes. Yet the systems receiving those changes are built from layers of services, legacy infrastructure, and dependencies that are difficult to see in full.” The November 16, 2026 article entitled “The Microsoft and FAA incidents show how AI accelerates change in systems we can’t afford to break” (https://tinyurl.com/4p8hpser) included these comments:
Last week’s Microsoft outage illustrates the same pattern at cloud scale. An issue introduced during an earlier network capacity upgrade surfaced after a subsequent network change, causing front-end servers to fail automated health checks. As servers were removed and clients reconnected, each reconnection triggered the exact operation that was already overloaded, creating a self-sustaining cascade — what Microsoft described as a metastable failure. The trigger was removed, but the failure persisted, because the system’s own recovery mechanisms kept amplifying the load. It’s the same issue: in complex, interdependent systems, a single change can cascade far beyond its intended scope.
AI accelerates the work entering those environments. It does not automatically accelerate our understanding of them. Coding agents can help teams build features, update dependencies and prepare fixes. GitHub reports that more than 40% of pull requests began with an agent’s first draft by September 2026, up from 17% in March. This does not mean every change reaches production faster, but it shows how quickly development practices shift. The resulting code still enters environments shaped by years of dependencies, architectural decisions, and operating constraints.
Attackers now leverage AI to build malware and automated campaigns, which increases the pressure on companies to deploy security patches from weeks to mere days. Organizations must patch more often and more quickly, increasing the volume of changes flowing through their systems — and as both the Microsoft and FAA incidents showed, it’s the change itself, not just its security intent, that can break a complex system.
What do you think?