Loadingā¦
4
My for loop ran for 3 hours because I missed one lousy equals sign
I was writing a basic while loop for a guessing game last Tuesday and forgot to update the counter, so it just spun forever and my laptop fan sounded like a jet. I sat there staring at the screen for way too long before my friend looked over and spotted it in like 5 seconds. How do you all catch those tiny bugs without losing your mind?
2 comments
Log in to join the discussion
Log In2 Comments
ray72312d ago
Print statements got me through CS 101 too, but honestly rubber duck debugging is faster. Explain the loop out loud to an actual object and you'll hear the missing counter update in your own voice.
2