3 ms·
That's why you use proper logging :/ If you're making something of a reasonable size, you should be logging tons of stuff. If you've made sure your logging is
by axod 16y ago
That's why you use proper logging :/
If you're making something of a reasonable size, you should be logging tons of stuff.
If you've made sure your logging is solid, often fixing a bug is just a case of looking in the log to see what went wrong.
- jeg 16y agoI agree that proper logging can replace the need for a debugger in many instances, but so can proper testing, talented devs, unlimited time, unlimited budget, etc. Under ideal circumstances (i.e. not real world), no one would ever need to fire up a debugger, but (most of us) don't work in those conditions. Can you create world-class software using only print statements to debug? Sure. Is that an efficient use of your time? Probably not. The bottom line is debuggers are just another tool in the development aresenal, and dismissing them merely because you can accomplish the same task in another way is asinine.
- axod 16y agoI don't dismiss them because of that, I dismiss them because I can do the same job quicker by thinking, knowing the code, being able to read and understand any code I didn't write, and inserting a couple of print statements.