Read my code, or why writing readable code matters
summary
Examines readable code as a cognitive problem and gives concrete practices: because working memory holds about four chunks, prefer short methods, small parameter lists, consistent naming and idiomatic patterns. Uses quick JavaScript/Java/Go examples, cites a “magic number” of four items and ~15 minutes to fully resume after interruptions, and recommends linters/formatters, avoiding mixed abstractions or cyclic dependencies, and building explicit domain models (diagrams or DDD) to reduce cognitive load.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:47Scala memory tests
- 6:29Java memory tests
- 10:48Readability and long-term memory
- 14:24Design patterns and idiomatic code
- 17:36Working memory and cognitive load
- 21:56Code organization and spaces
- 24:48Interruptions and productivity
- 26:33Reducing cognitive load
- 28:42Mental models in development
- 32:00Building strong mental models
- 34:12Learning and documentation
- 36:45Summary and Q&A
related talks
29mPsychology of Code Readability
28m7±2 Reasons Psychology Will Help You Write Better Code
17mReady for Readable Code?
52mHow to Read Complex Code
46mMastering the Art of Reading Code
54mReadable Code: The Secret to Clean, Productive Software
40mGood Code: What, Why, and How to Get There
39mClean, Concise, Collaborative Code