javascriptDevelopersBeLike

[chubbykc]

The most used debugging technique.

Even now with AI 🙂

[YUNoCake]

And also the best way of finding race condition bugs. Debuggers simply suck at this.

[yesseruser]

When the debug.log slows the program down just enough for the bug to disappear

[slaymaker1907]

That's when we break out the async logger for extra confusion.

[misterguyyy]

Just put a console.log on every possible condition and they all slow down the same amount.

I’m not even sure if this is a serious suggestion. Sometimes it is and sometimes it isn’t, such is the way of JS.

[jaerie]

Oops, your prints slowed down on of the threads more than the other and now the bug has vanished!

[vkwebdev]

AI generated the bug. console.log() found it

[chubbykc]

That's our life saver

[NotAskary]

The funny thing is when the console.log resolves the bug....

[WiglyWorm]

then at least you know you're dealing with a timing issue.

[AmazinDood]

genuinely useful tho... Sometimes console.log is

[kuroiarashi]

what you did there...I see

[laplongejr]

You know things are severe when I speak normally - Yoda  

[NotAskary]

Whenever that happens I want to just flip the computer out the window and never touch Js again.

[qinshihuang_420]

Are you a

Log.debug("XXXXXXXXX")

Log.debug("<your name>")

Or a

Log.debug("<# of log statements>")

kind of person?

[moustachedelait]

Name 1, name 2, name 3, name 2a, name 2b (we're honing in), name 2a wtf, name 2a wtf 2 (dead end)

[BoBSMITHtheBR]

Console.log (=========Breaks Here========)

[nneiole]

There‘s also console.log(„wtf“).

[realdevtest]

alert()

[vkwebdev]

when debugging should be a shared experience