Read Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems by David J. Agans Dave Agans Online

debugging-the-9-indispensable-rules-for-finding-even-the-most-elusive-software-and-hardware-problems

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. Written in a frank but engaging style, Debuggingprovides simple, foolproof principles guaranteed to help find any bug quickly. This book makes those shelves of application-specific debuggiWhen 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. Written in a frank but engaging style, Debuggingprovides simple, foolproof principles guaranteed to help find any bug quickly. This book makes those shelves of application-specific debugging books (on C++, Perl, Java, etc.) obsolete. It changes the way readers think about debugging, making those pesky problems suddenly much easier to find and fix.Illustrating the rules with real-life bug-detection war stories, the book shows readers how to:* Understand the system: how perceiving the ""roadmap"" can hasten your journey* Quit thinking and look: when hands-on investigation can't be avoided* Isolate critical factors: why changing one element at a time can be an essential tool* Keep an audit trail: how keeping a record of the debugging process can win the day...

Title : Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems
Author :
Rating :
ISBN : 9780814474570
Format Type : Paperback
Number of Pages : 192 Pages
Status : Available For Download
Last checked : 21 Minutes ago!

Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems Reviews

  • David
    2019-03-13 15:05

    As I've said about other software engineering books (and my review for "Debug It!"), there's a fair number of useful ideas in this book, and enough dubious ideas to hold back any forceful recommendation.First things first: the "9 indispensable rules" are neither a checklist nor a rubric. 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"):- are simple enough to seem useless when you first hear them,- actually contain a really useful idea that's worth internalizing,- can help you in a great number of situations, but- are also absolutely wrong in many other situations.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 (and 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.In summary: as with "Debug It!", there are useful ideas here, but they should be considered very thoughtfully.

  • Борис Кучин
    2019-03-14 15:50

    "This book tells you how to find out what's wrong with stuff, quick. 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."Примерно с этого начинается первая глава. Тут всё правда. Книга небольшая, книга весёлая и в ней всё по делу.Книга именно про отладку. Причём не делается акцент, что это должна быть отладка софта. Автор, судя по историям, успел поработать и с софтом и с железом, поэтому на чём-то одном не зацикливается. Вот есть проблема, вот правила, которые нужны применять, чтобы её найти и починить (правило про Quit Thinking and Look вот прям очень хорошее).В книге куча примеров (war stories). Многие из них не про программирование (машины, которые не заводятся; окна которые пропускают воду; видеочип, работа которого зависит от рубашки тестировщика, etc.). Из-за разнообразия, правда, не всегда понятны детали. Но читать всё равно интересно.Не могу сказать, что после прочтения я стал ошибки находить в два раза быстрее. Но в каких-то сложных случаях советы (Quit Thinking and Look, Keep an Audit Trail) реально помогали.Рекомендую. Сам прочитал два раза подряд.

  • Dmitri
    2019-03-02 12:18

    If you're a programmer: read this book!

  • Christopher Litsinger
    2019-02-26 10:00

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

  • Matthias Ferber
    2019-02-23 16:09

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

  • Wangyiran
    2019-02-21 11:49

    useful but more involve hardware, i read it,when i have to accept a project "smartwave" ,whose maintainer have leave.i constantly debug and find what and where i need.i used the way such as know the system,find bug from downstream,log the debug system and so on.so the book is useful,but i metioned the soft developer,you can read it faster at the example,the example involve more about hardware example,i can't understand it very well.because of these unuseful example and practice,so the book is more theoretical,so scan it and then get what you want get

  • Bob
    2019-02-24 12:04

    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. Highly recommended!

  • Liam
    2019-03-10 15:49

    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.

  • John
    2019-03-09 11:52

    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.

  • Frank
    2019-03-10 16:07

    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.

  • Mitchell
    2019-02-24 09:59

    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 stories but aimed to be amusing and was at least somewhat amusing and fairly short. Worth reading.

  • Арсений
    2019-03-13 15:58

    Common sense backed with a ton of experience.Pretty entertaining and able to provide insight

  • Bart
    2019-02-24 16:03

    A very interesting and funny read. Certainly a valuable addition to any debugger's bookcase.

  • David Robins
    2019-03-05 11:53

    Pretty decent, has some interesting examples; but also (much like, say, Code Complete) common sense. Still, it's nice to have the principles laid out.

  • Tanvi
    2019-03-04 09:53

    A must read for every software engineer :)

  • Muhammet
    2019-02-23 12:01

    Fun to read book for all engineers! Useful and applicable methods for debugging. Note that the book is not technical.

  • Chris Lim
    2019-03-03 16:01

    A must read for all engineers and programmers.