The rules of battle for tracking down -- and eliminating -- hardware and software bugs. 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, 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. 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 qqroadmapqq 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 dayFigure 1-1. When to Use This Book. actual problem so you can fix it, and then make sure you really fixed it so you can go home triumphant. ... Software engineers debug; car mechanics troubleshoot. Car designers debug (in an ideal world).
|Author||:||David J. Agans|
|Publisher||:||AMACOM Div American Mgmt Assn - 2002-09-23|