The Zen of Programming
summary
A 40-year coder argues for ruthless simplicity: prefer single-line functions, short names, remove unnecessary dependency injection, and treat every line of code as ongoing cost. Uses TypeScript microservices with a repo/gateway layered architecture, trunk-based development with ~20 commits per day, and reports a service handling 68,000 requests per minute as “fast enough.” Tests drive design (TDD style) so debugging drops, teams form rotating micro teams to experiment and adapt.
AI-written summary · about
chapters (25)
- 0:00Intro
- 1:57Being a travelist
- 4:00Being a codist
- 5:51The zen of programming
- 6:20How does learning work?
- 8:58Learning & unlearning
- 10:49A quest for super simple code
- 12:32The wall in the desert
- 14:50The end of "productivity"
- 15:54Code lives in your head
- 19:07Programming is addictive
- 20:20Always travel light
- 22:37You can only spend your time once
- 24:25Do we really need this now?
- 25:10Simplicity rules
- 30:00Architect to adapt
- 35:21There are no best practices
- 37:42Monadic code
- 38:11Unit testing
- 40:13Passive testing
- 41:15Testing a design
- 43:20Active testing
- 45:26Learn by doing
- 48:35Some people like change. Others don't.
- 50:36Outro
related talks
46mThe Zen of Programming. A personal journey towards writing beautiful code.
56mThe Diabolical Developer
40mThe Best Programmer I Know
50mThe Effective Developer - Work Smarter, Not Harder
01h 09mThe Well-Balanced Programmer
31mThe Effective Developer - Work Smarter, Not Harder
48mA Personal Philosophy of Excellent Engineering
49mThe Best Programmer I Know