Loading…
11
Spent 3 hours stuck on a missing semicolon in my first JavaScript project
I was sitting at my kitchen table in Boise last Tuesday trying to get a simple calculator to work for my intro to coding class. Kept getting a blank screen and had no clue why, so I copied my code into the browser console and it finally showed me the error was on line 47. Turns out I forgot one semicolon after a function call and that was it. My teacher said this happens to everyone at least once, so now I'm wondering how long it took other people to stop making this mistake.
1 comments
Log in to join the discussion
Log In1 Comment
robinmason25d ago
That line 47 error hits hard. I remember spending a whole weekend on the same thing back when I started, and the worst part is the browser gives you nothing until you open the console. Here is the real answer though: you never fully stop making it, you just get faster at finding it. After a few months your brain starts checking the ends of lines on autopilot, and most code editors will flag it for you with a red squiggle. My advice is turn on a linter in whatever editor you use, because it catches missing semicolons before you even save the file. Three hours on your first project is honestly normal, so do not sweat it.
8