My first hackathon crash taught me to read error logs top to bottom

Back in March I joined a 48 hour hackathon in Chicago and spent 6 hours stuck on a bug where my app just showed a blank screen. I kept tweaking the code, refreshing, nothing worked. Finally a mentor sat down and made me scroll to the very first line of the console error, not the last one. Turns out I had a missing closing bracket on line 3, but I was looking at the crash report on line 200. Now I always start debugging from the top of the log and it saves me so much time. Anyone else have a moment where the simplest habit just clicked for them?

0 comments

Log in to join the discussion

Log In

0 Comments

No comments yet

Be the first to share your thoughts on this discussion.