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):||6 November 2012|
|PDF File Size:||13.37 Mb|
|ePub File Size:||11.98 Mb|
|Price:||Free* [*Free Regsitration Required]|
No better book that breaks down the concept. If you’re a programmer: I guess we can forgive priority-two bugs like bunions and male pattern baldness.
Debugging : The 9 Indispensable Rules for Finding Even the Most Elusive Bugs
Agans provides nine simple rules to follow, and some amusing stories to back them up. Mitochondrion rated it it was amazing Nov 09, Quit thinking and look 4.
Ddavid helps you keep track of books you want to read. Sep 13, Dmitri rated it it was amazing. 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.
David A. Wheeler’s Review of “Debugging” by David J. Agans
As a manager, I’ve started dehugging realize that some of these principles apply to people problems as well. 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”. A must read for all engineers and programmers. I’ve read the book before, and decided to revisit it, as I probably will every now and again. Victor Grigoriu rated it it was amazing Jun 13, The book is well-organized entertaining and easy to read.
Keep an audit trail 7. I’ll bet that many of these rules are seen as common sense in the developer communities. Change one thing at a time 6.
Sep 27, Mitchell rated it really liked it Shelves: I get what the author wants to say, but telling people to “quit thinking” isn’t what he means.
Written in a frank but engaging style, Debugging provides simple, foolproof principles guaranteed to help find any bug quickly. Not a dsbugging new here. It is your fundamental guide to start from “first principles”.
This is a great book on how to debug systems — not like how to use a debugger, but how to think. Ann rated it it was ok Aug 19, 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. Want to Read saving….
Peter Jones rated it really liked it May 30, Get a Fresh View.
To ask other readers questions about Debuggingplease sign up. Other editions – View all Debugging: As I’ve said about other software engineering books and my review for “Debug It!
Interesting to read a methodology around debugging. 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. Change One Thing at a Time.
As a programming student this book helped me view debugging as a process, rather than a “holy agams it finally works” moment. It changes the way readers think about debugging, making those pesky problems suddenly much easier to find and fix. If you didn’t fix it, it ain’t fix. Refresh and try again. 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.
His nine common sense rules for successful computer program code and hardware troubleshooting and debugging are applicable to all fields of technical endeavor. The View from the Help Desk. I second that recommendation.
This is a very important, short, accessible and fun book.