The 2AM stack trace that flipped my opinion on rubber duck debugging
I used to think talking to a rubber duck was the dumbest thing ever. Last week I was stuck on a null pointer in my Python script for 3 hours, super frustrated. My buddy on Discord told me to explain each line out loud to my cat, and I laughed at him. Actually tried it with my tabby named Pixel, and by line 12 I realized I was checking the wrong variable name. It took me 20 minutes to fix the whole thing after that. Has anyone else had a dumb simple trick like this actually work when you were deep in the weeds?