Recently I read two fantastic books about debugging. I think they might be useful to others, especially for junior programmers :-)
The first one is "The Developer's Guide to Debugging". This book is very pragmatic and thin. It is only 2xx pages. But its length doesn't mean its content is shallow. In the contrary, it is very dense. It covers wide range about debugging, including debugger usage(basic and advanced tricks), memory leak and corrupt detection, profiling(memory and CPU), parallel issues, environment issues, linking issues, how to write debuggable code, static checking and how to integrate all of them with system thinking!! I have this book years ago but realize its value after programming several years. My bad.
The second one is "Why Programs Fail". The author is know for his work for creating DDD. This book shows the "science" perspective of debugging. It tackles an advanced issue: automatic debugging. If you want to know the current stage of debugging but without enough time to do research. This book is for you.
All in all, if you do not have much time and eager to know the common tricks, read the first book. If you have some programming experience and desire to know how debugging experts think, read both books. They are worth reading. I promise. :-)
All in all, if you do not have much time and eager to know the common tricks, read the first book. If you have some programming experience and desire to know how debugging experts think, read both books. They are worth reading. I promise. :-)
留言
張貼留言