Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems
| Author | : | |
| Rating | : | 4.99 (823 Votes) |
| Asin | : | 0814474578 |
| Format Type | : | paperback |
| Number of Pages | : | 192 Pages |
| Publish Date | : | 2016-04-06 |
| Language | : | English |
DESCRIPTION:
It's easy to follow and logical approach and progression." -- IEEE Software magazinethe book lays out sensible strategies and tactics, clearly based on years of experience and reflection. -- BIZLIFE June 2003. "get this book.Its stories and examples are amusing and instructive." -- Test & Measurement World"a short but invaluable work dedicated to helping you hunt down pesky problems online and off." -- New.Architect magazine, February 2003"I have printed out his rules and expect I'll lend this book out frequently." -- Dr.Dobb's Journal,Gregory V. -- GlobeTechology February 2003Problem-solve
jiang siyu said A book that helps you effectively troubleshoot and you don't end up wasting a bunch of time detouring. I'm a professional programmer for less than "A book that helps you effectively troubleshoot and you don't end up wasting a bunch of time detouring" according to jiang siyu. I'm a professional programmer for less than 2 years, however my debugging skill stands sharp amongst my team, owing to this book. I cannot believe how powerful these debugging rules are. For example, one time I have to troubleshoot a very tricky race condition issue. The rule "quite thinking and look" forced me not to make any pre-assumptions, and rather look into the loggings and the data in the database. Along with "divide and conquer", I was able to narrow down the amount of data to look into and find it is . years, however my debugging skill stands sharp amongst my team, owing to this book. I cannot believe how powerful these debugging rules are. For example, one time I have to troubleshoot a very tricky race condition issue. The rule "quite thinking and look" forced me not to make any pre-assumptions, and rather look into the loggings and the data in the database. Along with "divide and conquer", I was able to narrow down the amount of data to look into and find it is . This is how you debug stuff - life hacking style Niklas Andersson If you have 10-20 years of experience I guess you know most of the rules outlined in this book already. It won't give you any code examples though. More like sharpening your mindset when it comes to problem solving. But hey, I don't regret that I read it, and I suppose you won't regret it either.. Debugging made easy Gabor Szakacs 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!
. Agans is a recognized expert called in to help with tough debugging problems. He currently runs PointSource, a computer systems consultancy. He has worked with industrial control and monitoring systems, integrated circuit design, handheld PCs, videoconferencing, and countless other systems. David J
Written in a frank but engaging style, Debugging provides 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. 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. The rules of battle for tracking down -- and eliminating -- hardware and software bugs. 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"