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 .
|Published (Last):||27 March 2009|
|PDF File Size:||11.48 Mb|
|ePub File Size:||15.95 Mb|
|Price:||Free* [*Free Regsitration Required]|
Aug 24, Bart rated it it was amazing. His nine common sense rules for successful computer program code and hardware troubleshooting and debugging are applicable to all fields of technical endeavor. The title probably does the book a disservice, because it’s really a broadly useful troubleshooting guide, although the title wouldn’t necessarily indicate that.
Thanks for telling us about the problem. Get a fresh view 9. Want to Read saving…. Certainly a valuable addition to any debugger’s bookcase. Dec 09, Bob rated it really liked it. Jul 03, Chris Lim rated it it was amazing.
Follow the Author
There’s also a chapter providing an alternative “vi This is a very important, short, accessible and fun book. Quit thinking and look 4. 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.
I borrowed it from a friend who says he recommends ahans to every technical person he works with. It changes the way readers think about debugging, making those pesky problems suddenly much easier to find and fix. William Laney rated it it was amazing Jan 26, No better book that breaks down davud concept.
Check the plug 8. Agans Writing as. For years my only recommendation to someone interested in the heuristics of problem solving was George Polya’s ddavid To Solve It”, but aans I can cheerfully add Agan’s “Debugging”.
To see what your friends thought of this book, please sign up. A must read for all engineers and programmers. Dec 27, Liam rated it it was amazing.
There are no discussion topics on this book yet.
Debugging Rules! – Find out what’s wrong with anything, fast.
I recently did a talk about debugging and there was a lot of overlap. Be ware that the examples are predominantly hardware or mechanical, but it makes little difference. Jan 23, John rated it really liked it. A very interesting and funny read. The examples were a bit dated and it helps to understand solid state debugginh but the principles are sound.
Ismael rated it it was amazing Nov 10, Jul 09, Muhammet rated it it was amazing. That’s actually the opposite of what inexperienced engineers need to learn about debugging. This is a very important, short, accessible and fun book. No trivia or quizzes yet. Apr 07, Tanvi rated it davir liked it.
The book is well-organized entertaining and easy to read. Goodreads helps you keep track of books you want to read.
In my favorite war story, an intermittent 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.
Davidd to read a methodology around debugging. This is a great book on how to debug systems — not like how to use a debugger, but how to think. There’s also a chapter providing an alternative “view from the help desk” which I’ve found very useful.
Make it fail debuggng. Also, this book recommends that you learn your debugging tools well, so I learned and practiced using PyCharm’s debugger well, which has made davis huge difference when I’m debugging Python code. Useful and applicable methods for debugging.
Debugging, David J. Agans, eBook –
Roxana rated it really liked it Oct 23, agabs It does a great job of collecting and organizing the principles of skillfully tracking down issues. Steve rated it it was amazing Nov 30, Pretty decent, has some interesting examples; but also much like, say, Code Complete common sense.
It’s based on the 9 rules which form a basis for every debugging process: