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):||17 February 2008|
|PDF File Size:||17.71 Mb|
|ePub File Size:||13.36 Mb|
|Price:||Free* [*Free Regsitration Required]|
Sep 08, Andreea Lucau rated it it was ok. William Laney rated it it was amazing Jan 26, Jul 21, Matthias Ferber rated it it was amazing. If you’re a programmer: Agans is a recognized expert called in to help with tough ddbugging problems.
It took God one day to design, prototype, and release that product; talk about schedule pressure! I wish that I could make this ddebugging required reading This book is probably the most useful book I could recommend for anyone in the IT industry.
Roxana rated it really liked it Oct 23, There’s also a chapter providing an alternative “vi This is a very important, short, accessible and fun book. Be ware that the examples are predominantly hardware or mechanical, but it makes little difference. Common sense backed with a ton of experience. I guess we can forgive priority-two bugs like bunions and male pattern baldness. It changes the way readers think about debugging, making those pesky problems suddenly much easier to find and fix.
Fun to read book for all engineers! That’s actually the opposite of what inexperienced engineers need to learn about debugging.
Debugging : The 9 Indispensable Rules for Finding Even the Most Elusive Bugs
Dec 27, Liam rated it it was amazing. 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. A very interesting and funny read. Jun 26, David rated it liked it.
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 rebugging bug occurred. Account Options Sign in. Jan 03, Frank rated it it was amazing. Mar 21, Bruce rated it it was amazing Shelves: If you like books debugigng love to build cool products, we may be looking for you.
Recommended for any and all troubleshooters, no matter what your field.
It’s also very well-written and often funny. This is a great book on how to debug systems — not like how to use a debugger, but how to think.
Debuugging it fail 3. Not a lot new here. Apr 07, Tanvi rated it really liked it. Change One Thing at a Time.
The rules of battle for tracking down davic and eliminating — hardware and software bugs. Keep an audit trail 7. Get a fresh view 9. Open Preview See a Problem? I’ll bet that many of these rules are seen as common sense in the developer communities.
Also, this book recommends that you learn debugglng 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.
Debugging Rules! – Find out what’s wrong with anything, fast.
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. When the pressure is on to root out an elusive software or hardware glitch, what’s needed is a cool head courtesy of a set of rules guaranteed to work on any system, in any circumstance. Jul 09, Muhammet rated it it was amazing. Paperbackpages. I borrowed it from a friend who says he recommends it to every technical person he works with.
As a programming student this book helped me view debugging as a process, rather than a “holy shit it finally works” moment. Want to Read saving…. There’s also a chapter providing an alternative “view from the help desk” which I’ve found very useful. Pretty decent, has some interesting examples; but also much like, say, Code Complete common sense. He has worked with industrial control and monitoring systems, integrated circuit design, handheld PCs, videoconferencing, and countless other systems.
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.
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”.
Still, it’s nice to have the principles laid out. Peter Jones rated it really liked it May 30, Preview — Debugging by David J.