Loading…
10
Question about the "explain it out loud" trick a guy at a meetup in Tucson mentioned
So I was at a small code meetup in Tucson last Thursday and this guy next to me was stuck on a for loop that kept spitting out the wrong total. He started talking to himself, literally out loud, saying stuff like "okay so this thing goes in, then it gets multiplied, wait no." And like 30 seconds in, he stopped and said "oh, it's resetting my counter inside the loop." I asked him about it after and he told me he does this every time and it works better than staring at the screen. I tried it on a while loop that kept running forever in my own project and I caught it in under a minute. Something about hearing the steps in my own voice makes the bad part stand out way more than reading it. Now I keep a notebook and sort of narrate, even when my roommate thinks I'm losing it. Has anyone else tried saying their code out loud to find a bug, and does it work for harder stuff like nested functions?
0 comments
Log in to join the discussion
Log In0 Comments
No comments yet
Be the first to share your thoughts on this discussion.