Why does everyone skip the part about reading the error message?

I spent a whole afternoon last week watching my code fail on line 12 and I kept tweaking the variables, changing the math, even rewriting the whole loop. Then my buddy came over, looked at the console for two seconds, and pointed at the error text that literally said 'missing semicolon on line 12'. I felt so dumb. It happens to me all the time because I get excited to fix something and jump straight to guessing. Since then I make myself read the error out loud before touching anything, and it's saved me like an hour on each bug. Does anyone else have a habit of skipping the obvious clue and just poking around until it breaks more?

1 comments

Log in to join the discussion

Log In

1 Comment

wesleyjohnson2mo ago

Man, I felt that. Reading it out loud is the real trick.

8