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 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.
@mitchellh 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.
-
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.
@mitchellh 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. -
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.
@mitchellh 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.
-
@mitchellh 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.
Same experience here. And it's presented like facts. When asking, they point out that [talky program used] provides sources (which they of course never read).
I fear that as society we're to blame at least party after "I googled it" became an accepted answer without actually naming the pages found by the search.
-
R relay@relay.mycrowd.ca shared this topic
-
@mitchellh 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 ... ?
@slacy @mitchellh yep. Because specs that covered everything (aka waterfall) failed so perfectly before. Why not try it again, this time with an algorithm that has no comprehension to tell you that your spec is trash.
-
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.
@mitchellh 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.
-
R relay@relay.infosec.exchange shared this topic
-
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.
@mitchellh 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".
-
@mitchellh 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.
@landelare @mitchellh it's the new LetMeGoogleThatForYou butt worse
-
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.
@mitchellh @briankrebs 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.
-
@mitchellh @briankrebs 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.
@mitchellh @briankrebs I wholeheartedly believe that LLMs take away the most important part of programmers‘ jobs: creating something they can be proud of. And it’s replaced by instructing „someone“ else on creating the software and reviewing the result. Of course they’ll care less abut the quality if they weren’t the ones who created it. It’s like everyone has become a manager, and no-one is the actual creator of the systems being built.
-
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.
-
Same experience here. And it's presented like facts. When asking, they point out that [talky program used] provides sources (which they of course never read).
I fear that as society we're to blame at least party after "I googled it" became an accepted answer without actually naming the pages found by the search.
@ChristianRiegel @landelare @mitchellh I posted this a year ago: https://mastodon.nu/@ahltorp/114454413624506937
-
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.
@mitchellh We have to stop using human terms to help the tech bros anthropomorphize these pieces of crap. The AI malfunctioned. It’s a machine.
-
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.
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:
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:
The Human Cost of 10x AI Productivity
AI tools increased code review volume by 98% but your brain still runs at 10 bits per second. The physical toll on senior engineers is measurable.
(techtrenches.dev)
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.
-
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:
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:
The Human Cost of 10x AI Productivity
AI tools increased code review volume by 98% but your brain still runs at 10 bits per second. The physical toll on senior engineers is measurable.
(techtrenches.dev)
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.
The conversation I was totally not ready for where the ones where people being totally earnest told me they believed LLMs are intelligent or can reason.
I knew inherently this was wrong b/c I spent time understanding how they work in detail but actually explaining it in a plain way stumped me w/o thinking more deeply about it.
If you spent time learning about Russell, Wittgenstein, Hilbert, Godel and others you should see the flaws in thinking and get why induction can't get you there but that is hard row to explain to anyone who is not familiar.
So I think these two articles hit the right spot:
Shafik Yaghmour (@shafik@hachyderm.io)
Attached: 2 images LLMs Are Not Intelligent: https://joshbrake.substack.com/p/llms-are-not-intelligent It is a deep rabbit hole. #ai
Hachyderm.io (hachyderm.io)
and
Shafik Yaghmour (@shafik@hachyderm.io)
Attached: 2 images "Large language mistake" "Cutting-edge research shows language is not the same as intelligence. The entire Al bubble is built on ignoring it.": https://buildcognitiveresonance.substack.com/p/large-language-mistake Down the rabbit hole I go. #ai
Hachyderm.io (hachyderm.io)
but you can go deep on this one.
-
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:
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:
The Human Cost of 10x AI Productivity
AI tools increased code review volume by 98% but your brain still runs at 10 bits per second. The physical toll on senior engineers is measurable.
(techtrenches.dev)
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.
@shafik @mitchellh A cursory reading of Robert Pirsig's "Zen and the Art of Motorcycle Maintenance" betrays how quality has its own ineffable quality. KLOCs are not a useful metric often; McCabe's Cyclomatic Complexity is where I'd start. Dijkstra brought the wisdom yet as Adam Smith has been selectively quoted in econo-political argument, Dijsktra seems to be selectively quoted by members of the deep-learning community.
-
@mitchellh We have to stop using human terms to help the tech bros anthropomorphize these pieces of crap. The AI malfunctioned. It’s a machine.
@CStamp @mitchellh Kate Crawford warns about this ~7 pages into "Atlas of AI" and @HalvarFlake covered the topic well last July: https://addxorrol.blogspot.com/2025/07/a-non-anthropomorphized-view-of-llms.html
-
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.
@mitchellh @DukeDuke hadn't occurred to me that the AI psychosis may be a factor driving the enshittification of tech, but that makes perfect sense. I swear, COVID and genAI are our civilization's answer to Romans' lead pipes updated for the 21st century
-
@shafik @mitchellh A cursory reading of Robert Pirsig's "Zen and the Art of Motorcycle Maintenance" betrays how quality has its own ineffable quality. KLOCs are not a useful metric often; McCabe's Cyclomatic Complexity is where I'd start. Dijkstra brought the wisdom yet as Adam Smith has been selectively quoted in econo-political argument, Dijsktra seems to be selectively quoted by members of the deep-learning community.
any metrics that solely look at the code will not tell you what you need to know.
The whole lifecycle has to be measured, including code review, bug reports, rates of errors over time etc
-
@mitchellh @briankrebs I wholeheartedly believe that LLMs take away the most important part of programmers‘ jobs: creating something they can be proud of. And it’s replaced by instructing „someone“ else on creating the software and reviewing the result. Of course they’ll care less abut the quality if they weren’t the ones who created it. It’s like everyone has become a manager, and no-one is the actual creator of the systems being built.
@lizbian @mitchellh @briankrebs Regarding the anthropomorphization argument: merely calling into question the nomenclature of "AI Alignment" is enough to trigger contempt/threat reactions in some "AI" proponents, betraying it has developed a pseudo-religious property. When people are unable to step to one side and consider the technology in its wider context, regardless of whether they were "one-shotting" code subsystems with e.g. GLM 5.1, demons form.
