Reading other peoples code
summary
She gives a concrete, iterative plan for tackling huge codebases (Vivaldi + Chromium cited as ~600,000 files): start by cloning, building and running tests, then gripping strings to find code, follow button text to set breakpoints and inspect UI event flow, read the driving “main” functions and client usages of a class, use logging/profiler for async or flaky problems, treat refactoring as throwaway for learning, and finish by retelling (write docs or explain) to expose misunderstandings.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 7:30Getting the code
- 9:05Why
- 10:55The process
- 11:33The 10 techniques
- 12:08Grepping
- 13:23Button
- 15:35Following input events
- 17:01Tests
- 18:46Refactoring
- 20:24Maine
- 22:54Main Layout
- 25:36Runtime Investigation
- 32:12Reading a Class
- 33:49Retelling Rubber Duckie
- 37:22iterative process
- 38:14psychological safety
- 45:17learning mode
