"This comprehensive book on debugging techniques is a must-read for all novice programmers and provides a good value for advanced software developers. Debugging by Thinking describes various approaches to debugging and fills in a long-time gap in the software engineering library. 'To err is human'—software developers may know this fact better than other engineers. Debugging offers the only help for code errors, and this book analyses it as a mental discipline. After reading this book, your debugging will no longer be an ad hoc activity, and will become better organized and more efficient."&151; Dr. Piotr Findeisen, Systems & VLSI Technology Division, Hewlett-Packard Company "Buy a copy of Debugging by Thinking for every programmer in your organization&151;it will help them to tackle debugging in a thoughtful, systematic, and effective way."&151;Richard Goldhor, VP of Engineering, Enounce, Inc. Debugging by A Multi-Disciplinary Approach uses the methods of literary detectives such as Sherlock Holmes, the techniques of mathematical problem solving, the results of research into the cognitive psychology of human error, the root cause analyses of safety experts, the compiler analyses of computer science, and the processes of modern engineering to define a systematic approach to identifying and correcting software errors. Its unique features include * Language Independent Examples are given in Java and C++ * Complete source code shows actual bugs, rather than contrived examples * Examples are accessible with no more knowledge than a course in Data Structures and Algorithms requires * A "thought process diary"shows how the author actually resolved the problems as they occurred
Book has a very catchy title (only 'Don't panic' written in large, friendly letters would've done the job better). Other than this the is a rather summation and it's quite dry and boring to go through ...