How We Tell Stories In Code
summary
Claim: good software is a human-facing narrative that accepts unpredictability rather than architecting it away. Cites tools actually used: functional programming, immutability, testing, type systems, plus practices like pair programming and iterative refactor. Concrete examples: a homemade 3D engine that ran but crashed about every minute, reading Doom’s C source for 15 years of learning, and using grant‑writing compression to pick 1–2 core accomplishments. Personal data points: ~20 years programming, 3 years out of work, 5 years on disability.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 3:24Why stories matter in code
- 14:35The real story of getting into tech
- 21:44Refining code like a writer
- 27:01Advice for better programming
- 27:44Q&A begins
related talks
48mStorytelling With Software
34mHow do our ideas about coding affect the software we create?
35mCraft, Engineering, and the Essence of Programming
27mHow you tell the story matters: telling better stories and making better technologies
42mWhat our Brains can Teach us About Software Engineering
39mWriting for Humans: Designing better software by keeping humanity in mind
59mSondheim, Seurat and Software: finding art in code
03mFrom puzzles to products