25
The amount of people who skip basic error reading is wild
I keep seeing posts where someone's code breaks and they just paste the whole thing asking for help. Nine times out of ten, the error message tells you the exact line and what's wrong. Last week, a friend spent 3 hours stuck because of a missing comma, and the console said 'SyntaxError: unexpected token' with an arrow pointing right to it. It's like having a map to the treasure but refusing to look at it. Learning to read those messages is the first real skill you need. How did you guys finally start to understand what the errors were trying to say?
2 comments
Log in to join the discussion
Log In2 Comments
the_sandra2d ago
Was there a point where it just started making sense? For me, it was getting the same type of error over and over until I had to learn its pattern. Like @davis.diana said, one error can make it click, but for me it was more about building a list in my head of what common ones mean. A "ReferenceError" means it can't find a thing, a "TypeError" means it found the thing but you're using it wrong. Once you have that basic decoder ring, the details in the message start to actually help instead of just looking like noise. It turns from a scary wall of text into a simple checklist.
3