DRY is about knowledge, not similar lines. Distinguishing shared rules from incidental duplication and recognizing the cost of premature abstraction.
The DRY Myth — When Code Duplication Is the Correct Architecture Read Post »
Exploring an unfamiliar repository: entry points, call paths, grep and rg, LSP, Git history and running one concrete execution path.
Reading Other People’s Code — From Entry Points to Understanding the System Read Post »
Debugging methodically: describe the symptom, establish expected behavior, form a hypothesis and test it with a debugger, logs or git bisect.
Debugging Code — Hypotheses Instead of Guesswork Read Post »