I used to use debuggers quite a bit. However, I found myself writing code without thinking it through, on the theory that whatever I wrote I could clean up using the debugger. This didn't work very well.
Now I use print almost exclusively. The trick is to stop what you're doing and think about what's happening (or not happening). Consider what must happen for things to work out as they do, and then test your idea with a well-placed print statement. Often I use a log file in order to have something I can look at carefully.
I think the decision about whether to use the debugger should not be made on the basis that the debugger is too hard. IMNSHO, one should learn it, and then see how it compares to print statements. Otherwise you may be overlooking a valuable tool. Much depends on personal preferences, and one size does not fit all.
In reply to Re: debugging - straw poll ...
by spiritway
in thread debugging - straw poll ...
by danmcb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |