--- title: "Too much, all at once: digest or burn out?" speakers: "Scott Tolinski (Syntax)" duration: "23:57" source: transcript.md video: null themes: [overwhelm, meaning, decisions, habits, mental-health] reader: "Will and his clients: how people absorb a world where they can do far more than they can hold" built_from_notes: - notes/inbox/2026-11-10T1013-like-turing-posts-recent-post.md - notes/inbox/2026-11-10T1014-ai-agents-anxiety-and-the-cost-of-too-many-decisions.md - notes/inbox/2026-11-10T1019-slides-are-a-3d-model-zooming-between-monitors.md - notes/inbox/2026-11-10T1025-presentation-built-in-3djs.md - notes/inbox/2026-11-10T1026-probably-three-js.md - notes/inbox/2026-11-10T1030-one-agent-watched-not-parallel-mental-health.md read_alongside: "https://www.turingpost.com/p/ai-agents-anxiety-and-decision-overload" key_points: - "The pull is compulsive: one more prompt, a slot-machine loop, too many decisions at once (00:04:51, 00:06:32, 00:09:42)" - "Underneath is a crisis of meaning: what the work is, and whether it still means anything (00:12:11)" - "People can absorb it, by rewiring and by building limits, but the talk leaves open whether we digest it or burn out (00:14:00, 00:17:50, 00:19:50)" kind: talk-story status: draft --- # Too much, all at once Scott Tolinski surveyed more than 4,000 developers about how AI coding is affecting their mental health (00:04:22). The answers describe people who can suddenly do far more than they can hold. Read with the notes taken in the room, the talk is about one question: is this a new world we will learn to absorb, or one that burns people out first? *Framing note: "crisis of meaning", "manic" and "digest or burn out" are the framing from the notes, not his words. Each section separates what he said (cited) from that reading.* ## A manic loop The first thing the survey found is that people can't stop. 52 percent kept prompting past the time they meant to quit (00:04:51), and those who struggled to stop also reported sleeping badly (00:06:05). One respondent had the AI remind them to stop for meals and still ignored it (00:04:51). He describes the pull as a slot machine: a variable reward, like a loot box, where the next prompt might be the one that gets it right (00:06:32). At the extreme, he cites a developer who ended up in hospital from stress, trying to use up tokens before a model was retired (00:03:25). He isn't writing about other people. His own symptoms from an earlier injury (sleep loss, muscle twitches) came back when he started prompting heavily (00:01:23), and he ties them to stress (00:20:46). > “Let me just one more. Let me just one more, right?” > — 00:04:51 > “It feels like I'm buying lottery tickets with my time and attention, but it's so fun to build.” > — 00:06:32 **Visual:** photo `photos/PXL_20261110_181435938.jpg` (the “prompting past when you meant to stop” chart) ## Too much at once The pressure isn't only internal. 71 percent feel they have to produce more simply because AI makes it possible, and only 195 people said never (00:07:54). One respondent says writing code by hand now feels like taking a break, and real breaks feel close to illegal (00:07:54). Then multiply it. Running five agents means five streams of questions; he names it decision fatigue (00:09:42), and quotes a React developer's escalation: two agents, four, eight, infinity (00:09:42). The result is people who feel more productive than ever and more tired than ever (00:09:42). > “Obviously, it's decision fatigue.” > — 00:09:42 > “If I can run four, I can run eight. And I can run infinity” > — 00:09:42 **Visual:** photo `photos/PXL_20261110_181822800.jpg` (the slide: writing code by hand feels like taking a break) *Read alongside:* Ksenia Se's Turing Post editorial, “The Anxiety of Abundance” (Nov 9, 2026), makes the same point from outside the talk: agents take the doing off your hands, but the deciding stays with you, and it doesn't scale. ## A crisis of meaning Under the overwork is a harder question: what the work even is. He says developers are in a transition in their understanding of their own work, and many are mourning the loss of writing code by hand (00:12:11). The survey answers split. One person lost their spark, and now it's just money. Another says AI is the spark, and someone senior enough that they rarely code is "so back now" (00:12:11). *The reading:* this is the crisis of meaning underneath the mania. The same change empties the work for one person and refills it for another. > “I lost my spark, my passion.” > — 00:12:11 > “And so, a lot of people are having to mourn the loss of writing code by hand” > — 00:12:11 **Visual:** photo `photos/PXL_20261110_182211766.MP.jpg` (the “I lost my spark” slide, with him on stage) ## Digesting: the brain rewires 63 percent say their coding skills are diminishing (00:14:00). He explains it with neuroplasticity: the brain strengthens the paths it uses, and the ones it stops using fade (00:14:00). At first that upset him. Then he looked at what he'd forgotten (old CSS clear-fix tricks, sites that worked in Internet Explorer 5) and decided most of it no longer matters (00:14:00). *The reading:* this is what digesting looks like. Old skills fade, new paths form, and losing them is a cost only if they were still the point. > “So again, we start to form new pathways.” > — 00:14:00 **Visual:** diagram “old paths fade as new ones strengthen: forgetting as digestion” ## Building ways to absorb it His answer is not a tool. The things that make an impact are better habits and sticking to them (00:17:50), which he admits is easier said than done (00:17:50). Specifically: - **Fewer agents at once.** A respondent: less parallelization makes for a calmer mind. He agrees from experience (00:19:50). - **Grounded time.** Hobbies, pottery, hiking: experiences that were nice to have are becoming necessary (00:17:50). - **Go outside**, away from screens and agents (00:20:46). - **Keep agents out of downtime.** Checking agents on your phone during a hockey game is where it slips (00:21:48). One respondent reports halving their hours, with better mental health and more output (00:17:50; the transcript garbles the line, and the slide in the photo reads "I do half the work, 4x the output and a lot of time for hobbies"). *From the notes:* one agent, watched, rather than many in parallel, is the practice that stood out in the room. > “Less paralization makes for a calmer mind.” > — 00:19:50 > “Nature heals AI psychosis. Go touch grass.” > — 00:20:46 **Visual:** photo `photos/PXL_20261110_182820893.jpg` (the “hours worked per day have halved” slide, hours and output bars animated) ## Digest and transcend, or burn out? The talk doesn't settle it. On one side, he expects change: developers are mid transition (00:12:11), and as the models get better some of this pressure changes (00:19:50). The brain rewires (00:14:00). On the other, people are exhausted and holding it in. They used the survey to say how hard it is, because nobody's talking about it (00:04:22). And self-control is not a system (00:21:48). His own deck is evidence for both. A respondent says AI let them make slides out of three.js, something they'd never have tried (00:12:11), and this talk is built that way: every slide is a 3D model (00:06:32). Abundance can be delightful and still be too much. *The reading:* the open question is whether people digest this and come out the other side, or burn out first. The talk's honest answer is that it depends on the limits people and organizations build, and that nobody has those yet. > “As the models get better or faster or whatever, some of this changes.” > — 00:19:50 > “It's not that easy to build these systems, right?” > — 00:21:48 **Visual:** diagram “a fork: overwhelm → digest (rewire, limits, meaning) or burn out (no limits, no stopping)”