>but debuggers/profilers are incredibly useful and important, and it’s essentially malpractice for a developer never to use them.
Just wait for the moment you need to write code for an embedded platform that doesn't have a debugging mechanism.
I've been programming for more than 30 years. Funnily, I used to use debuggers A LOT (in Borland Turbo C++ DOS "IDE" times, Visual Basic, Eclipse, Netbeans, Adobe Flash Builder, etc). But nowadays I seldomly use the debugger, if at all.
Haha I loved Netbeans, and in college(UK not US) got to the point when I taught actionscript instead of the teacher.
> Just wait for the moment you need to write code for an embedded platform that doesn't have a debugging mechanism.
Very close to 0% of programmers on this site are doing this. The vast majority are writing JavaScript/TypeScript, Python, or some other high-level language and targeting web platforms.
> But nowadays I seldomly use the debugger, if at all.
That might be fine for you and your use cases, but it's not fine for CRUD app developers who are essentially passing and mutating data around databases and state machines.
>That might be fine for you and your use cases, but it's not fine for CRUD app developers who are essentially passing and mutating data around databases and state machines.
I've done a mixed bag of these, but yep ultimately mainly just CRUD now days and yep that's all we're doing. It's what a lot of us are doing!