“The most effective debugging tool is still careful thought, coupled with judiciously placed print statements.”
- Brian Kernighan
- Brian Kernighan
I fall back on debuggers when the environment is hostile: Half understood code from someone else, unreliable hardware (like embedded), or debugging memory dumps.
But before both, the initial approach is thinking deep and hard, and reviewing all available evidence like logs. If this is not enough, I try to add better troubleshooting abilities for the future.