3 ms·
I do, mainly because of the cognitive overhead of setting up (and fixing when necessary) the extra tooling. Integrating my editor with whatever runs my code is
by brundolf 4y ago
I do, mainly because of the cognitive overhead of setting up (and fixing when necessary) the extra tooling. Integrating my editor with whatever runs my code is just rarely a zero-effort experience
The exception is with JavaScript in a browser, since the browser is both the native environment where the code is running, and can show the highlighted code and let me set breakpoints. However, even then, more and more of my JS code takes the form of expressions, not procedural statements, and breakpoints just don't help much with those. So in practice I still use them rarely
- syspec 4y ago> However, even then, more and more of my JS code takes the form of expressions, not procedural statements, and breakpoints just don't help much with those Would you mind expanding on that?
- brundolf 4y agoReact-style code ends up being more functional, with a lot of just nested expressions, and the concept of a "break point" barely even makes sense in those contexts. If you want to see intermediate values you'd have to first break them out into named constants, and even then there'd be little point to "stepping" (vs just printing) because they're going to be stateless I might use a stepping debugger on the odd procedural/stateful code, where there are actual variables that change over time, but that's less and less common for me these days