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):||2 August 2009|
|PDF File Size:||9.33 Mb|
|ePub File Size:||19.4 Mb|
|Price:||Free* [*Free Regsitration Required]|
The rules are clear, make sense, but they were introduced by A LOT of war stories, most of them related to dzvid you debug hardware problem.
Follow the Author
Paperbackpages. The author goes through each rule step-by-step and present “war stories” to demonstrate the rules in action. I get what the author wants to say, but telling people to “quit vebugging isn’t what he means. It changes the way readers think about debugging, making those pesky problems suddenly much easier to find and fix. Still, it’s nice to have the principles laid out.
Lists with This Book. Fun to read book for all engineers! The examples were a bit ddebugging and it helps to understand solid state electronics but the principles are sound. I was quite pleasantly surprised the author managed to reduce the skill to nine short rules particularly when it sometimes aganz be a process that is difficult to explain.
I’ve read the book before, and decided to revisit it, as I probably will every now and again. Check the plug 8.
His nine common sense rules for successful computer program code and hardware troubleshooting and debugging are applicable to all fields of technical endeavor. As a manager, I’ve started to realize that some of these principles apply to people problems as well. I’ll bet that many of these rules are seen as common sense in the developer communities. The debgging and the rules themselves are a bit muddled, and that can really lead readers down a wrong path. Want to Read Currently Reading Read.
Common sense backed with a ton of experience. A must read for every software engineer: Get a fresh view 9. Sep 27, Mitchell rated it really liked it Shelves: Victor Grigoriu rated it it was amazing Jun 13, dagid I recommend this book to all engineers, both the students and the ones in the industry. 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: No better book that breaks down the concept. Jul 09, Muhammet rated it it was amazing. 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.
If you’re a debuggiing Keep an audit trail 7. Make it fail 3. It’s a quick and fun read. Jul 21, Juraj Martinka rated it it was amazing. May 25, Michael rated it really liked it.
Debugging Rules! – Find out what’s wrong with anything, fast.
Jul 16, David Robins rated it really liked it. Jan 03, Frank rated it it was amazing.
There’s also a chapter providing an alternative “vi This is a very important, short, accessible and fun book. 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 debhgging blind adherence when a thoughtful application is more appropriate. Divide and conquer 5.
David A. Wheeler’s Review of “Debugging” by David J. Agans
William Laney rated it it was amazing Jan 26, Aug 24, Bart rated it it was amazing. The nine debugging rules that Agans lays out are applicable to any problem that you need to solve. It is your fundamental guide to start from “first principles”. As I’ve said about other software engineering books and aganns review for “Debug It!
Jun 26, David rated it liked it.
It’s also very well-written and often funny. That’s actually the opposite of what inexperienced engineers need to learn about debugging. Interesting to read a methodology around debugging.
Certainly a valuable addition to any debugger’s bookcase. 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”. Quit thinking and look 4. Thanks for telling us about the problem. I guess we can forgive priority-two bugs like bunions and male pattern baldness.
Understand the system 2. It took God one day cavid design, prototype, and release that product; talk about schedule pressure! Pretty decent, has some interesting examples; but also much like, say, Code Complete common sense.
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.