Simple debugging like described here is a basic level. You start to use console.log when debugger is not enough (e.g. time-dependent issues, races, event processing).
That's not a very nice way of expressing a difference of opinion.
Maybe. But it's neither nice to say "you are doing it wrong" to people who are better than you in debugging (they can use both debugger and logging while author mastered interactive debugging only)
Thanks for reading. You are correct in saying that this article is simple and basic. The intended audience is for developers who are unaware of browser debugging tools.
I also agree that there are times when using the debugger is not enough. Nevertheless, I am not a master in interactive debugging 🙂. There's much room for improvement and I am still learning like everyone else.
Loving this community engagement!
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.