Debugging is as much of an art as it is a science. There are lots of great tools to help developers debug their code. I believe developers, including myself, have learned to depend too much on these tools instead of thinking through the problem. There is a common thread across all programming languages and development platforms. That thread is the way that you approach, identify, and tackle a bug. To help develop an environment of good debugging practices, I have decided to write a series of blogs on technology agnostic debugging techniques.
My first post about The Lost Art of Debugging is a blogroll of resources, both electronic and print, that developers should read to help develop good debugging techniques. Here are ten great resources on the methodology of debugging.
Web Sites & Blogs
- HackNot – Debugging 101
- Reading Tea Leaves – The Fine Art of Debugging
- Simply Breath Teching – Debugging Solutions – A Framework
- VETTY OFFICER’S WEBLOG – Debugging tips for New software engineers
- Zen and the Art of Debugging
- “Code Complete: A Practical Handbook of Software Construction” by Steve McConnell
- “Debugging by Thinking: A Multidisciplinary Approach” by Robert Charles Metzger
- “Why Programs Fail: A Guide to Systematic Debugging” by Andreas Zeller
- “The Mythical Man-Month” by Frederick P. Brooks
- “Debugging” by David J. Agans
Do you have other debugging resources that you depend on? Have you seen a great article on debugging? Do you have a debugging horror story you would like to share? Leave me a comment with your book, web site, or tale of woe.