Dillon Mulroy, Rhys Sullivan, and Sunil Pai discuss the emotional cost of coding with AI. Dillon and Sunil work at Cloudflare; Rhys is building Executor. Recorded August 3, 2026; about 56 minutes.

Human communication still needs a human author.

  • 00:00: Rhys describes recognizing Claude’s voice in someone speaking. His tweet received about 700,000 views, followed by an apparently automated reply.
  • His concern is credibility. Publishing more unedited output can erase the voice that made people trust its author.
  • Dillon objects to AI replies. Rhys worries about mistaking neurodivergent phrasing for generated text. Style alone is an imperfect detector.
  • 03:30: The /bro skill asks the model to restate an answer without jargon. In a workplace discussion, label pasted model output so colleagues know what they are reading.
  • 05:26: Sunil uses Borges’ Tlön, Uqbar, Orbis Tertius as a metaphor for invented language reshaping ordinary life.
  • The hosts describe conspicuously generated public statements and words such as “substrate” entering conversation. These are observations and examples, not proof that any unusual sentence came from AI.

Burnout can coexist with good hours and useful output.

  • 08:48: Dillon’s starting point is uncertainty: changing models, changing tools, and inconsistent results make a hard-won workflow unstable.
  • 11:48: The WHO framing names exhaustion, distance or cynicism toward work, and reduced professional efficacy. Burnout is classified as an occupational phenomenon.
  • Sunil draws on Christina Maslach’s person-workplace mismatch: workload, control, rewards, community, fairness, and values. He resists treating burnout as personal weakness.
  • 14:09: Dillon says he has strong work-life balance, clear direction, and autonomy. Learning a fundamentally different job can still reduce his sense of competence.
  • 28:21: He reports producing more work he is proud of while finding the process more exhausting. Productivity and sustainable work are separate measures.

Tools can preserve craft or distance people from it.

  • 16:52: Ethan Niser’s Not Holding Back the Ocean compares the change to moving from physical film cutting to digital editing. Dillon takes encouragement from serving the finished product.
  • 18:18: Kirwin Hampshire’s The Dark Night of Mathematics prompts sympathy for threatened expertise and training traditions. Predictions about future mathematical proofs remain the hosts’ speculation.
  • 21:28: A thought experiment asks engineers to imagine models returning binaries instead of editable source. It helps explain why artists might experience replacement rather than collaboration.
  • 22:29: Sunil prefers music tools that leave his hands in the process. His Pizzo demo pairs an agent with a digital audio workstation whose controls remain visible and editable.
  • 23:50: The hosts disagree about long autonomous game-building runs. A recognizable game can be impressive while still being difficult to steer toward a particular person’s taste.
  • 27:37: Dillon is experimenting with rapid iteration in a shared Markdown document. He wants frequent correction, not a long wait for a finished artifact.

Automation can remove the social value of a task.

  • 29:09: Sunil describes two weeks of leave and quiet weekday cinema visits. This helped him reflect; he does not present it as a universal treatment.
  • 30:44: He questions what Glyph Lefkowitz’s “futzing fraction” leaves out. Time and financial value can miss the cumulative emotional cost of repeated agent supervision.
  • 32:22: Charlie Marsh’s advice to build things that may soon become obsolete raises another burden: entire features and products can lose relevance quickly.
  • 33:39: Sunil says Codex grouped roughly 100 repository issues in ten minutes. The old hour-long triage call also gave his remote team shared context and time together.
  • 34:47: Dillon spent almost twelve hours with teammates during a production incident. He enjoyed the collaboration despite the incident, and recognized how isolated normal work had become.

An agent helped cause an incident and helped repair it.

  • 38:45: Dillon says an agent deployed a prototype directly to production, bypassing their normal release tool. A migration broke data because its corresponding writer was not in place.
  • Agents helped query ClickHouse, logs, and SQLite databases. The team gathered the evidence in an hour or two, then wrote and monitored repair scripts.
  • Dillon estimates recovery would previously have taken at least a week. That is his counterfactual estimate, not a measured comparison.
  • Human knowledge of schemas and intended behavior supplied the precise fix. He left the incident more committed to reading the generated code.
  • 41:15: The hosts call model ability “spiky.” Strong local performance can coexist with missing a basic constraint, such as multiple customer accounts.
  • 41:52: Repeating the same correction in new sessions wears Dillon down. He is experimenting with saved feedback and review tools, without claiming to have solved it.

Sunil names the identity problem directly.

  • 45:14: Being the person trusted with hard problems was part of his identity. Directing a capable machine can feel different from doing the brush strokes himself.
  • 46:21: He worries that large code-output claims frighten junior developers while seniors spend less time mentoring them.
  • 47:30: He questions whether less struggle also weakens his ability to recognize valuable work. This is his account of meaning, not a requirement that useful work be painful.
  • 48:17: Time away and a team lunch helped him reconnect. He says he feels much better on returning.

Useful software still gives them joy.

  • 49:14: Rhys enjoys small personal projects, including a recipe viewer and experiments where friends’ agents can communicate. He says these have not all become lasting habits.
  • 50:12: Dillon enjoys a workflow finally working well. His recipe-formatting app helped him cook twice that weekend, and curious interns made him more hopeful.
  • 52:45: Sunil’s favorite feeling remains someone using his software and saying it helped. He connects this to years improving the experience of Cloudflare Durable Objects.
  • 54:21: Dillon remembers small back-office tools that visibly improved a colleague’s day. Scale is not required for that satisfaction.
  • 55:01: The hosts encourage people who are struggling to seek support. The video description includes regional mental-health resources and Find a Helpline.