Debugging
by David J. Agans · first published 2002
81% recommend19% neutral
Why HN recommends it
Short, readable set of nine debugging rules, each with concrete real-world examples, that replaces random code changes with systematic method. Suits newer programmers and experienced engineers, software or hardware.
Summarised by Claude from recommending comments
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Mentions per year
What Hacker News says
Related books
2012–2026Why programs fail
Andreas Zeller
Recommended by 7 · mentioned by 87 recommend · 8 mention7 recommend · 87 recommend
2007–2026Code Complete
Steve McConnell
Recommended by 393 · mentioned by 669393 recommend · 669 mention393 recommend · 669393 recommend
2007–2026The Practice of Programming
Brian W. Kernighan
Recommended by 90 · mentioned by 12890 recommend · 128 mention90 recommend · 12890 recommend
2007–2026Lisp in Small Pieces
Christian Queinnec
Recommended by 101 · mentioned by 141101 recommend · 141 mention101 recommend · 141101 recommend
2007–2026The Little Schemer
Daniel P. Friedman, Matthias Felleisen
Recommended by 288 · mentioned by 438288 recommend · 438 mention288 recommend · 438288 recommend
2007–2026Programming Perl
Larry Wall, Tom Christiansen, Jon Orwant, Christiansen
Recommended by 90 · mentioned by 21490 recommend · 214 mention90 recommend · 21490 recommend
2008–2026The art of electronics
Paul Horowitz, Winfield Hill
Recommended by 153 · mentioned by 230153 recommend · 230 mention153 recommend · 230153 recommend
2007–2026Effective Java
Joshua Bloch
Recommended by 172 · mentioned by 243172 recommend · 243 mention172 recommend · 243172 recommend
I wonder if you have much to add to http://www.amazon.com/Debugging-Indispensable-Software-Hardw... (which I really like). Rule 5: "Quit thinking and look" is (I think) equivalent to your "don't assume". Rule 6: "Divide and Conquer".
on “Being a "Great Coder" and 10000 Hours” ↗Become an excellent debugger. It's sorely neglected as a skill that goes along with development, but is not the same thing as being a good coder. Read this book: https://www.amazon.com/Debugging-Indispensable-Software-Hard... It's short and sweet and applies to any technology problem.
on “Ask HN: What is your best advice for a developer to write better code?” ↗I highly recommend, "Debugging" by David Agans. http://books.google.com/books?id=jynA9ECbBsgC It's both profound and practical. I did not expect a book on debugging to be a page turner but I could not put this one down.
on “Best Books / Stories on Debugging” ↗Code Compete 2 Software Estimation: Demystifying the Black Art Pro GIT Debugging by Agans
on “Ask HN: Books for soon to be Software Engineers” ↗I've read a number of books on debugging, it's something of an interest of mine. The best general-purpose debugging book I've read is the cumbersomely named Debugging: The 9 Indispensible Rules for Finding Even the Most Elusive Software and…
on “Ask HN: Good books on debugging?” ↗Another great read for debugging that was recommended to me years ago: http://www.amazon.com/Debugging-Indispensable-Software-Hardw...
on “A collection of debugging stories” ↗> Learn how to debug I recommend this book: http://www.amazon.com/Debugging-Indispensable-Software-Hardw...
on “Ask HN: How to be a great Junior Engineer?” ↗Debugging by David Agans is great. It’s my #1 book recommendation for software engineers. https://amazon.com/dp/0814474578 The lessons from the book are especially helpful when I feel stuck in debugging; I’ll…
on “Teach Debugging (2014)” ↗I recommend https://www.amazon.com.br/Debugging-Indispensable-Software-H... It has concrete points to focus when debugging and a bunch of examples for each. And it's easy to read as an introduction to the subject.
on “Ask HN: Software Debugging Papers?” ↗There are good books about debugging, simple but effective. https://www.amazon.ca/Debugging-Indispensable-Software-Hardw...
on “Why don't schools teach debugging, or, more fundamentally, fundamentals?” ↗Most of theses have free online versions available: The New Turing Omnibus, 66 Excursions in Computer Science[1] Code Complete [2] Debugging The 9 Indispensable Rules of Finding Even the Most Elusive Software and Hardware Problems [3] The Pattern on the Stone [4] The Tinkertoy Computer and Other Machinations ... [8] ----- #5, #6 & #7…
on “Ask HN: What book should my CS1 students read?” ↗I read Agans's Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems back when I was in high school and still pretty new to programming. I learned a lot from it, and still recommend…
on “Why Don't Schools Teach Debugging?” ↗I second the recommendation of Debugging by Agans. It was recommended to me by one of the best debugging people at Apple, and the approaches it outlines have served me well in the years since.
on “Finding the Four Month Bug: A Debugging Story” ↗> Teaching these skills in CS curriculum would probably be a good idea. It was included in my college CS curriculum, using the most obvious text (Debugging, by Agans) almost 10 years ago -- though I had a head start, since I read a copy of it from my public library about 4~5 years before that. If other schools haven't followed suit, I have to ask "What…
on “Learning to program is getting harder” ↗Debugging by David J. Agans. It's about 206 pages and the information is pretty high level, but it taught me to systematically debug problems instead of blindly changing random code.
on “Ask HN: What are the best programming books you could read in a weekend?” ↗