4 ms·
Well, shit happens, and you may need to receive inputs that are out of your control, or use libraries that are less then perfect and you need to use intermediat
by klez 7y ago
Well, shit happens, and you may need to receive inputs that are out of your control, or use libraries that are less then perfect and you need to use intermediate results. In those cases a debugger (or even just strategic prints) can be a godsend.
- JustSomeNobody 7y agoI can use other tools. A good logging framework or wireshark, etc to capture and view data. I won’t use a third party library that is shit.
- klez 7y agoWhat if you inherited someone else's code? Are you going to change all the libraries because you don't like them? Or even if they use good libraries, how are you going to unravel complex pieces of code? What I'm trying to say is, sometimes you need all the help you can get. And even an awful debugger is better than doing it in your head.
- JustSomeNobody 7y agoI fix other devs code with a debugger. I don’t “code with a debugger” myself. I think it is wrong and lazy to do so. For third party libs I work with the vendor to unshit their shit. Or I switch, yes. I write code that has to run out in BFE for 5-10 years. I can’t be sloppy about it.