Reading code under the influence of one’s emotions
summary
Claims that reading code is an under-taught skill and that emotions steer interpretations, so adopt a staged empathy checklist from malice → stupidity → ignorance → lack of attention → unstated context → systemics. Uses practical tools: dependency graphs, red pen mapping of jump paths, and field‑note marginalia. Runs a workshop reproducing 30 client behaviors with 680 attendees where every team produces code they immediately regret, proving systemic pressure matters. Recommends reading Thinking in Systems and How to Read a Book.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 3:00The hidden agenda
- 4:25Emotions
- 5:15Fear
- 6:25Coping
- 6:50My coping mechanisms
- 7:55Hollands razor
- 9:50Stupid
- 15:50Unstated context
- 19:20Systems thinking
- 27:50Everyone creates bad code
- 29:01Changing the culture
- 31:00Reading as a cost
- 34:19Level of reading
- 35:43Indexing
- 37:41Graphs
- 42:14Separation
- 44:14Analytical reading
- 46:33Finding time to read
- 48:02Software is software
- 52:27Conclusion
