Other Sellers on Amazon
+ $3.99 shipping
+ Free Shipping
+ $3.99 shipping
Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems Paperback – Illustrated, January 1, 2006
"Devoted" by Dean Koontz
For the first time in paperback, from Dean Koontz, the master of suspense, comes an epic thriller about a terrifying killer and the singular compassion it will take to defeat him. | Learn more
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Frequently bought together
Customers who viewed this item also viewed
IEEE Software magazine: "Unlike most books about debugging, this book isn't a technical manual. It's easy to follow and logical in approach and progression. The author elegantly presents the concepts and makes the debugging task unintimidating but, at the same time, points out that the major task is learning to apply his rules. Debugging not only makes the subject area easy to understand; it's an excellent example of how you can present the art of debugging in a way that's meaningful and exciting. This book should be required reading for all technology college students. It explains the logic you need in the real world, logic that so many students don't learn before graduation. After reading this book, I got excited about debugging and went out to look for something to test the ninerule approach on.""
Slashdot.com, David A. Wheeler: “It's not often you find a classic, but I think I've found a new classic for software and computer hardware developers. It's David J. Agan's Debugging….It's hard to bottle experience; this book does a good job. This is a book I expect to find useful many, many, years from now….I think this is a great book….Novices need to learn the fundamentals, and pros need occasional reminders of them; this book is a good way to learn or be reminded of them. Get this book.”"
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 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
- Item Weight : 12 ounces
- Paperback : 192 pages
- ISBN-10 : 0814474578
- ISBN-13 : 978-0814474570
- Product Dimensions : 6.75 x 0.5 x 9.88 inches
- Publisher : AMACOM; Illustrated Edition (January 1, 2006)
- Language: : English
- Best Sellers Rank: #263,851 in Books (See Top 100 in Books)
- Customer Reviews:
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
One of the great things about this book is that it's generalistic in nature, not specific. Agans's decades of troubleshooting experience has given him great insight on how to go about debugging in all sorts of environments, so he lays out nine rules for approaching any problem:
Understand the System
Make it Fail
Quit Thinking and Look
Divide and Conquer
Change One Thing at a Time
Keep an Audit Trail
Check the Plug
Get a Fresh View
If You Didn't Fix It, It Ain't Fixed
Debugging isn't an art performed only by folks with some odd genetic disposition, it's a critical craft which can and must be learned. I was fortunate to have some good troubleshooters as mentors during my days working radar inflight in the Air Force, but I've fallen out of many of the good practices those folks beat^H^H^H^Hinstilled in me. Agans's book is helping me pull out of the thrash and churn mode of debugging.
This book's only 175 or so pages long and is well-worth adding to your library. Actually, substitute "a critical addition" for "well worth adding". I'm also going to make sure this book gets added to the professional development reading list I'm working on creating.
As per pros for the book:
* Rang true with me by stating, don't get lost in the details, but actually get in there and LOOK at the problem - not read about it.
* Good stories and examples
* Good flow and not boring
* Good techniques for problem solving
* Good price for the content
* Reads a bit like a personal opinion like rant
* Needs a bit more editing (small typos)
* Slightly repetitive (but I understand that this may have been a literary tactic)
Honestly, this was a good read and I would gladly recommend this book for any person attempting to improve their thought process regarding debugging or solving problems. Undergraduate and graduate students + professors should seek to read this book or have it among the required readings for advanced programming classes.
Interestingly enough, I think some programmers do make pre-assumptions when troubleshooting. This set of debugging rules advice against the pre-assumptions and stick with scientific methodologies.
Even if you are not a software developer or an engineer, this book is still valuable. Members of the QA team and help desk can also benefit from this book. It will help you in your troubleshooting efforts and also allow you to file bug reports that contain good data.
This book is only 175 pages, it is an easy read ... but it is filled with practical advice. Great job David!
Top reviews from other countries
I keep the nine rules printed out next to my PC which helps me course-correct whenever I start getting lost in the weeds.
This should be required reading for new developers. It will easily pay for itself a hundred times over given the amount of time it will save you!
This book is especially of more relevance to current students as it trains them to approach each problem in a methodical way. That said, seasoned professionals can also learn a thing or two from it.
By the word 'debugging' most of us will think of software, but the book shows us that the described techniques work well for both software and hardware.
The many experiences the author shares with the reader, in the form of 'war stories', make it not only and educational but also a light and entertaining read.
If you think your debugging techniques leave room for imrovement? Start reading this book!
If you think your debugging techniques cannot be improved?
Well, you definitly should read this book!
Quite a light-hearted style and lots of humour so its not a difficult book to read either.
If your an engineer in the computing field, this is one for your bookshelf.