Stop skipping the rubber duck step in debugging

I watched a guy in our study group burn 2 hours on a typo in a variable name last Tuesday, and he just kept adding console.logs. Talking through your code out loud to a rubber duck or even a mug catches dumb mistakes way faster, has anyone else found that works better than staring at the screen?

0 comments

Log in to join the discussion

Log In

0 Comments

No comments yet

Be the first to share your thoughts on this discussion.