Hacker News new | past | comments | ask | show | jobs | submit
We've had spectacular infrastructure outages for decades; I think that a cluster of incidents in one week doesn't establish that AI is directly responsible for declining reliability.

IMO, the issue is that AI is reducing the cost of building and modifying systems much faster than it's reducing the cost of understanding them. For example, an engineer can work on a problem or project for a week that could otherwise be done by AI in an hour or so. But, that week spent was not "wasted time"; it was understanding what it is they are building, discovering undocumented assumptions, knowing about different dependencies, developing intuitions about the system and how it works, etc.

This causes comprehension debt. Yes, the system does ultimately work, the tests also pass. But the level of comprehension goes down significantly.

That said, AI can also help reduce this debt by asking it what you need help understanding.

A good blog post on this: https://larsfaye.com/articles/ai-coding-will-prevent-experti...

> We've had spectacular infrastructure outages for decades

Absolutely.

However, we've also never poured more in, to such centralised infrastructure.

I've actually never worked in any company that has had a communications outage for 36 hours in my life; and I've worked in places we had a dancer IRCd running on an old laptop under the faux floor in the server room with Solaris as the main communications tool... thing is: it was so simple, when it went down we just fixed it.

Technology companies have very successfully convinced us that we should outsource responsibility, because there are economies of scale. Then they ask for a free pass because "scalability is hard".

You don't get to say scalability is hard when you've been pushing and propagandising centralisation for over a decade, while having thousands of staff on million-dollar yearly TC packages.

Everyone here will say "nobody got fired for buying x- because everyone does" (Slack, IBM, Microsoft, AWS), and you can use it as an excuse... but you know what happens when we over-rely on something like that and it fails?

Economic crashes. That's exactly how the 2008 financial crisis happened, everything depending on something that had "absolved" responsibility. Such a thing has ruined the prospects of an entire generation of people, and I'm actually becoming really upset that we think we're being clever bastards because "oh hum, well, I can't be held responsible for total systematic collapse, everyone else was doing it!"

{"deleted":true,"id":50564222,"parent":50556529,"time":1795113517,"type":"comment"}
loading story #50554338
Skills, metaskills, and learning by doing.

When you change a system directly you learn the underlying nature of the system and your toolset for making changes. Guide a third party toward making the changes and you learn the nature of the interaction and your toolset for evaluating the outcome of changes.

Does the distinction matter? Depends on your perspective I suppose.

loading story #50559962
> We've had spectacular infrastructure outages for decades

And yet, in the entire history of electromechanical switching in the Bell System, no central office was ever out of action for more than 30 minutes for any reason other than a natural disaster. (With one late exception, a major fire in New York City in 1975.[1])

That was achieved by design. Electromechanical telephone switches were designed to have no single point of failure. That was achieved in practice. Failures occurred all the time, but the problem was confined to a small group of lines, if not a single line. I'm not going to go into how that was done; read up on #5 crossbar if you're interested. Even complex functions such as long-distance routing had backdowns to static routes stored in read-only devices, in case the telco equivalent of BGP failed.

That reliability record has not continued into the computer era.

[1] https://en.wikipedia.org/wiki/1975_New_York_Telephone_exchan...

No need to go that far back in time: the GSM system was also flawless, until "the convergence", and is still orders of magnitude more robust than the Internet.

The reason I believe has to do with cloud sitting on top of layers and layers of abstractions, reused for "simplicity" or short time to market rather than because they fit the domain.

Given the history, it’s a bit ironic that we’ve managed to make the internet more centralized and less resilient than the phone lines.
This is the main thrust of the article, if you read the whole thing.
loading story #50563170