Debugging: The 9 Indispensable Rules
by David J. Agans · David J. Agans
Agans distills troubleshooting into nine rules, such as understanding the system, making the failure reproducible, changing one thing at a time, and keeping an audit trail. Illustrated with hardware and software war stories readers can apply immediately.
This link may earn us a small commission at no extra cost to you. Affiliate disclosure
More resources on Debugging
Rubber Duck Debugging
The Wikipedia entry on the practice of explaining code line by line to an inanimate object. It covers the origin of the term, why articulating a problem aloud surfaces faulty assumptions, and related psychological research.
The Art of Debugging
A hands-on treatment of debuggers rather than debugging folklore: breakpoints, watchpoints, stack inspection, and core dumps worked through GDB, DDD, and Eclipse. Readers come away able to drive a symbolic debugger on C and C++ programs.
stackoverflow.com
Stack Overflow is a developer-focused Q&A site where programmers ask debugging and coding questions and share practical, answer-ready solutions with code examples. It hosts a vast, searchable archive of community-voted answers across languages and technologies, organized by tags and reputation.
Why Programs Fail
Treats debugging as a disciplined scientific process: reproducing failures, isolating them with delta debugging, tracking infection chains from defect to symptom, and automating the search for causes. Grounded in research, with tooling and experiments throughout.