Elektrine lite

← Feed

@mitchellh@hachyderm.io

Post #2846502

2026-05-15 20:17 UTC

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

Replies (17)

  • @pojntfx@mastodon.social 2026-05-15 20:36

    @mitchellh@hachyderm.io I would love to see someone commission a study on this. It _feels_ like things are in general getting less reliable atm, esp. the stack I rely on for work (GitHub, Linear, Slack, Notion, VSCode, ), but then I can't find any data on any of it.

    Open ##3068898

  • @bnferguson@ruby.social 2026-05-15 20:41

    @mitchellh@hachyderm.io God, ALL of this. I worry, too. I really feel "resilient catastrophe machine".

    Open ##3068933

  • @tobinbaker@discuss.systems 2026-05-15 21:06

    @mitchellh@hachyderm.io that's an interesting analogy, feels like both vibecoding and "resilience engineering" tend to mask systemic risk by superficially and temporarily mitigating the symptoms

    Open ##3068934

  • @nickynah@rebel.ar 2026-05-15 21:13

    @mitchellh@hachyderm.io I’ve been thinking a lot about this, and my personal conclusion is that the raise of the attention economy has made nuanced discussion virtually impossible, so nuanced topic (all important problems are nuanced) are impossible to discuss, because all people see is “number go up” The only solace I have is that this is unsustainable, and it will collapse, costing us a lot, but it will collapse

    Open ##3068935

  • @slacy@mastodon.social 2026-05-15 21:37

    @mitchellh@hachyderm.io The story I've heard is the "well, we just rewrite the entire thing every six months so there's no point in fixing/improving because the next iteration/generation will be that much better as the agents improve." I can actually sort of see this, and it's somewhat along the lines of "spec-driven-development" but ... ?

    Open ##3068937

  • @mitchellh@hachyderm.io People whom I've believed to be highly intelligent would unironically send me crap like "Claude said X" or "Gemini said Y", honestly implying that they're sharing useful information with me. It's insane.

    Open ##3068947

  • @pgoultiaev@hachyderm.io 2026-05-15 22:36

    @mitchellh@hachyderm.io Unfortunately, changing a very convinced person’s view to a different perspective is almost impossible. Not enough things have gone wrong due to AI psychosis for people to augment their perspectives and be open to helpful discussions… yes, databases have been wiped etc., but these examples are (unfortunately) seen as one-offs. I feel like discussing the approach to how to apply AI in the best way can bring perspectives together instead of battling an opposing view.

    Open ##3068953

  • @lkanies@hachyderm.io 2026-05-15 22:48

    @mitchellh@hachyderm.io there are so many different crazy things people believe now, almost implicitly. The big one I keep thinking about is that people just seem to think code longevity has zero value any more. Like, we always knew code that doesn’t change for a long time is maybe a bad sign, that it is rotting. But it is also a good sign that it is likely more stable, secure, and valuable than new code. But so many people now just seem to think it is always a good thing to be able to change any code any time. They don’t talk about the gradual hardening that is no longer happening, or the ability for other parts of the system to evolve more because this part is so stable. I assume that over time our industry will learn how to talk coherently and intelligently about all this. But we’re obviously a long ways from there, and there’s a lot of destruction going to happen between then and now.

    Open ##3068956

  • @mitchellh@hachyderm.io I have a client that used Claude's API capability to pull some info out of the system and regurgitate it as a webpage. They were "blown away" by it. Never mind that I, the consultant and subject matter expert, already provided a detailed report months ago that they completely ignored. They then asked if we had Claude and if not that we should seriously consider getting it. I think the word that came to mind was that it felt denigrating.

    Open ##3068957

  • @jamesb2147@infosec.exchange 2026-05-15 23:09

    @mitchellh@hachyderm.io I don't necessarily disagree, but "resilient catastrophe machine" feels an awful lot like Salesforce (and a lot of the rest of the tech industry). I mean, you do have to strike a balance, but in my experience, moving faster has very frequently been the economic winner, even at the expense of quality. I say this as someone that abhors the wasted hours fixing systems that weren't designed properly, and the lost business from features that never actually worked but were already sold. I don't want my experience to teach this lesson, and I desperately want someone to convince me otherwise.

    Open ##3068958

  • @nivex@tenforward.social 2026-05-15 23:11

    @mitchellh@hachyderm.io There as an adage older than tech itself: "An ounce of prevention is worth a pound of cure." You don't have to recover from bugs you never shipped in the first place, regardless of how fast you think you can do it, not to mention dealing with lingering side effects once the service is "recovered".

    Open ##3068959

  • @lizbian@chaos.social 2026-05-15 23:44

    @mitchellh@hachyderm.io @briankrebs@infosec.exchange I’ve found myself talking to certain colleagues very carefully when AI comes up because I have that uncanny feeling that they might become overly defensive if I share my honest criticism of AI. It’s the same behaviour when talking about that difficult colleague that everyone likes. Like, talking to people who are in a toxic dynamic. But the dynamic is with LLMs. There have been enough cases that we can say that LLMs may abuse their users to keep them engaged.

    Open ##3068960

  • @mitchellh@hachyderm.io Ask them what they will do when their cloud is down. Handwaving ensues. Fog rolls in.

    Open ##3364849

  • @lispi314@udongein.xyz 2026-05-16 00:04

    @mitchellh@hachyderm.io MTTR implies that there ever is recovery to start with. If it's always failing/incorrect (and it is), that immediately breaks down. MTBF in the immediate is asymptotic because it's always failing.

    Open ##3364850

  • @CStamp@mastodon.social 2026-05-16 00:27

    @mitchellh@hachyderm.io We have to stop using human terms to help the tech bros anthropomorphize these pieces of crap. The AI malfunctioned. It’s a machine.

    Open ##3364851

  • @shafik@hachyderm.io 2026-05-16 00:49

    @mitchellh@hachyderm.io There are some good folks writing some solid pieces. This one has nice graphs laying out the long-term costs in a way that I think most folks can absorb: https://www.jamesshore.com/v2/blog/2026/you-need-ai-that-reduces-your-maintenance-costs and honestly if you have spent any time thinking about the software development lifecycle seriously this should hit home b/c there is nothing revolutionary there. This one talks about the hard cognitive limits human have: https://techtrenches.dev/p/the-human-cost-of-10x-how-ai-is-physically and why this means that lines of code is not the correct measure of productivity and in fact this is a terrible measure. What is there I think is less commonly well known and may take a bit more thought to get in the big picture sense. Anyone who has spent time thinking about software quality, you should be nodding your head b/c it is correct.

    Open ##3364852

  • @mitchellh@hachyderm.io I have people I’ve been (or am) *very* close to I’ve had to say “we don’t talk about AI” with.

    Open ##3364854