4 ms·
I'll probably get a ton of pushback on this, but I never found huge value in debugging compared to using a strict type system and writing easily testable code.
by loveparade 4y ago
I'll probably get a ton of pushback on this, but I never found huge value in debugging compared to using a strict type system and writing easily testable code. I haven't debugged, as in used an interactive debugger like gdb, in many many years, not counting occasions where I needed to reverse-engineer some C code.
I would prefer languages where the need for interactive debugging is minimized through the type system, good abstractions, and good testing frameworks. Functional languages (ideally strongly typed), or something like Rust, tend to fall into this category. And even for less strict languages, I find debugging to be significantly slower than spending upfront time writing testable abstractions, which usually means functional code that operates on immutable data structures when possible.
Debuggability is nice... but isn't not having to debug even better?
- 32gbsd 4y agoHow do you know that what you wrote works?
- tcbasche 4y agotests Do you really step through the debugger to see if something works?
- 32gbsd 4y agoSo you debug it then you write the tests? Or you write the tests first then you debug? Because you gotta debug it at some point.
- Decabytes 4y agoWhen a test fails it can be difficult to pinpoint where in the pipeline it's failing. Using a debugger and setting break points is really helpful to help find the location where things are going wrong.