Code reading
summary
Research shows developers spend about 58% of their time comprehending existing source, so the talk gives concrete practice: timed first glance exercises, tracing variables to build a dependency graph, picking the five most important lines, and summarizing behavior. Tools demonstrated include running tests in a debugger, using git history, generating a dependency matrix or simple diagrams, and small local refactors to reformat or rename for understanding.
AI-written summary · about
chapters (10)
- 0:00Code reading importance
- 1:43Reading vs writing code
- 3:31Code reading club
- 8:06Why code is confusing
- 14:11Effective code reading
- 17:25IDE tools for code
- 23:07Tracing code behavior
- 26:39Onboarding to codebase
- 31:16Codebase dependencies
- 36:31Practicing code reading
