> OP is smart to adjust to change
When did I tell OP not to change? My comment was about how my own workflow has changed radically in the last couple of years.
> the moment I stop using my IDE, you’d tell me don’t know what I am doing??
What? I didn't do anything of the sort.
> Dude, I probably was writing assembly code by hand when there were no IDEs and you were still trying to figure out the taste of Play-Doh
This is incredibly childish. If you really are as old as you imply, the cringe is all you, friend.
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.
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.
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!
I understand there are people who haven't used debuggers before and don't know what they're missing out on, but there's no excuse for that anymore because it's become much easier to set them up and use them.
Debugging and profiling has always been outside of the IDE for me, except when I started out as a Java Developer.
I don't and have never understood why someone spins up a full-weight IDE and then not used that same GUI to manage their debugger, since you get a lot of added benefits from that (being able to copy/paste from the editor to code evaluation/REPL for example).
I wasn't trying to criticize this early work at all. It looks like a fun and promising project!
Profiling is a tool meant for processes that relate to performance, or hot spots. Debuggers when integrated well[1], are great tools but compete with print based debugging which is a much more general skill one uses and needs to learn.
Let's reserve malpraxis considerations for writing code without any true thought given for security, privacy, accessibility and human rights affected.
[1] and I don't like the interface of any of the debuggers I used. Except maybe in ghci, if I had the patience to script a Tcl/Tk frontend one day.