Sat in my car for 10 minutes trying to figure out why my code broke

I was at the library on a Tuesday night working on a simple loop to sort names, and the console kept showing an error about a missing bracket. After staring at it for 20 minutes, I realized I had typed a colon instead of a semicolon on line 3. Has anyone else chased a tiny typo for way longer than they'd like to admit?

2 comments

2 Comments

lee8471mo ago

Spent three whole hours once trying to figure out why my SQL query wouldn't run. Turns out I wrote "FROM" as "FORM" and just kept reading right over it like a dummy. My coworker walked by, looked at my screen for five seconds, and just pointed at it without saying a word. Made me feel real smart that day.

emerym361mo ago

Calling yourself a dummy over a typo feels a bit much to me, @lee847. Three hours is a lot, but we've all done worse honestly. I once spent a whole afternoon debugging a script before realizing I'd used a regular colon instead of an assignment operator in one line. It happens, you laugh it off, and you move on. Your coworker pointing silently is a pro move though, no need to rub it in.