Debugging Rules! This site contains resources to help you debug stuff — mostly software and electronic Dave Agans’ long-awaited novel is now available!. Buy Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems by David J Agans (ISBN: ). David said: As I’ve said about other software engineering books (and my The nine debugging rules that Agans lays out are applicable to any problem that you .
|Country:||Central African Republic|
|Published (Last):||19 February 2008|
|PDF File Size:||20.6 Mb|
|ePub File Size:||3.6 Mb|
|Price:||Free* [*Free Regsitration Required]|
There’s febugging a chapter providing an alternative “vi This is a very important, short, accessible and fun book. Sep 13, Dmitri rated it it was amazing. Ann rated it it was ok Aug 19, If you’re a programmer: The author goes through each rule step-by-step and present “war stories” to demonstrate the rules in action. The rules are clear, make sense, but they were introduced by A LOT of war stories, most of them related to how you debug hardware problem.
David A. Wheeler’s Review of “Debugging” by David J. Agans
May 25, Michael rated it really liked it. Check the plug 8.
That’s actually the opposite of what inexperienced engineers need to learn about debugging. Steve rated it it was amazing Nov 30, The best example is the rule “quit thinking and look”, which could be much more accurately and not less succinctly called “stop guessing and gather data”.
Jul 09, Muhammet rated it it was amazing. Jul 21, Matthias Ferber rated it it was amazing. Sep 27, Mitchell rated it really liked it Shelves: In my favorite war story, an cebugging video-processing bug was eventually traced to the plaid flannel shirt th This is a great book on how to debug systems — not like how to use a debugger, but how to think.
Just a moment while we sign you in to your Goodreads account. This is a great resource. Certainly a valuable addition to any debugger’s bookcase.
The writing and the rules themselves are a bit muddled, and that can really lead readers down a wrong path. I really enjoyed this book. The book is well-organized entertaining and easy to read. Divide and conquer 5. A must read for all engineers and programmers. May 15, Wangyiran rated it really liked it. As I read this book I noticed I seemed to almost magically be debugging more effectively.
To ask other readers questions about Debuggingplease sign up. Peter Jones rated it really liked it May 30, The title probably does the book a agan, because it’s really a broadly useful troubleshooting guide, although the title wouldn’t necessarily indicate that. Thanks for telling us about the problem. I second that recommendation. It is your fundamental guide to start from “first principles”. Still, it’s nice to have the principles laid davic. The examples were a bit dated and it helps to understand solid state electronics but the principles are sound.
Not a lot new here. I’ll bet that many of these rules are seen as common sense in the developer communities.
Follow the Author
Useful and applicable methods for debugging. Want to Read saving….
Be ware that the examples are predominantly hardware or mechanical, but it makes little difference. Dave Agans Goodreads Author. I guess we can forgive priority-two bugs like bunions and male pattern baldness.
And just like everyday aphorisms like “a bird in the hand is worth two in the bush”most of the principles in this book like “check the plug”: No better book that breaks down the concept.
Thallia rated it it was amazing Jun 28, Fun to read book for all engineers! I had some issues following all the explanation there. Keep an audit trail 7. Paperbackpages. This book is probably the most useful book I could recommend for anyone in the IT industry.