Spent 2 hours fixing a typo that was sitting in plain sight

Last Tuesday I was helping my cousin debug his first Python script, a simple calculator thing. He kept getting a NameError and we both stared at the screen for what felt like forever. Turns out he wrote 'pirnt' instead of 'print' on line 3, and neither of us caught it until I read it out loud word by word. I told him that's why I keep a rubber duck on my workbench, sometimes saying the code out loud just clicks. Has anyone else had a bug that took way too long because you assumed the error was somewhere smart?

1 comments

1 Comment

gonzalez.vera5d ago

The duck thing never worked for me, a second pair of eyes beats it every time.