Summary

This chapter started out defining bugs and describing process problems that contribute to bugs. Then it discussed what you should know before you start debugging. Finally, it presented a debugging process that you should follow when you debug your code.

The best way to debug is to avoid bugs in the first place. If you plan your projects properly, have a real commitment to quality, and learn about how your products fit with their technologies, the operating environment, and the CPU, you can minimize the time you spend debugging.

The key thought I want to leave you with is this: while debugging is difficult and can sometimes make you feel overwhelmed when faced with an impossible problem, it's only a temporary solution. What makes debugging hard is that almost none of us have had any education in debugging, so we've all learned it on the job piecemeal. In fact, when I was in college getting my bachelor's degree in Computer Science, I asked about debugging, and my entire debugging training consisted of the following: "Don't write bugs in the first place." You can learn to debug better, and I hope this chapter has started you on your way.