Loading…
3
Spent 2 hours stuck on a typo in my first JavaScript project and almost gave up
I was sitting at my kitchen table in Boise at like 11pm last Wednesday, my code kept throwing an error and I could not figure out why. Turns out I typed a comma instead of a semicolon on line 47, and once I fixed it everything ran fine. Does anyone else spend way too long on tiny stuff like this when they are just starting out?
1 comments
Log in to join the discussion
Log In1 Comment
janac5114d ago
Laughed when I read this because I did almost the exact same thing but with a curly quote that my editor snuck in. Spent a whole Saturday morning staring at it, googling stuff like "javascript error not making sense," even closed my laptop and went for a walk to cool off. Came back, zoomed in on the code, and there it was, one dumb little character that looked fine to my eyeballs but was not the right one at all. The worst part is these mistakes never feel like real coding problems, they just feel like getting tripped by your own shoelace. Fixing it took two seconds and I felt both relieved and kind of dumb at the same time. For what it's worth, that feeling never totally goes away, you just get faster at spotting the dumb stuff as you go.
6