I automate it, cause I hate typing too. E.g. double-clicking an identifier (or selecting an expression) and pressing F3 adds the log("<sel>:", <sel>) to the

I automate it, cause I hate typing too. E.g. double-clicking an identifier (or selecting an expression) and pressing F3 adds the log("<sel>:", <sel>) to the next line automatically. Later I format it as a more meaningful log level/message or <C-/> it out if it was a “silly” loglevel. The ability to program an editor changes how you look at things like that. F3 to list, F2 to saveall, and instantly I see the entire new path of execution, with all insights I’ve thought of at this point. It’s like an interactive debugger, but more interactive in some sense. (I’m also barely typing keywords, e.g. “eafu” means “export async function(|) {|}” and so on.) Well these are environments that don't allow nice code editing and debugging. Idk. While that is true for some envs, I’m able to choose at my job. And what I’m usually choosing isn’t an IDE (emphasis on D). Sometimes I have to work with IDE-oriented envs and sure, there I have to use it because console and dump tools suck, but to me it feels like walking through the mud.