Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. 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.

Scheduled Pinned Locked Moved Uncategorized
82 Posts 64 Posters 77 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • bms48@mastodon.socialB bms48@mastodon.social

    @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.

    bms48@mastodon.socialB This user is from outside of this forum
    bms48@mastodon.socialB This user is from outside of this forum
    bms48@mastodon.social
    wrote last edited by
    #32

    @lizbian @mitchellh @briankrebs Prof. Michael Wooldridge has expressed clearly, for wider dissemination on his Royal Society lecture from February, many of the problems recapitulated in this thread; the zingers are 30m in or so and he flies cover very carefully at the start. This is where I'd point civilians. But the odd Condescending Wonka meme may help. https://www.youtube.com/watch?v=CyyL0yDhr7I

    1 Reply Last reply
    0
    • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

      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.

      W This user is from outside of this forum
      W This user is from outside of this forum
      w_gulley@mstdn.social
      wrote last edited by
      #33

      @mitchellh Were you alive in the 1970's when GM's Van Nuys plant produced so many malfunctioning cars that they couldn't repair them fast enough to keep them from piling up on the lot there in Van Nuys? We'll fix them later, just get them off the line was the mantra. But they didn't. Fix them later. Sound familiar? Yes, but this time it will be different. Riiiiight.

      1 Reply Last reply
      0
      • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

        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.

        klausfiend@mstdn.caK This user is from outside of this forum
        klausfiend@mstdn.caK This user is from outside of this forum
        klausfiend@mstdn.ca
        wrote last edited by
        #34

        @mitchellh I used Claude today to verify a change I'd made to a piece of Python code. Instead of using a statically defined tuple of valid subclass names, it suggested using a pattern I found later on StackOverflow that it stated was "drift-proof" (which is what I wanted, to reduce toil in the code base.)

        It offered me something that 1) failed right away due a missing import it didn't mention in its suggestion and 2) the code it suggested returned an empty tuple when I used the suggested pattern. I shrugged, and reverted to the manual method I had originally written.

        Claude is arguably the most robust model for software engineering and I find it does dumb shit _all the fucking time_ ... and so many people just blithely assume it's right without checking.

        1 Reply Last reply
        1
        0
        • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

          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.

          richpuchalsky@mastodon.socialR This user is from outside of this forum
          richpuchalsky@mastodon.socialR This user is from outside of this forum
          richpuchalsky@mastodon.social
          wrote last edited by
          #35

          @mitchellh

          It's not "AI psychosis". It's just bad programmers and people who don't know anything about anything, and that suddenly has been revealed now that they don't have to pretend to do anything.

          1 Reply Last reply
          0
          • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

            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.

            cyberwitch@goingdark.socialC This user is from outside of this forum
            cyberwitch@goingdark.socialC This user is from outside of this forum
            cyberwitch@goingdark.social
            wrote last edited by
            #36

            @mitchellh I toss the occasional "Where's your Ed At?" podcast their way. Sometimes the best grounding force is a Brit swearing in your ear for 40 minutes about trading made-up fart tokens.

            1 Reply Last reply
            0
            • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

              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.

              gatesvp@mstdn.caG This user is from outside of this forum
              gatesvp@mstdn.caG This user is from outside of this forum
              gatesvp@mstdn.ca
              wrote last edited by
              #37

              @mitchellh I think you are on to something being up in corporate behaviour, I'm not sure if it's attributable directly to "AI psychosis" as much as companies leveraging the robots to serve their basest instincts.

              You and I can look at a system like GitHub or Windows and say that it has gone to complete trash. We can say that the cost of the downtime (for us) exceeds the value of the new features coming in.

              But that math appears to be different for their customers. We're not seeing a mass exodus from GH or from MS products. All of that MTTR math is proving out. Failures are way less costly than developers kept claiming. Shipping is way more important.

              Corporations are finally unleashed to ship trash and keep collecting subscriptions at an unprecedented rate.

              Line must go up 📈

              I personally think this is all bad. But I don't know that it's "AI psychosis" rather than just basic "corporate psychosis".

              1 Reply Last reply
              0
              • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

                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.

                hopeless@mas.toH This user is from outside of this forum
                hopeless@mas.toH This user is from outside of this forum
                hopeless@mas.to
                wrote last edited by
                #38

                @mitchellh Let's hope OP never decides to get into politics. Because demonizing everyone who reached a different conclusion than him with "psychosis" came very naturally. There's no justification given for the use of the word in this context either.

                Link Preview Image
                concern troll - Wiktionary, the free dictionary

                favicon

                Wiktionary (en.wiktionary.org)

                unlofl@mstdn.socialU 1 Reply Last reply
                0
                • hopeless@mas.toH hopeless@mas.to

                  @mitchellh Let's hope OP never decides to get into politics. Because demonizing everyone who reached a different conclusion than him with "psychosis" came very naturally. There's no justification given for the use of the word in this context either.

                  Link Preview Image
                  concern troll - Wiktionary, the free dictionary

                  favicon

                  Wiktionary (en.wiktionary.org)

                  unlofl@mstdn.socialU This user is from outside of this forum
                  unlofl@mstdn.socialU This user is from outside of this forum
                  unlofl@mstdn.social
                  wrote last edited by
                  #39

                  @hopeless Its a metaphor and the post explains their concern pretty well

                  Can anyone help me find the downvote button here? My fedi client still only has one for "fav"

                  immibis@social.immibis.comI 1 Reply Last reply
                  0
                  • pojntfx@mastodon.socialP pojntfx@mastodon.social

                    @mitchellh One of the best descriptions I've heard lately was that it feels like "losing coworkers to dementia" as people adopt it, where everyone feels like they know everything, but when you talk with them in person or there is a problem that needs to be fixed _now_ it becomes very clear that the capability to do that has atrophied basically completely

                    johannab@cosocial.caJ This user is from outside of this forum
                    johannab@cosocial.caJ This user is from outside of this forum
                    johannab@cosocial.ca
                    wrote last edited by
                    #40

                    @pojntfx @mitchellh holy goats, hadn’t hear that dementia analogy before but that is exactly it. I’ve lost elder family to dementia and when you’ve lived with it you realize that it is so much more than “forgetting”, it is literal decay of executive, cognitive capability. Not sure i hould say thanks for sharing that, i’m now going to see it everywhere. 😳

                    1 Reply Last reply
                    0
                    • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

                      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.

                      nikclayton@mastodon.socialN This user is from outside of this forum
                      nikclayton@mastodon.socialN This user is from outside of this forum
                      nikclayton@mastodon.social
                      wrote last edited by
                      #41

                      @mitchellh does this mean you're going to remove the "maintainers are exempt" language from https://github.com/ghostty-org/ghostty/blob/main/AI_POLICY.md ?

                      1 Reply Last reply
                      0
                      • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

                        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.

                        tmcfarlane@toot.communityT This user is from outside of this forum
                        tmcfarlane@toot.communityT This user is from outside of this forum
                        tmcfarlane@toot.community
                        wrote last edited by
                        #42

                        @mitchellh memories of the "microservices fix everything" brigade. We threw out easy integration testing and embraced distributed SPoFs

                        1 Reply Last reply
                        0
                        • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

                          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.

                          jasongorman@mastodon.cloudJ This user is from outside of this forum
                          jasongorman@mastodon.cloudJ This user is from outside of this forum
                          jasongorman@mastodon.cloud
                          wrote last edited by
                          #43

                          @mitchellh Also, the data's showing very clearly that MTTR is getting longer, probably because of growing comprehension debt.

                          Link Preview Image
                          1 Reply Last reply
                          0
                          • lizbian@chaos.socialL lizbian@chaos.social

                            @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.

                            kekunplazas@mamot.frK This user is from outside of this forum
                            kekunplazas@mamot.frK This user is from outside of this forum
                            kekunplazas@mamot.fr
                            wrote last edited by
                            #44

                            @lizbian @mitchellh @briankrebs Yep, exactly my point since a pretty long time.

                            1 Reply Last reply
                            0
                            • pojntfx@mastodon.socialP pojntfx@mastodon.social

                              @mitchellh One of the best descriptions I've heard lately was that it feels like "losing coworkers to dementia" as people adopt it, where everyone feels like they know everything, but when you talk with them in person or there is a problem that needs to be fixed _now_ it becomes very clear that the capability to do that has atrophied basically completely

                              cczona@hachyderm.ioC This user is from outside of this forum
                              cczona@hachyderm.ioC This user is from outside of this forum
                              cczona@hachyderm.io
                              wrote last edited by
                              #45

                              @pojntfx I lost a loved one to dementia, and have been saying for a while how similar LLM psychosis is to that experience.

                              Carina C. Zona (@cczona@hachyderm.io)

                              @Di4na @jenniferplusplus and there is already evidence emerging that engineers who depend on LLMs to write their code for them are eroding their skills. I would analogize it to early stage dementia. The person can't see how their judgement is gradually developing fissures that compromise their ability to function. Eventually it will become too clear to deny anymore. But right now they are increasingly impaired while no less confident in the comprehensiveness of their skills. It's the period when they present a big risk to self and others, because of the growing gap between reality and perception of competence. This person is letting LLMs draft most of their code, and fails to see that not continuing to hone their own skills as an active coder has personal consequences; and that doing so en masse poses societal consequences. What happens in a generation when there are virtually no engineers left who can review a LLM's outputs competently?

                              favicon

                              Hachyderm.io (hachyderm.io)

                              Carina C. Zona (@cczona@hachyderm.io)

                              @janl@narrativ.es I do feel in mourning. It's been very similar to when a relative developed dementia. The person I knew disappeared in jolting episodes, replaced by someone with their face but an unrecognizable personality and stripped of the values they'd held dear. It was deeply troubling and so, so sad to be around. In the past year I've been feeling that same sense of loss. Moving through the stages of grief for one person, then another, another. It's mentally exhausting. But when you care about someone or something, it's difficult to just decide to not let it matter.

                              favicon

                              Hachyderm.io (hachyderm.io)

                              They think they are fine, while the person you used to know is gradually replaced by someone unrecognisable. Professional de-skilling issues aside, a sadder dimension to me is how AI psychosis degrades not only cognition but also social skills. So relationships deteriorate too, and at scale that will ultimately become communities and solidarity deteriorating as well. It's been disturbing to see people I care about lose interest in connecting at a human level, while grasping for the empty flattery of a large language model. Is this our future, truly?

                              datenwolf@chaos.socialD 1 Reply Last reply
                              0
                              • S spacelifeform@infosec.exchange

                                @mitchellh

                                Ask them what they will do when their cloud is down.

                                Handwaving ensues. Fog rolls in.

                                immibis@social.immibis.comI This user is from outside of this forum
                                immibis@social.immibis.comI This user is from outside of this forum
                                immibis@social.immibis.com
                                wrote last edited by
                                #46
                                @SpaceLifeForm @mitchellh "When the cloud is down, it's foggy" - some kind of strange metaphor or pun
                                1 Reply Last reply
                                0
                                • unlofl@mstdn.socialU unlofl@mstdn.social

                                  @hopeless Its a metaphor and the post explains their concern pretty well

                                  Can anyone help me find the downvote button here? My fedi client still only has one for "fav"

                                  immibis@social.immibis.comI This user is from outside of this forum
                                  immibis@social.immibis.comI This user is from outside of this forum
                                  immibis@social.immibis.com
                                  wrote last edited by
                                  #47
                                  @unlofl @hopeless There's no fediverse downvote by design, and the upvote/like/star doesn't do very much either. You can block people who continually spout nonsense.
                                  1 Reply Last reply
                                  0
                                  • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

                                    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.

                                    tenpasttwo@mas.toT This user is from outside of this forum
                                    tenpasttwo@mas.toT This user is from outside of this forum
                                    tenpasttwo@mas.to
                                    wrote last edited by
                                    #48

                                    @mitchellh
                                    In the 90s we only optimised to MTBF, MTTR wasn't considered terribly helpful. A software deployment could run for months without restarts or updates. But back then a person could hold an entire stack in their minds. I recall my first realisation of the total shift to MTTR with an ML based written record reader. We outsourced the ML, each instance could read only 1 record before dying. My boss was nonfussed, just restart it anew for every record... Infra is now just bubbles popping.

                                    1 Reply Last reply
                                    0
                                    • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

                                      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.

                                      totoroot@ibe.socialT This user is from outside of this forum
                                      totoroot@ibe.socialT This user is from outside of this forum
                                      totoroot@ibe.social
                                      wrote last edited by
                                      #49

                                      @mitchellh@hachyderm.io Thanks for stating what many are seeing in our industry. Especially since your opinion bears a lot of weight.

                                      I myself am trying to figure out how to voice concerns in the workplace and in the Open Source communities I participate in, while trying to not completely disregard the excitement people feel.

                                      It becomes hard to argue with colleagues about the pros and cons of using LLMs in software engineering, when the CTO suggests an AI-first approach to anything, at any chance they get.

                                      ambrosia_engine@mastodon.socialA 1 Reply Last reply
                                      0
                                      • mitchellh@hachyderm.ioM mitchellh@hachyderm.io

                                        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.

                                        ambrosia_engine@mastodon.socialA This user is from outside of this forum
                                        ambrosia_engine@mastodon.socialA This user is from outside of this forum
                                        ambrosia_engine@mastodon.social
                                        wrote last edited by
                                        #50

                                        @mitchellh I'm doing a PhD on the epistemic risks of LLMs. I used to work in industry and I see this too and it's so terrifying. Currently writing a paper looking at one of the mechanisms at play here, but how do we even talk to these people and get them help anymore? Especially when it's clear entire startups are affected.

                                        1 Reply Last reply
                                        0
                                        • rebelgeek99@mastodon.socialR rebelgeek99@mastodon.social

                                          @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

                                          kaffando@mastodon.socialK This user is from outside of this forum
                                          kaffando@mastodon.socialK This user is from outside of this forum
                                          kaffando@mastodon.social
                                          wrote last edited by
                                          #51

                                          @RebelGeek99 @mitchellh @DukeDuke

                                          What you've just said....yes. Exactly that.

                                          Yes.

                                          #COVIDBrain #AISlop

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups