Programming Intuition
summary
Argues that what matters are concrete claims and artifacts: great programmers are ~10× more productive, and intuition is trainable by mapping abstractions to senses. Shows three built instruments that work—dangling string Ethernet monitor for network weather, plywood server gauges that audibly signal overload, and lava lamps for build status that change team behavior—plus favors tools that shorten the feedback loop (Ruby REPL, visualizers like Code Canvas) so patterns become feelable and learning happens quickly.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:27Tactical design principles
- 6:45Paul Graham on programming as art
- 8:53Brains wired for real world
- 10:19Music and brain signal processing
- 15:32Music and code relationships
- 20:22Emotional response to code quality
- 23:55Static versus dynamic structures
- 26:22Concrete abstractions
- 31:08Lava lamps and team awareness
- 33:39Senses and pattern recognition
- 36:49Kinesthesia and code resistance
- 38:56Beauty and intuition in code
- 40:00Cultivating programming intuition
- 41:27Tools and feedback
- 43:59Developing intuition through practice
- 45:45Film making and attention
- 47:15Closing thoughts
related talks
29mA Journey Inside the Developer Brain
43mYou Belong In A Room Full of Wizards
31mThe Effective Developer - Work Smarter, Not Harder
30mCognitive Shortcuts: Models, Visualizations, Metaphors, and Other Lies
35mHow to feel good about the code you contribute
07mDevelopment setup: how an important part of your toolset is often overlooked
27m"Intuitive" Tooling
24mBeyond the Commit: A Fireside Chat on AI and Developer Productivity