Concern raised about normalizing failures in infrastructure layers
3 Yesterday 12:44 PM · 1d ago · 2 comments · 1 source · development 3 of 7
A commenter warns that accepting AI-generated failures at the library and infrastructure level could cascade, degrading reliability for all downstream systems and users.
“But what if we start normalizing failures in the libraries, the infrastructure, and the compilers? Everything descends into a mess of unreliability, and that slows EVERYTHING and EVERYONE down.”
adamddev1ihatethefuture.com author Article authoroli5679 AI systems engineer (ops automation)adamddev1 Commenterbenjaminsky2 Developer with validation experience
The whole story articlespostscomments the bright band is this development · numbered dots are the others · click one to jump
What people said 2 voices · verbatim
-
Excellent post. People always defend agentic/LLM-driven development by saying, "Well it's good enough", or "It works most of the time."That may be tolerable for some user-facing app. But what if we start normalizing failures in the libraries, the infrastructure, and the compilers? Everything descends into a mess of unreliability, and that slows…
-
> This leads to a normalization of inexplicability.It’s also tightly connected to a normalization of lack of accountability.> This isn't "getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem" -- you still have to do the hard part.This is probably losing the younger portion of the audience…
All 7 developments of Article on AI-driven software failures sparks debate over… →
NewswiresHacker NewsMastodonLobsters