"Isn't that the wrong way?"
"Yeah, but faster!"
It's caused my AI, it doesn't really matter who's fault it is
Basically, blaming AI slop supports a lot of pre-existing beliefs, while blaming AI hackers does not.
AI really does have the potential to make software more robust and higher quality than ever before. We can write more tests, new kinds of tests, do pen testing, do deeper analysis of code. But we're not. This, like software before, is a slop machine. It's about getting things to kind of work just enough that customers are, very temporarily, dazed, and sales are able to sell it. It's a house of cards situation and all we've done is starting stacking more cards on faster.
[1] https://apnews.com/article/faa-smart-ai-outage-08af345749c81...
[2] https://www.faa.gov/newsroom/nationwide-ground-stop-question...
Don't counter lack of credibility by spreading information you can't verify. It just muddies the water even more. There's people out there right now who think it's the AI apocalypse because a banking system is a bit slower.
> It doesn't send or receive data to the system that was overloaded, it's built to receive data from a completely different system.
You're adding your own assumptions. This is what they said:
> Q: Was this caused by SMART system?
> A: No. The two systems are not related. SMART is a data aggregator, and it does not feed information into the air traffic control system.
It doesn't feed data, they didn't say it is completely isolated, which fits what I wrote.
They absolutely have incentive to avoid investigation that the company that donated to Duffy's son in law received nearly a billion no bid contract and failed to deliver a working product.
Now don’t get me wrong, Duffy could totally be running cover for him and that is certainly the kind of corruption I expect from this administration. But the details are not quite as severe and direct as you are making them out to be it seems.
As near as I can tell, they are saying that the communication issues are not related to the new computer system (not causative) - not that the new system is physically disconnected from the communications network.
(The article is a bit confusing, using "connected" and "linked to", which could either be describing physical or causative relationships).
Q: Was this caused by SMART system? A: No. The two systems are not related. SMART is a data aggregator, and it does not feed information into the air traffic control system.
If you dig a bit further the aggregator gets its data from SWIM, which receives (but does not send) data from the system that went down. I believe it's a 1 way VPN connection that they use to aggregate data because SWIM is consumer facing as well.[1]
So unless something went terribly wrong the AI couldn't have had anything to do with it. But that won't stop it being the top narrative for all time because nobody will look into it this far and we no longer believe any official stories about anything.
Then next day they had conference where they came up with the maintenance guy.
Are you truly believe that a guy replacing a switch somewhere in Arkansas can just shut down the whole air travel in the entire country? The biggest disruption since 9/11 25 years ago? And just happened a day after SMART was deployed.
We are on tech forum, I would assume I'm talking to tech people who I hope understand how networking equipment operates.
Chernobyl was caused by a guy flipping a switch, Challenger blew up because of a faulty O-ring, etc.
I also wonder if Trump's administrations' spokespeople even realize they have a massive credibility problem, and that if they want people like me to believe anything then I have to hear it from a mid-level functionary, not a political appointee.
You say whatever makes your stocks go up and now down, and if you don't, you are stupid because it's normalized now, there are no repercussions, and if you don't someone else will.
Of course not, but that's the point of wanting to hear something from someone lower in the org chart: people lower-down on the totem-pole have fewer things within their remit that they can credibly talk about publicly; so if they ever speak of things above-their-pay-grade (like a technical team manager giving an official statement concerning departmental-level funding) then it's a signal they aren't speaking honestly.
No, just no...Chernobyl was caused by the staff doing an experiment that to put it mildly was wildly risky. They disabled safety systems with wrenches (meaning they couldn't easily be reenabled). Challenger blew up because staff at NASA ignored warnings from the people who made the O-rings. Saying these were "straws" is completely irresponsible. Attitudes like this are what cause outrages. Also, unless you are being dishonest, this is the worst string of outrages in the history of tech. There is a cause. It can be found. And unless you think in these terms, you have no business working with a production system in any way.
>Do you really believe
Thanks, conspiratorial thinking hadn't annihilated my last brain cell yethttps://www.latimes.com/travel/la-trw-laxdelays15aug15-story...
By Tami Abdollah Aug. 15, 2007 12 AM PT
U.S. Customs officials said Tuesday that they had traced the source of last weekend’s system outage that left 17,000 international passengers stranded in airplanes to a malfunctioning network interface card on a single desktop computer in the Tom Bradley International Terminal at LAX.
The card, which allows computers to connect to a local area network, experienced a partial failure that started about 12:50 p.m. Saturday, slowing down the system, said Jennifer Connors, a chief in the office of field operations for the Customs and Border Protection agency.
As data overloaded the system, a domino effect occurred with other computer network cards, eventually causing a total system failure a little after 2 p.m., Connors said.
A deployment on Friday screwed things up vs. an adversarial attack which involved multiple agency needing to cover up together with unclear motive and huge risk down the line? It's an easy pick.
Vibe coding, vibe reviewing, vibe fixing. No one has a clue how software works anymore.
Now, no one does. We ask AI to figure it out and fix it. What happens if the AI goes down?
Also, I don't think it's that "AI code is inferior" but rather devs got sloppy and no longer review code. Not to say that everyone's lazy but me---a lot of systemic/environmental factors could be the reason.
People were making memes about the GitHub unicorn a decade ago.
Much better than Azure, but that’s not a high bar.
Just because an outage doesn’t affect your specific app doesn’t mean it didn’t happen. By that logic Microsoft didn’t have an outage last week since my windows gaming pc was fine.
I know there are more incidents than that.
It could be because some critical infrastructure are due to upgrade after a long delay and this is inevitable at some point.
It could be that AI agentic hacking has pushed for some rearchitecture in faster deployment time, which may result in big outage for industry that has so much legacy and used to big bulk deployment only.
Or it could just be because we rely more on cloud infrastructure than previously.
shit programmers have always been a thing, these same shit programmers now putting output from claude straight to production
on top of this there are literally PMs getting involved and doing their own PRs, see vscode recently
This is a systemic issue that's driven by AI but the responsibility lies with leadership who are still operating on the move fast and break things mentality.
Staff-level engineers can do this work because they always have, but if they are suddenly the only ones who can in an org then they are simply overwhelmed.
Like take the Binance hack for example. A naughty hacker, instead of stealing bitcoin, could have just caused mass outage and disruption without stealing anything, but didn't because bad actors usually want some financial benefit.
Like if we learn that PII was stolen, then it's be safe to say that this was a cyber attack.
This is armchair psychology and extremely bad one because the people who have been concerned with engineering quality have been vastly outnumbered by people who just want to be able to turn their brain off and "ship fast" for probably 15+ years, and that's been reflected in reliability long before LLMs came around.
The code these systems churn out at scale is absolute trash but the financial incentives are to produce out more of it because nobody is ever actually held liable for software breaking in our age
Think system(curl) and random-if-cascades which are never reached - they removed the system(python) in this iteration though...
At this point I think AI-code is just average and probably just fine for corporate environments/SaaS (especially given what thkse produce today), but I still think infrastructure should be a) understood by humans b) produced without installing a backdoor on the dev machine and c) a human should decide what to build and be able to reign in the machine.
While there may be people arguing for that, the more relevant point is that regardless of any possible positives of AI code, there are clear negatives that are being largely ignored. Specifically in such outage cases, the volume of code being put into production with little or no review or understanding.
Clothes. Food. Appliances. Tools. Electronics.
All of these things got worse, but got WAY cheaper. All of these industries had to shed excess labor like crazy in pursuit of optimization at the cost of quality.
Why would coding be different?
No, people want to believe that it is good, despite all evidence. However the status quo will not be returning, because it will get better. The catch is that it will somehow end up in your pacemaker or the brakes on your car while it still sucks.
Somehow I knew I would find something like this on this comment section.
Nobody is claiming multiple parallel failures. They are claiming one failure that impacted multiple organizations.
What's it going to take for the AI pushers to see that maybe this isn't the road to go down.
What's new? What has been operating fine until the AI, cloud, and centralized computing came onto the scene?
My first thought for this week's outages has been that people are moving too fast and are, as the saying goes, breaking things.