To Code Is Human
summary
Code decisions hinge on human limits: sleep and regular meals beat extra hours, coding while exhausted produces antiwork that later explodes (example: a cache-expiry bug that locks a database after a late launch). Vision uses saccades so long lines hurt readability, memory holds seven give or take two items, and stories speed long-term recall. Design for those limits: short functions, three-indent depth, readable refactors, tests-first to use the brain’s reward cycle.
AI-written summary · about
chapters (15)
- 0:00Start
- 4:45Ante Work
- 5:45Consistent Energy Delivery
- 10:47Avoid Fast Carbohydrates
- 13:26Achievable Goals
- 13:39Tracking Your Progress
- 16:42Memory
- 17:57Cognitive and Physiological Limits
- 18:22Levels of Indentation
- 19:09Readability
- 23:23Self Discipline
- 24:55The Reward Cycle
- 29:18Real-Time Code Review
- 36:17Stepping Back and Acknowledging What You'Re Feeling
- 38:18Work with Your Body
related talks
42mTo Code is Human
29mPsychology of Code Readability
39mRead my code, or why writing readable code matters
42mWriting Code for Humans, Not Computers
54mReadable Code: The Secret to Clean, Productive Software
29mA Journey Inside the Developer Brain
52mHow to Read Complex Code
28m7±2 Reasons Psychology Will Help You Write Better Code