Debugging Rules! This site contains resources to help you debug stuff — mostly software and electronic Dave Agans’ long-awaited novel is now available!. 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 . Debugging—The Nine Indispensable Rules for Finding Even the Most Elusive Software elusive software and hardware problems / David J. Agans. p. cm.
|Country:||Trinidad & Tobago|
|Published (Last):||23 September 2006|
|PDF File Size:||13.3 Mb|
|ePub File Size:||11.44 Mb|
|Price:||Free* [*Free Regsitration Required]|
Jul 21, Juraj Martinka rated it it was amazing.
Recommended for any and all troubleshooters, no matter what your field. There are no discussion topics on this book yet. 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. Pretty entertaining and able to provide insight. Make it fail 3. For years my only recommendation to someone interested in the heuristics of problem solving was George Polya’s “How To Solve It”, but now I can cheerfully add Agan’s “Debugging”.
Open Preview See a Problem?
Debugging : The 9 Indispensable Rules for Finding Even the Most Elusive Bugs
Jul 16, David Robins rated it really liked it. Agans provides nine simple rules to follow, and some amusing stories to back them up. As a manager, I’ve started to realize that some of these principles apply to people problems as well. It is your fundamental guide to start from “first principles”. It’s brilliantly laid out for someone new to the discipline, but even if you’re experienced it’s well worth a read for the clarity of the 9 elegant principles the author identifies, and for the many memorable “war stories” he describes from his own engineering career to illustrate them.
Want to Read Currently Reading Read. As I’ve said about other software engineering books and my review for “Debug It! Jan 23, John rated it really liked it. Check the plug 8. It does a great job of collecting and organizing the principles of skillfully tracking down issues.
Worse, there’s a strong tendency for people to take such pat one-liners out of context, and the author invites that by promoting the rules themselves rather than the ideas. If you’re a programmer: I was quite pleasantly surprised the author managed to reduce the skill to nine short rules particularly when it sometimes can be a process that is difficult to explain.
Keep an audit trail 7. I recommend this book to all engineers, both the students and the ones in the industry. Mitochondrion rated it it was amazing Nov 09, I recently did a talk about debugging and there was a lot of overlap.
David A. Wheeler’s Review of “Debugging” by David J. Agans
Thanks for telling us about the problem. This is a great book on how to debug systems — not like how to use a debugger, but how to think.
Apr 07, Tanvi rated it really liked it. Divide and conquer 5.
Debugging Rules! – Find out what’s wrong with anything, fast.
Pretty decent, has some interesting examples; but also much debugglng, say, Code Complete common sense. 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. Paperbackpages. If you didn’t fix it, it ain’t fix. Written in a frank but engaging style, Debuggingprovides simple, foolproof principles guaranteed to help find any bug quickly.
Victor Grigoriu rated it it was amazing Jun 13, Interesting debuging read a methodology around debugging. 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. Jan aganz, Frank rated it it was amazing.
As I read this book I noticed I seemed to almost magically be debugging more effectively. May 25, Michael rated it really liked it. To ask other readers questions about Debuggingplease sign up. Get a fresh view 9. I borrowed it from a friend who says he recommends it to every technical person he works with.
I had some issues following all the explanation there. The writing and the rules themselves are a bit muddled, and that can really lead readers down a wrong path. This book is probably the most useful book I could recommend for anyone in the IT industry. Ann rated it it was ok Aug 19, Just a moment while we sign you in to your Goodreads account.
Sep 13, Dmitri rated it it was amazing. It took God one day to design, prototype, and release that product; talk about schedule pressure! Jul 09, Muhammet rated it it was amazing. Dave Agans Goodreads Author. The examples were a bit dated and it helps to understand solid state electronics but the principles are sound. Sep 08, Andreea Lucau rated it it was ok. To see what your friends thought of this book, please sign up.
Not a lot new here. That’s actually the opposite of what inexperienced engineers need to learn about debugging.