I think he's just pointing out that AI has made news of IT failures "more interesting" and thus, more reports are getting out where in the past, they'd not be interesting.
I think you went off somewhere else.
Re:NSA Internal Network Down
by joe_the_user on Tuesday November 17, 2026 @01:38PM
(#50536086)
The OP is giving an alternate explanation of the general phenomena that this headline is a part of. Nothing wrong with describing the framework that software "drift" is happening in.
Which is to say, a parent post here on HN doesn't narrow the topic to it's focus. That's what makes discussion here interesting.
Re:NSA Internal Network Down
by joe_the_user on Tuesday November 17, 2026 @01:13PM
(#50535679)
I don't necessarily agree about the warnings. AI often gives me "now be careful" warnings about it's output along with the caveat at the bottom of each ChatGpt page.
I suspect the situation is that AI's caveats are just easier to ignore than a person's warnings. Plus all the other factors you list. Also, AI tends to give a person the kind of communication they ask for. I always ask for options but I suspect other people ask for just answer and so they get them.
Yeah I think most people just prompt AI to close gaps until it gives a green light to go ahead.
Asking the coin-tossing machine if it's safe until it says it's safe. :)
Re:NSA Internal Network Down
by clickety_clack on Tuesday November 17, 2026 @01:50PM
(#50536304)
10 years ago, most work happened in Word or Excel on a desktop app on your computer, so you weren’t depending on a constellation of cloud based SaaS vendors. If outlook went down for an hour, you’d just continue working without the disruption of an inbox. Now, the path to do your work requires online vendors to be online, so if they go down you’re blocked.
AI is tuned to speak confidently and ship independently; it is rare that it will suggest that one go back to a broad survey of stakeholders to ensure no Chesterton's Fence is being torn down (https://fs.blog/chestertons-fence/). "I've read the documentation and logs, and nothing suggests this system needs these legacy capabilities/components" is something we hear all day, and it is a siren's song if there ever was one.
Couple that with a general (and valid!) consensus that modernization of legacy systems must be accelerated for a variety of reasons - to mitigate this new and continuing "Black October" of hyper-agile agent-driven cyberattacks (whether the network is public or private); to have more flexible infrastructure for new features to stay ahead; to allow human teams to show their efficacy in a world where technology jobs are increasingly at risk - and you have a perfect storm where change management is no longer what it once was.