Spent 2 hours debugging a missing semicolon in JavaScript

I was staring at my code for what felt like forever. Console kept throwing an error but I skimmed right past the line. My buddy looked over my shoulder for 5 seconds and pointed at line 47. Felt dumb but now I slow down and actually read each line before running it. Anyone else do this more than they'd like to admit?

3 comments

3 Comments

oliver7192mo ago

Isn't that always how it goes?

shanegibson2mo ago

Read some mechanics saying they deliberately lowball the timeline so you don't go to another shop, knowing full well it's gonna take longer. Kinda feels like the old bait and switch but with hours instead of prices.

clairer792mo ago

Exactly. It's like clockwork with the repair shop near me on Main Street. They quote three days for a simple brake job and then call you a week later saying they found "unexpected issues." How many times do you need to find the same unexpected problem before you start expecting it? Do they have a dartboard in the back they throw wrenches at to decide the timeline? I get parts delays exist but at some point it stops being bad luck and starts being bad planning.