Login
You're viewing the functional.cafe public feed.
  • Nov 14, 2026, 11:11 AM

    trouble with both the Microsoft and FAA fuckups is that both are fully explicable by normal idiot management decision making around IT

    so before we can state in an article/episode that either was caused more or less directly by the AI, and not standard pre-AI incompetence, we need more direct evidence

    it's most frustrating

    💬 23🔄 49⭐ 127

Replies

  • Nov 14, 2026, 11:13 AM

    @davidgerard is it that big a difference, given that AI and nonsense tech management come from the same culture? but: yes, it's a frustrating wait for the SuperFail.

    💬 0🔄 0⭐ 10
  • 💬 0🔄 1⭐ 6
  • Nov 14, 2026, 11:15 AM

    @davidgerard

    There is also a big incentive to hide any evidence that this is the case if true.

    So, in a way we can only look at the wider picture. Have there been more software failures as of late? Have they happened in ways that we might not normally expect?

    And even if there was evidence that it was vibe-coded software that failed some would still say that it was just "not prompted correctly" or "not reviewed enough" etc. so in the end it's always human error.

    But that's the point.

    💬 2🔄 5⭐ 23
  • 💬 0🔄 0⭐ 5
  • 💬 0🔄 0⭐ 1
  • Nov 14, 2026, 11:17 AM

    @davidgerard

    I don't feel like it's my responsibility to tell anyone "perhaps this wasn't a direct failure of AI, it's more complex than that"

    When those who have foisted AI into everything have done less than nothing to educate people about what this technology really is, what it can and can't do.

    If the general public thinks "they put AI in it and then it broke" well then. How is that different from "they put AI in it and now it's amazing" ?

    💬 5🔄 8⭐ 36
  • 💬 2🔄 1⭐ 3
  • 💬 0🔄 0⭐ 3
  • Nov 14, 2026, 11:30 AM

    @thejessiekirk @futurebird @davidgerard@circumstances.run

    Yes, why saving them from getting hoist by their own petard? They kept "putting AI into" everything, now they're blaming AI. It actually fits my agenda nicely, so who am I to dig them out of the hole they dug for themselves?

    💬 1🔄 0⭐ 2
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 1
  • 💬 2🔄 0⭐ 0
  • Nov 14, 2026, 11:59 AM

    @thejessiekirk @futurebird

    > The FAA specifically? @futurebird

    Reading the post by the OP, we see

    > trouble with both the Microsoft and FAA fuckups is [...]

    so, in the context of this thread: Why not both.

    @futurebird 's response, in my impression, though, generalized the group of perpetrators somewhat:

    > those who have foisted AI into everything

    So my "they" is this group.

    What's your problem with "they" here? What's your problem generally with those terse 1-3 word response?

    Maybe I should have just replied "Problem?"?

    💬 2🔄 0⭐ 1
  • 💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 2
  • Nov 14, 2026, 12:01 PM

    @glitzersachen @thejessiekirk

    I'm a little lost what the point of contention is here. There has been a trend of big companies adding AI features to their software and many people have said these features are unwanted or not useful. There have been claims by those who sell AI services that AI and vibe coded software can save governments and companies tons of money on wages. So, many like the FAA have rushed to adopt this technology and THEY have been reckless I think.

    💬 1🔄 0⭐ 5
  • Nov 15, 2026, 1:03 AM

    @futurebird

    > I'm a little lost what the point of contention is here

    Me, too, frankly. I should not have replied to overly general 1 to 3 word interjections. My bad^Hweird. I tend to be overzealous trying to clarify what I meant.

    💬 0🔄 0⭐ 0
  • Nov 14, 2026, 12:07 PM

    @thejessiekirk @glitzersachen @futurebird

    The FAA specifically were launching a new AI based plane tracking system at the time of the outage which they are saying was caused by overloaded routers.

    So it looks to me like their new AI system (which they have on multiple occasions said is just for optimizing routes and not going to do anything safety critical) shoved too much data into their system and knocked down everything else.

    💬 1🔄 0⭐ 2
  • 💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 9
  • Nov 14, 2026, 1:47 PM

    @davidgerard @futurebird 💯 I agree that people in general have no obligation to give these clowns any benefit of the doubt, I still want good journalists to preserve their credibility and dig for the facts. Your poll the other day about covering Humble Bundle vs MS was a good example of that.

    💬 1🔄 0⭐ 3
  • 💬 0🔄 0⭐ 2
  • Nov 14, 2026, 11:29 AM
    @futurebird @davidgerard also, normal idiot management decisions increase when the staff that might have pushed back on it have all been fired and said management is neck deep in the sycophantic llm replacements.
    💬 0🔄 0⭐ 0
  • Nov 14, 2026, 11:53 AM

    @futurebird @davidgerard yes. Don't ascribe to malice that which can be explained by incompetence. It works both ways round. And also if you substitute AI for incompetence.

    💬 0🔄 0⭐ 4
  • Nov 14, 2026, 5:23 PM

    @futurebird @davidgerard @Gizmo Funnily the last iPhone update I installed noticeably changed my autocorrect for the worse. My first thought was “ugh they’ve foisted the massive LLMs on us all” but didn’t have the hard data for it.

    And then read this: theguardian.com/technology/202

    It’s important not to always jump to conclusions, but it’s also important to trust one’s own experiences. We’ve all seen how hard and fast these jerks have pushed “AI,” we don’t exactly need peer reviewed data here.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 3
  • Nov 14, 2026, 11:23 AM

    @davidgerard I’ve read here a comparison with climate change and hurricanes.
    Found it appropriate (maybe it was you?)

    You cannot directly say that a particular hurricane was caused by climate change.

    As genAi accelerates the (often) flawed ways and processes of managing code and technical things, we’ll see an increase of the frequency of these problems/events.

    💬 0🔄 1⭐ 3
  • Nov 14, 2026, 11:24 AM

    @davidgerard Exactly. It was an 80s truism that failure is ALWAYS the fault of the people making the decisions. Always. If employees or agents fail, it’s because decision-makers didn’t do their job somewhere in the journey.

    💬 0🔄 0⭐ 2
  • 💬 0🔄 0⭐ 2
  • Nov 14, 2026, 11:47 AM

    @davidgerard Hanlons Razor for me. I can absolutely see someone doing an update on a Friday that took it down. Whether they couldn’t be arsed to check properly or were pushed to do it is just extra detail.

    💬 0🔄 0⭐ 2
  • 💬 1🔄 0⭐ 1
  • 💬 1🔄 1⭐ 1
  • Nov 14, 2026, 12:45 PM

    @davidgerard near, yes.

    No need to get into the qualifiers, but if we ban the profit motive, a lot of genuinely useful and nondestructive applications will emerge more clearly.

    💬 0🔄 0⭐ 0
  • Nov 14, 2026, 12:15 PM

    @davidgerard “never attribute to artificial intelligence that which can be adequately explained by natural stupidity”

    💬 0🔄 3⭐ 9
  • Nov 14, 2026, 12:23 PM

    @davidgerard Journalists should’ve asked the FAA what caused the “data overload” and what guarantees there are that this won’t happen again? Blaming old equipment isn’t enough of an explanation.

    💬 0🔄 0⭐ 2
  • Nov 14, 2026, 12:28 PM

    @davidgerard you are definitely correct. However, the "we are jamming generated code into everything" people and the "buffoonish fuckwits who fire 1000s to juice the stock price" people ARE THE SAME PEOPLE.

    They are responsible, and we can remind everyone of that. The mechanism of failure is downstream, and I am arguing, irrelevant.

    💬 0🔄 0⭐ 4
  • Zorrozorrobandito@aus.social
    Nov 14, 2026, 12:40 PM

    @davidgerard much as it would tickle my schadenfreude for it to be the fault of AI, I've been one of these f#$!wit managers this thread is giving a good kicking to and sometimes, shit just breaks.

    Health checks between devices fail, so they don't fall over, someone types a '1' instead of a '2' in the change, the validation test didn't cover the edge case, etc, etc

    💬 0🔄 0⭐ 1
  • 💬 2🔄 2⭐ 0
  • Nov 14, 2026, 12:59 PM

    I think the real story here is not that it happened, but how their incident response flailed around as if they don't even know their own infrastructure anymore. That's a cultural shift that can be pinned on dogmatic "AI" adoption even if you can't point directly to a PR from Claude as the trigger.

    💬 3🔄 2⭐ 0
  • Nov 14, 2026, 2:01 PM

    @boxobark.ing @davidgerard this was why I ripped the piss out of their status update that said they were "seeing encouraging signs of recovery" like they were mere passengers along for the ride with the rest of us

    💬 1🔄 2⭐ 10
  • 💬 0🔄 0⭐ 5
  • Nov 14, 2026, 2:18 PM

    @boxobark.ing Spend 50 years bulding things that mostly work, then fire all the architects, builders and maintenance staff in the hope that the power tools left on site or in cupboards can fix everything that breaks on their own because a lot of money was spent to buy them.

    💬 0🔄 0⭐ 5
  • Nov 14, 2026, 2:58 PM

    @boxobark.ing @davidgerard
    OK, so… MIcrosoft have always had a soft spot in their own understanding of their cloud infrastructure. I was a CTO of a company that was using Azure to provide data to a fleet of devices, and one time we rolled out an update that could;t read the result of a query from Azure, so it would send the request again. We only rolled out the update to about 1% of the fleet before the load on the SSH authentication servers overwhelmed the entire Azure west European infrastructure because crypto is expensive.

    Anyway the important thing was that you couldn’t see the issue on any of the customer facing dashboards - if we looked on the client side we could see more than 90% of requests failing but on the Azure side all we could see was lower than expected traffic. When we reported the problem to MS (initially as one endpoint having an issue) it took them many many hours to realise what the actual issue was taking down their entizre network. And they only figured it out because we did some investigating on our side to see exactly where in the connection things were failing. They couldn’t even see their entire service was down (for all customers, not just us) - though they finally twigged when I explained it wasn’t just the one endpoint, but all of them.

    Anyway, this situation looks very similar in its response shape, but mine happened 8-9 years ago, so I wouldn’t be too quick to point the finger at AI here.

    💬 3🔄 7⭐ 19
  • 💬 0🔄 0⭐ 1
  • 💬 0🔄 0⭐ 0
  • Nov 14, 2026, 3:58 PM

    @demallien yeah. Microsoft has somehow had an "AI first" attitude towards expertise and experience long before the AI actually existed to try to replace people with

    I think that's why Nadella embraced AI so hard - he recognized it as an actualization in tech of the company's existing attitudes

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 4
  • Nov 14, 2026, 4:56 PM

    @davidgerard @boxobark.ing

    I opened a support ticket for Azure (unrelated to M365 outage) about a preview feature not enabling. After the second AI slop repeating back everything I wrote, and hallucinating how you even enable preview features, I told the bot to get me a person who knows the system.

    Two days later I finally find the relevant Learn article on my own, and fix the issue (wrong feature selected due to crappy documentation). The bot never responded.

    💬 0🔄 1⭐ 0
  • 💬 0🔄 0⭐ 1
  • Nov 14, 2026, 1:25 PM

    @davidgerard For the Microsof outage, my personal suspicion is it’s both. Years of underinvestment paired with a brain drain as the “AI transformation” has taken root. The people who know how the system works, might have been able to limit the impact or recover it quicker aren’t there any more. Whoever is left is overloaded and only has AI to “guide” them.

    A friend recently called this “creating experience gaps” and I wouldn’t be surprised to see phrases like that show up in a lot more post-mortems over the next few years.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 1
  • Nov 14, 2026, 2:54 PM

    @davidgerard I don't know about Microsoft, but the FAA failure sounds like bog standard systems rollout by people who have no business doing a systems rollout

    Even if you take their words at face value and don't read the subtext- they rolled out a system without doing proper testing of any kind and apparently didn't do a phased rollout. For a life or death system? Don't let these people near a computer ever again

    💬 2🔄 4⭐ 0
  • 💬 1🔄 0⭐ 5
  • Nov 14, 2026, 3:49 PM

    @davidgerard I also will bet that the new systems make no attempts to be efficient and they put systems coded as modern web based systems on networks built to handle 1980s level network code.

    When they say the old systems were "overwhelmed" by the new systems, bloated modern network code immediately came to mind

    And one thing ai agents love to produce is network code that uses far more bandwidth than it should need. Because that's the shit it has been trained on

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 3
  • 💬 0🔄 0⭐ 0
  • Oregon Slimoregon_slim@c.im
    Nov 14, 2026, 2:59 PM

    @davidgerard

    Did you see the presser yesterday where they blamed the old software that still worked for not being able to handle the data that the new software was hurling at it, and blamed the Congress (100% controlled by their coterie) for not giving them $50 billion to do it right? That's like blaming vandalism when you learn the dumb way that a reflecting pool is not a parade route. They scoffed at the idea that one could expect old systems to work smoothly with new systems. That's exactly the plan that they tried to get away with. Fortune favors the bold, but so do the Darwin Awards, the National Enquirer and the Police Gazette.

    💬 0🔄 0⭐ 1
  • Nov 14, 2026, 4:21 PM

    @davidgerard I think we have a deep national shift in risk management philosophy. Historically, we view infrastructure risk like NASA does. Put a ton of research in up front to understand all variables, and manage redundancies in hopes to avoid catastrophic failure.

    We're now in the SpaceX(Musk) Iterative Development era with little or no redundancies. Failure is expected. Manage fallout. The "You have to break a few yokes" philosophy.

    Its deeply wreckless and callus.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0