3 ms·
I'm curious about this whole "have to be contrarian deal." Guy writes blog post which is good advice in 99% of the situations and someone just has to bring up t
by bjourne 14y ago
I'm curious about this whole "have to be contrarian deal." Guy writes blog post which is good advice in 99% of the situations and someone just has to bring up that, yeah, somewhere, sometimes more logging is not necessarily better. Why always nitpick on things?
In my work, if people wrote more and better log messages I would be delighted. They almost never do and instead rely on the Visual Studio debugger to inspect program state. It works great when debugging your own code, but is pretty useless when debugging someone elses code (you dont know where to place the breakpoints) or when analyzing a crash on a production site.
- jpd 14y agoI always figured that this was because a developer ran into a situation where the concept was naively applied and it ended up biting him. So, instead of staying quiet, he let people know the problems he ran into so that others don't get bitten as well and approach the problem more carefully.
- colomon 14y agoThe thing is, the article does not say "There are many circumstances where logging is a great tool." Who would object to that? However, what the article says is "One of the differences between a great programmer and a bad programmer is that a great programmer adds logging and tools that make it easy to debug the program when things fail." In other words, he's more or less explicitly saying people who do not use logging are bad programmers. So it's not at all surprising that there is vocal disagreement.
- d23 14y ago> I'm curious about this whole "have to be contrarian deal." Guy writes blog post which is good advice in 99% of the situations and someone just has to bring up that, yeah, somewhere, sometimes more logging is not necessarily better. Why always nitpick on things? It's just the nature of HN. I've given up on bitching about it.