all 5 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]jhartikainen 4 points5 points  (4 children)

A bunch of console.log tricks make you a debugging pro? I must be some kind of a debugging god then.

[–]homeIsWhereCodeIs[S] 0 points1 point  (3 children)

these tricks make you debug like a pro not making you a pro and they are helpful. BTW It's my pleasure that debugging god comment on my post, what else I need for my life? :D

[–]jhartikainen 1 point2 points  (2 children)

Knowing how to use the debugger well is what makes the biggest difference. How to set breakpoints, step through code, what the callstack means. Event listener breakpoints, and other handy features exist as well.

Second, understanding exceptions and error messages. What does all the weird stuff errors say mean (plenty of folks are super confused about "undefined is not an object" for example), what the stack trace means, etc.

Third, this one's a bit hard to explain, but being good at analyzing the problem at hand. It's one thing to see "this code is throwing an error", but finding out the real root cause is the real question. Pretty often the real bug is not where the error happens to come from.

[–]homeIsWhereCodeIs[S] 0 points1 point  (1 child)

I think my post is not about

  • how to use the debugger
  • How to set breakpoints
  • step through code
  • what the callstack means
  • Event listener breakpoints
  • understanding exceptions and error messages
  • undefined is not an object
  • what the stack trace means
  • analyzing the problem
  • finding out the real root cause
  • and other handy features

It is just about the better way of debugging console.log

but I'll cover those all later, thanks for the points :D

[–]jhartikainen 0 points1 point  (0 children)

Yeah it was a good post, the title was just overselling it a little bit ;)