Over the next few months, I’m going to do a short series on debugging. Admittedly, debugging is boring, soul crushing and deadly, deadly dull but it must be done.
You can follow this deeply dreary topic on debugging techniques, should you please.
This short series will cover the methods I’ve found through during my experience on many web app projects and those I found, liked and stolen from a selection of the books on the subject.
Why?… because debugging – or just solving apparently complex problems – is what I spend most of my life doing. Every problem starts as a black box and usually ends up being fixed by a few lines of code, if not less. The question is: how to avoid spending your entire life on 3 lines of code.
The techniques I’ve found for solving problems aren’t based on particular tools, programs or programming languages. They apply to many situations because they’re about solving problems, dealing with information, coming up with ideas…
Here’s some of the things I’ll cover:
- Before you even type one line of “fixing” code. The bug fixing cycle.
- Logic tools and problem solving for programmers.
- Ways of gathering information.
- Hot to find a cause.
- How to understand the system.
- Causes of bugs.