And as far as air traffic is concerned, they’ve been trying to strangle it since at least 1980. Canada has a privatized system, so it’s possible to create such things but that is a matter of political will not money.
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.
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!"
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...