Debugging has ratings and 22 reviews. David said: As I’ve said about other software engineering books (and my review for David J. Agans (Writing as). David A. Wheeler’s Review of Debugging by David J. Agans. March 2, It’s not often you find a classic, but I think I’ve found a new classic for software and. Debugging—The Nine Indispensable Rules for Finding Even the Most Elusive Software elusive software and hardware problems / David J. Agans. p. cm.

Author: Malajinn Goltijas
Country: Burundi
Language: English (Spanish)
Genre: History
Published (Last): 3 July 2014
Pages: 178
PDF File Size: 16.90 Mb
ePub File Size: 13.15 Mb
ISBN: 398-8-57471-242-5
Downloads: 85122
Price: Free* [*Free Regsitration Required]
Uploader: Taurr

My library Help Advanced Book Search.

Check the plug 8. 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. There are no discussion topics on this book yet. Thanks for telling us about the problem.

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”. Sep 08, Andreea Lucau rated it it was ok. It’s based on the 9 rules which form a basis for every debugging process: Change one thing at a time 6. Not a lot new here. This is a great book on how to debug systems — not like how to use a debugger, but how to think.

  BW3S MENU PDF

Debugging : The 9 Indispensable Rules for Finding Even the Most Elusive Bugs

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”.

I really enjoyed this book.

Other editions – View all 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. Fun to read book for all engineers! Thallia rated it it was amazing Jun 28, Open Preview See a Problem? Apr 07, Tanvi rated it really liked it. I second that recommendation. It changes the way readers think about debugging, making those pesky problems suddenly much easier to find and fix.

David A. Wheeler’s Review of “Debugging” by David J. Agans

And just like everyday aphorisms like “a bird in the hand is worth two in deebugging bush”most of the principles in this book like debuggijg the plug”: In my view this book was too long. May 25, Michael rated it really liked it. I’ve read the book before, and decided to revisit it, as I probably will every now and again. Steve rated it it was amazing Nov 30, Get a fresh view 9.

Interesting to read a methodology around debugging. Sep 13, Dmitri rated it it was amazing. Jul 16, David Robins rated it really liked it. This is a very important, short, accessible and fun book. Easy Exercises for the Reader. Pretty entertaining and able to provide insight.

  KENSINGTON 33197 MANUAL PDF

Dave Agans Goodreads Author.

Get a Fresh View. Common sense backed with a ton of experience. Illustrating the rules with real-life bug-detection war stories, the book shows readers how to: Written in a frank but engaging style, Debuggingprovides simple, foolproof principles guaranteed to help find any bug quickly.

Daavid thinking and look 4.

Preview — Debugging by David J. Just a moment while we sign you in to your Goodreads account. Sep 27, Mitchell rated it really liked it Shelves: Jul 09, Muhammet rated it it was amazing. To see what your friends thought of this book, debigging sign up.

If you didn’t fix it, it ain’t fix. Note that the book is not technical. Account Options Sign in. I had some issues following all the explanation there. A solid book on general timeless debugging principles. As I read this book I noticed I seemed to almost magically be debugging more effectively.

The nine debugging rules that Agans lays out are applicable to any problem that you need to solve. As a programming student this book helped me view debugging as a process, rather than a “holy shit it finally works” moment.