Yes, but only because it gives you a link to where that was run. Click the link to the right with filename:lineNumber, and it will open the sources tab to that line. Set a breakpoint and rerun to pause there, then step through the code’s execution.
Of course, if you’re using minified or processed code, this will be more difficult, in that case figure out how to do it in VS Code.
Thankfully I use python mostly and pycharm makes it easy-ish to get the debugger hooked up to a project. But learning that process definitely took a few days
I believe in a conspiracy theory that nobody uses debuggers.
console.logcounts as “a debugger”, right?It does for me!
Yes, but only because it gives you a link to where that was run. Click the link to the right with filename:lineNumber, and it will open the sources tab to that line. Set a breakpoint and rerun to pause there, then step through the code’s execution.
Of course, if you’re using minified or processed code, this will be more difficult, in that case figure out how to do it in VS Code.
deleted by creator
I work with 20 year old legacy spaghetti code, the debugger has become one of my most treasured tools.
deleted by creator
Grep log will outlive us all
I use them daily. It makes it so much easier to work with an existing code base
Yep. Once you get the hang of it, you will cringe to think of all the wasted effort that came before. But getting the hang of it takes dedication.
Thankfully I use python mostly and pycharm makes it easy-ish to get the debugger hooked up to a project. But learning that process definitely took a few days
After decades of print debugging I finally got dap up and running in vim. It is very nice. Would recommend.
Does this include C programmers? I’ve definitely found GDB to be indispensable in the past (or maybe that’s what they would want you to think).
I can record a video tomorrow if it helps?