← /media/podcast
The Atrophy of the Coder
When the builder becomes the inspector — and the craft starts to fade.
76% of developers use AI tools. Veteran engineers admit they haven’t manually written code in months. What happens when the calloused mental muscles start to atrophy — and the code breaks at 2 a.m.?
>_ chapters
- 0:00 The 2 a.m. cursor in the technical void
- 0:22 AI acceleration: 76% adoption, 55% faster tasks
- 0:39 Builder to inspector: orchestrating agents, not writing code
- 1:05 When code breaks: do we still have the muscles to fix it from scratch?
- 1:25 Boats vs. swimming (Rob Vanderveer)
- 1:45 The dangerous myth: human as secondary oversight
- 2:09 The technical void: speed vs. architectural understanding
- 2:34 Aotearoa indie games: stories, automation, and representation
- 3:38 Auckland War Memorial Museum: AI can't feel cultural permission
- 4:17 Hardware is hard: no vibe coding through field failures
- 5:15 Socio-technical trust: people and tools, jointly optimized
- 5:28 The stupid work: manual debugging as verification capacity
- 5:42 South Auckland and the next generation
- 6:12 Legacy: resilience over volume of code produced
- 6:34 Tools that think alongside us — or replace the need to think
- 6:53 Closing: share this transmission
>_ key ideas
- Builder → inspector: when you stop writing code, the calluses fade.
- Acceleration without verification capacity is debt, not speed.
- Cultural permission, hardware, and field failures can't be vibe-coded.
- Socio-technical trust: optimize people and tools together, never one without the other.
- Legacy is resilience — not the volume of code an agent shipped on your behalf.