Pro tip: I keep seeing beginners in my online study group skip the simple console.log when they debug.

They jump straight into complex debuggers for a basic syntax error, but just adding console.log('got here') after line 15 in my last project saved me an hour of staring at the screen, so what's your go-to first step when something breaks?

3 comments

3 Comments

mason.brian5d ago

Honestly, console.log is my first move every single time. Tbh, it's just faster to throw a few logs in and see where the code actually stops working. Ngl, I've wasted hours in a fancy debugger only to realize I missed a simple typo that a log would have caught in seconds. Starting with the simplest tool keeps you from overcomplicating things right away.

sarah_hart5d ago

Right there with you... logs are my go-to for everything.

mila_harris5d ago

But is it really that big of a deal? It's just a quick way to check your work.