I have used them occasionally. It’s sometimes easier to use logging because you can dump an enormous amount of information and quickly then look through it if you already know what kind of information you want to look at. Debuggers are better when you have no idea what the hell is going wrong and need to get a little bit of info from everything instead of a lot of info from one thing.
I also work with 20 year old spaghetti code, but my software is primarily middleware and debuggers aren’t allowed on the full system where I’d actually be able to reproduce the issue. Insane amounts of logging statements have become my most treasured tool.
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.
I have used them occasionally. It’s sometimes easier to use logging because you can dump an enormous amount of information and quickly then look through it if you already know what kind of information you want to look at. Debuggers are better when you have no idea what the hell is going wrong and need to get a little bit of info from everything instead of a lot of info from one thing.
I work with 20 year old legacy spaghetti code, the debugger has become one of my most treasured tools.
I also work with 20 year old spaghetti code, but my software is primarily middleware and debuggers aren’t allowed on the full system where I’d actually be able to reproduce the issue. Insane amounts of logging statements have become my most treasured tool.
Grep log will outlive us all
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.
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
I can record a video tomorrow if it helps?
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).
After decades of print debugging I finally got dap up and running in vim. It is very nice. Would recommend.