countdown boutiques-francophones Learn more vpcflyout home All-New Kindle Music Deals Store sports tools Registry

Customer Reviews

5.0 out of 5 stars
5.0 out of 5 stars
5 star
4 star
3 star
2 star
1 star

Your rating(Clear)Rate this item
Share your thoughts with other customers

There was a problem filtering reviews right now. Please try again later.

Showing 1-8 of 8 reviews(5 star). Show all reviews
on January 29, 2003
An excellent book of reference for novice to medium level user.
Mr. Agans' book presents real life experiences, or as he calls them war stories and humor filled comment/anecdotes.
I find myself chuckling and giggling along while reading this
book, some of what he said brought back my own memories while
working/debugging on my own software bug(s), or other people's
bug(s) that I have somehow 'inherited' because they left the
company, or are too busy on other projects to debug their own
code. I like the metaphors that he uses to explain ideas or
concepts that seems a bit too complicated to understand.
Mr. Agans made this very clear in the beginning of his book;
the book is not a cover-it-all book, it is a general concept
book on how to isolate, find, and debug something that has gone
wrong. The principles presented by Mr. Agans can be applied to
situations covering everyday life. He presented examples of well
pump and light bulb, etc...
More experienced software/hardware engineers or more experienced
problem solvers who read this book might find it covering bases
that they already know, but the humor makes it worth while.
0Comment|Was this review helpful to you?YesNoReport abuse
on December 4, 2002
Debugging leads to quality products and competitive success. This book is the result of twenty years experience in troubleshooting hardware and software products. Agans documented his nine rules for debugging, and explains each one in a chapter. You can read this to get ideas for solving problems in a systematic way.
His first rule is "understand the system", another way to say "don't assume" or "read the manual". [His comments on "a politician" tells me he should follow rule #1 (p.18).] Sometimes the constraints of time and money will not let you capture enough information; management will set the rules and schedules.
The "quit thinking and look" rule says that facts should drive theories (like in criminal detection). Making a list of probable causes can be a guide to research. Page 54 tells of a bug in "one small, simple software routine". Is code inspection passe? Page 65 tells of a light not going on. Based on MTBF, its more likely the light bulb than the switch. But don't overlook the possibility of the connection at the receptacle.
"Divide and Conquer" would be better phrased as "narrowing the search" for a faulty component in a planned, logical manner. Changing one thing at a time advises against trial and error, or guessing at the solution. Keeping track of all changes allows narrowing the search, and any possible interaction with an earlier change.
"Check the Plug" suggests using a PRINT statement that works all the time, not just for a certain event. This is not practical advice in my experience! You should test the tool before using it for testing; recalibration is always good. "Get a Fresh View" is another way to restate the problem. When doing this you may suddenly realize what you've overlooked. Often someone has come across the same or similar problem. It can also be good politics to delegate responsibility.
Page 125 describes the classic "dirty gas filter" syndrome. Consider getting the gas lines blown out. A locking gas cap is one way to prevent this; don't overlook sabotage as a cause. "In the old system we knew how to crash it so they'd send us out on break." Chapter 11 recommends testing a fix by removing it to prove the change. This rules out any random differences; except when its obvious (p.128). Some problems do go away by itself. I once worked on a serially-reusable on-line program. After I made it reentrant (so it didn't modify the code) a lot of strange bugs just disappeared.
Chapter 13 gives a number of examples using the rules. The touchpad problem could have been avoided with either code inspection or programming standards. Or a better compiler? Chapter 14 tgells how the rules apply to a Help Desk. The last chapter suggests how to use this book at work or in school. But if your job resembles Dilbert's, bring your resume up to date (the tenth rule?).
0Comment|Was this review helpful to you?YesNoReport abuse
on November 21, 2002
David Agans does a great job of explaining how to approach debugging as a science rather than an art. If you're a novice programmer, the information here will prove invaluable; discovering how to debug effectively on your own can take many years.
Experienced programmers may consider most of the rules to be obvious; however, those same programmers might be surprised to find how many of these obvious rules they neglect to follow. I've been debugging for more than 20 years, and still learnt some useful new tricks.
Peppered throughout the text are a large number of war stories from the author's own experience with embedded systems. As well as illustrating how to (and more commonly, how not to) approach a particular problem, these are all well written and often entertaining.
Some of my favourites: how wearing the wrong shirt to work caused a new video compression chip to crash; teenagers coming home from school subtly altering the behaviour of a video conferencing system; a vacuum cleaner that made the house lights flash on and off; a noisy read/write line that led a junior engineer to mistakenly redesign an entire co-processor memory circuit; and the self-test feature on an old Pong video game.
Although most examples are hardware related, the approach described can be applied to almost any problem; indeed, several of the examples used have nothing to do with computing.
This is not a large book, but it's well laid out, easy to follow, and doesn't talk down to the reader. It's also packed with enough meat to satisfy the hungriest of programmers. Highly recommended.
0Comment|Was this review helpful to you?YesNoReport abuse
on June 3, 2003
This book is very useful for beginners and intermediate programmers. "Debugging" is full of practical advice on debugging in general. It is not tied to any particular programming language.
The book describes 9 main debugging "rules", and many smaller "sub-rules". The rules (such as "Make it fail" or "Quit thinking and look") and sub-rules (such as "Start from a known state" or "Build instrumentation in") are derived from common sense and years of experience. Many people know most of the rules, but perhaps do not systematically follow them. "Debugging" clarifies and makes a systematic review of the debugging practices, with examples taken from real life, simplified to remove the jargon.
The book is quite funny and makes enjoyable reading. I am looking forward to more: perhaps we can see more stories in the next edition, or in a companion volume, or on the debugging rules web site.
0Comment|Was this review helpful to you?YesNoReport abuse
on May 11, 2011
I really liked this book. The author did a good job of taking what would normally be a dry and unmotivating topic, distilling it down to its essentials and conveying the messages through entertaining anecdotes. He also included a number of "apply the lessons" type exercises toward the end of the book, which serves to reinforce the concept. This is well worth the money, and should be required reading for anyone entering the work force from college or university -- or even during their studies.
0Comment|Was this review helpful to you?YesNoReport abuse
on November 2, 2002
An absolute must for any problem solver. Mr. Agans offers a plain-speaking approach to cracking the trickiest engineering problems -- an approach that frankly can be extended to other types of problem solving. The author has "dealt" us a real classic -- makes this topic as intuitive as "do-re-mi".
0Comment|Was this review helpful to you?YesNoReport abuse
on November 20, 2002
This book reads more like a novel than a how-to book. Every rule is well illustrated with "war stories" that are as entertaining as they are enlightening. A must read for anyone that chases bugs, no matter what their level of exptertise!
0Comment|Was this review helpful to you?YesNoReport abuse
on October 28, 2015
This book completely changed my way of looking at problems. I have been in tech for 10 years and it has formed the foundation of how I attack hard technical issues. Every support engineer, developer and manager should read this book
0Comment|Was this review helpful to you?YesNoReport abuse

Need customer service? Click here