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.
|Published (Last):||19 March 2010|
|PDF File Size:||13.64 Mb|
|ePub File Size:||6.70 Mb|
|Price:||Free* [*Free Regsitration Required]|
Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Refresh and try again. Open Preview See a Problem? Thanks for telling us about the problem. Return to Agasn Page. Preview — Debugging by David J. Agans Writing as. Dave Agans Goodreads Author. Written in a frank but engaging style, Debuggingprovides simple, foolproof principles guaranteed to help find any bug quickly.
David A. Wheeler’s Review of “Debugging” by David J. Agans
It changes the way readers think about debugging, making those pesky problems suddenly much easier to h and fix. Illustrating agan rules with real-life bug-detection war stories, the book shows readers how to: Paperbackpages. To see what your friends thought of this book, please sign up. To xgans other readers questions about Debuggingplease sign up. Lists with This Book.
Jun 26, David rated it debhgging it. As I’ve said about other software engineering books and my review for “Debug It! They’re aphorisms and rules of thumb. 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”: As a result, the best way to view this book is a collection of things to think about when debugging, rather than a rigorous methodology or procedure.
I actually like that the book talks broadly about technical concerns rather than being dogmatic about a specific approach, but the set-up is problematic because it invites blind adherence when a thoughtful application is more appropriate. The writing and the rules themselves are a bit muddled, and that can really lead readers down a wrong path. The best example is the rule “quit thinking and look”, which could be much more accurately atans not less succinctly called “stop guessing and gather data”.
I get what the author wants to say, but telling people to “quit thinking” isn’t what he means. That’s actually the opposite of what inexperienced engineers need to learn about debugging. 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. It’s short and fun because it has to be — if you’re an engineer, you’re too busy debugging to read anything more than the daily comics.
Mar 21, Bruce rated it it was amazing Shelves: A solid book on general timeless debugging principles. As I read this book I noticed I seemed to almost magically be debugging more effectively. Also, this book recommends that you learn your debugging tools well, so I learned and practiced using PyCharm’s debugger well, which has made a huge difference when I’m debugging Python code.
Sep 08, Andreea Lucau rated it it was ok.
In my view this book was too long. The rules are clear, make sense, but they were introduced by A LOT of war stories, most of them related to how you debug debugigng problem. I had some issues following all the explanation there. May 25, Michael rated it really liked it. I really enjoyed dvaid book. 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.
This is a great resource. Sep 13, Dmitri rated it it was amazing. If you’re a programmer: Jul debuging, Juraj Martinka rated it it was amazing. This is a very important, short, accessible and fun book.
It’s based on the 9 rules which form a basis for every debugging process: Understand the system 2. Make it fail 3. Quit thinking and look 4. Divide and conquer 5.
Debugging : The 9 Indispensable Rules for Finding Even the Most Elusive Bugs
Change one thing at a time 6. Keep an audit trail 7. Check the plug 8. Get a fresh view 9. If you didn’t fix it, it ain’t fix. The author goes through each rule step-by-step and present “war stories” to demonstrate the rules in action.
There’s also a chapter providing an alternative “vi This is a very important, short, accessible and fun book. There’s also a chapter providing an alternative “view from the help desk” which I’ve found very useful. It is your fundamental guide to start from “first principles”.
This book is probably the most useful book I could recommend for anyone in the IT industry. 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.
I’ve read the book before, and decided to revisit it, as I probably will every now and again. It does a great job of collecting and organizing the principles of skillfully tracking down issues.
I wish that I could make this book required reading This book is probably the most useful book I could recommend for anyone in the IT industry.
I wish that I could make this book required reading for everyone I deal with. Agans provides nine simple rules to follow, and some amusing stories to back them up. It’s a quick and fun read. As a manager, I’ve started to realize that some of these principles apply to people problems as well.
Jul 21, Matthias Ferber rated it it was amazing. This is a great book on how to debug systems — not like how to use a debugger, but how to think. 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.
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. In my favorite war story, an intermittent video-processing bug was eventually traced to the plaid flannel shirt the author happened to be wearing on the days the bug occurred.
It’s also very well-written and often funny. I borrowed it from a friend who says he recommends it to every technical person he works with.
I second that recommendation. May 15, Wangyiran rated it really liked it. Dec 09, Bob rated it really liked it. 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”. His nine common sense rules for successful computer program code and hardware troubleshooting and debugging are applicable to all fields of technical endeavor.
Dec 27, Liam rated it it was amazing. I’ll bet that many of these rules are seen as common sense in the developer communities. As a programming student this book helped me view debugging as a process, rather than a “holy shit it finally works” moment. I recommend this book to all engineers, both the students and the ones in the industry. Jan 23, John rated it really liked it.
Interesting to read a methodology around debugging. The book is well-organized entertaining and easy to read. 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. The examples were a bit dated and it helps to understand solid state electronics but the principles are sound.
Jan 03, Frank rated it it was amazing. No better book that breaks down the concept. The nine debugging rules that Agans lays out are applicable to any problem that you need to solve. Recommended for any and all troubleshooters, no matter what your field.
Debugging Rules! – Find out what’s wrong with anything, fast.
Sep 27, Mitchell rated it really liked it Shelves: Not a lot new here. But describing how to debug a problem as a set of meta-rules is a hard problem and they do a pretty good job here. Very light and lots and lots of war h but aimed to be amusing and was at least somewhat amusing and fairly short. Common sense backed with a ton of experience.