I see this as following for many failing organizations.
- We used to take 1 month per patch. Mostly manual process.
- With AI, we implemented the process of 2 patches per week. Same old process. Solid verification is missing. Rollback is manual.
People are reading the article, or the first few sentences, right?
> Wall Street executives and the National Security Agency have told members of Congress that this week’s widespread tech outages were caused by attempts to fix vulnerabilities identified by artificial intelligence, according to three sources familiar with the private conversations.
aka, possibly rushed patches/patching, in response to AI-discovered vulns. As far as I can tell "AI-authored patches" is not really mentioned in this article. (Whether that's true or not, I won't speculate, but it's weird to see the several comments just jumping on "AI patching bad".)
I’m not sure where people got the idea that just because AI can write code now, it doesn’t need to be reviewed or tested.
> Bank CEOs, NSA Tell Congress That AI-Driven Patches Are Behind Outages
Don't know about the causal relationship but the correlation between major software outages and devs turning their brains off and beginning to use LLMs is interesting.
> They’re trying to push through a lot of patches all at once — more than the system was designed for.
How is a system designed for a certain rate of patches?