Am I the only one who thought rubber duck debugging was a joke until it actually fixed my bug?
I always rolled my eyes at the rubber duck thing in coding tutorials. Sounded like a silly meme from some old book. Then last week I got stuck on a loop in my little Python coin flip game for two evenings straight. My friend told me to just explain the code out loud to a rubber duck I had on my desk from a trip to Portland. I felt dumb doing it but I said each line out loud. About line 12 I heard myself say 'and here the counter resets' and I froze. I was resetting it inside the loop instead of after it. I fixed it in 10 seconds and my jaw dropped. Now I keep that duck next to my monitor. Has anyone else had a silly trick like this actually work, or am I just easy to convince?