Episode 3 of Next Token — Dylan Malroy, Ree, and Sunil Pi (all Cloudflare, and they work on the Agents SDK) — the episode the show’s been building toward: burnout in the age of agentic AI, closing on what still brings joy in software. ~56 minutes, recorded August 3, 2026.

The opening thread: “a vessel for Claude”

  • Dylan’s tweet (~700K views): watching a human speak and realizing they’re just a vessel for Claude — the dolly-zoom moment where the output is 100% unedited LLM slop. An AI slop reply landed within minutes; Ree’s policy is an instant block.
  • The “bro skill” (from the Planetator guy): restate what you just said without technical jargon, talk to me like a human — blown up into “the bro scale” on Twitter.
  • Borges’ Tlön, Uqbar, Orbis Tertius as the parable: a fictional world’s speech patterns take over the real one until everyone is a “beige personality.” The hosts’ real-world proof: athletes reading ChatGPT announcements, a state senator saying “here’s a version of this text that sounds better suited for legislative assemblies” mid-sentence, and humans in calls using the word “substrate.”

Burnout, properly defined

  • WHO: a syndrome from chronic workplace stress that has not been successfully managed — energy depletion, mental distance/cynicism, reduced professional efficacy. Marcy Sutton’s version: burnout happens when you recognize a problem and you can’t change it.
  • Maslach’s framing: burnout is a mismatch between person and workplace (workload, control, rewards, community, fairness, values) — caused by the job, not the person.
  • Ree’s read: best work-life balance of his career, clear direction, empowered — yet straddling burnout, because agentic engineering is a totally different job with a different skill set, and reduced efficacy up front plus constant change is taxing.

The two articles framing it

  • Ethan Naiser, “Not Holding Back the Ocean” — identity tied to being a very good engineer, changed overnight. The film analogy: was it about physically cutting film, or about building good products? Lean into the new form.
  • “The Dark Knight of Mathematics” — a mathematician watching models solve century-old proofs; young mathematicians’ thousand-year training process changing at this moment. “I wanted to buy the dude a beer.”

The agentic-work tension

  • LLMs outputting binaries vs. code: artists get no collaboration with the machine — and long agent runs feel closer to that than to the tactile 4.5/4.6 era.
  • The viral game prompts (Counter-Strike, Mario Kart): “implement XGAME, make it photorealistic slop, verify your outputs, go run autonomously” — impressive output, but you’re not interjecting taste; “once you interject you start fighting the training data.”
  • Ree: “I’ve still not done a 12-hour goal that didn’t produce anything but garbage. I want to walk the journey with the agent.”
  • The paradox: as exhausting as the tools are, he’s genuinely more productive — outputting work he’s proud to put his name on — and it’s still exhausting.

Ree’s leave, the futsing fraction, and takeoff

  • Two weeks of leave (recommends empty weekday morning showings), and Glyph Lefkowitz’s “futsing fraction” — the expected-value math of interacting with a coding agent — which “doesn’t calculate the toll on human beings when you do it many times in a row.”
  • Charlie Marsh’s tweet: build things that will be obsolete in a couple of months because they’re needed now. “Takeoff compresses the emotions and consequences too” — a year ago the obsolete software was a bash script; now entire products and tech stacks turn over in 3 months.
  • Issue triage used to be an hour-long team call that was healthy for reasons beyond the repo — now Codex computer use does it in 10 minutes. Friday’s production incident (an agent deployed straight to prod and ran a migration against a half-wired database) was an LLM-caused problem fixed with LLM help in hours instead of a week — but the humans who knew the codebase were the scalpel.
  • Isolation is worse than ever: agents let senior engineers do larger work for longer without interacting with teammates.

Sunil’s three theories

  1. Identity: “I’m not the guy anymore — am I doing the brush strokes, or using a remote control and watching a TV play what episodes I wanted to play?”
  2. The juniors: he ships 50-70K lines a week; juniors hear that with no mentoring model and no senior to ape keystrokes from. “Is that what’s expected of them?”
  3. No struggle left: “The American frontier was not found by patting the bison on the back… there’s no struggle left in that anymore.”
  • The fix: two weeks of leave, a London team lunch, and remembering what actually gives him joy. He’s back and feels great.

What still brings joy

  • Ree: personal software — an agent scraping HelloFresh recipes into a viewer, agents that chat with each other, a recipe-to-image app (“I used that cook to cook twice this weekend”), and talking to Cloudflare interns — the curiosity is still there.
  • Sunil: when a workflow he’s been tuning finally just works — “that’s rewarding in the same way problem-solving was the rest of my career. That gives me hope.”
  • Dylan: “someone using it and being happy with it” — even a tiny back-office tool that makes one business analyst’s day 10x better. “Is this what hard drugs feel like?”

“It’s not you. It’s definitely the job. Even the people who love this stuff a lot are renegotiating how they do it — especially at a time when things are changing every 3 months.”