Loading…
19
Tried VS Code's debugger instead of printing every line, and I found my bug in 4 minutes
I spent two hours last Tuesday adding print statements to a small guessing game to find a loop that ran one time too many, then a friend showed me the red dot on the left side of VS Code and it just stopped the code right there. Watching the variable count climb past 5 while the loop kept going made the problem obvious, and I felt a little silly about all those prints. Does anyone actually still debug with prints, or did you all switch at some point?
1 comments
Log in to join the discussion
Log In1 Comment
jamieh7620d ago
Oh man, the print statement thing is basically a rite of passage. We have all been there, spending way too long adding console logs like we are decorating a Christmas tree, only to have someone show us one breakpoint and make us feel like we just discovered fire. The funniest part is when you realize you could have just hovered over the variable and seen the whole thing without touching the code at all. I still use prints sometimes for quick stuff or when the debugger setup is being annoying, but watching a loop counter climb past 5 while the condition says stop at 5 is a special kind of face palm moment. The red dot is honestly the best thing VS Code ever gave us and I will die on that hill.
2