The worst part of console.log “debugging”, though, is that I've wasted hours – near days at times – trying to find the right place to put just one more console.log statement so that I could sift through dozens of them in the console output… only to realize that I'm STILL not logging the right information at the right time, or that I'm logging the right thing but at the wrong time!
And who hasn't accidentally deployed a console.log statement in to a production website, only to have the people using the site complain that the site is broken? It's happened to me, it's happened to my friends and colleagues, and it will continue to happen as long as we continue to abuse console.log.
Use A Debugger!
(There's also a bit of a bonus in the Visual Studio episode: it will show you how to build and run NodeJS apps directly in Visual Studio!)