← @bgSponge

Defining AI Psychosis. Part 2: "Prolific AI Psychosis"

Summary

Psychiatrist Jeff Clark defines prolific AI psychosis as high-volume AI output that fails to increase—or even destroys—real work value, driven by a soft break in quality judgment rather than by more code itself.

  1. Volume is not the disease.

    Prolific AI psychosis is failing to assess one's own output quality, so more lines of code or text can mask flat or negative value.

    Prolific AI psychosis occurs when a person generates a large quantity of AI output without significantly increasing the real value of their work.

    The problem lies in the subject’s perception of their output: they can’t assess the quality of their own work.

  2. Harnesses raise the stakes.

    Agent loops that open programs, browse, and ship apps compound both miraculous wins and impossibly bad decisions that look like wins.

  3. Supervision is the real job.

    Models speak with equal confidence as senior engineer and as red-Kool-Aid toddler; rejecting counterfeit wins takes skill, focus, and patience.

    They’re one part senior engineer and one part toddler-running-across-white-carpet-with-a-jug-of-red-Kool-Aid.

  4. Intermittent reinforcement drives the spiral.

    Unpredictable rewards plus hype, job fear, and metrics-driven environments pull people into sleepless hyperfocus where usefulness questions feel like distractions.

    AI software development feels like playing the world’s most favorable slot machine.

  5. Craft stays a human conversation.

    Useful, good, desirable, and delightful are hard for LLMs to supply; intentional boundaries matter anywhere AI can automate.

Read the original ↗Save to your Sponge

Summarized with Sponge. Quotes are the author’s own words.

More from @bg

All readings →