- Logging Do's and Dont's
- The Dark Art of Logging
- Everything you ever needed to know about logging (okay, this one was a comment on the other two being published, but it's funny)
The advice is funny in a "holy crap do people need this, you made me cry" kind of way. Really?
People need to be told to log exception stack traces?
People need to be told to parameterize logging statements? Although this one is funny, because it uses SLF4J, and SLF4J's logging formats are hilarious in a post-1.4 world. Come on.
log.info("You passed me [%s] as an argument.", argumentValue);
Trace logging with aspects is kinda funny too - for one thing, it's actually decent advice, but for another, you're TRACING. Dude. Even the log statement submission should be in an executor.
The Dark Art of Logging is funny too - it's like they're instructing people to log stuff, you know? It's stuff that once you use it at all, you look at your navel and think "Gee I really should give myself enough information to reconstruct the call." Hmm, maybe people do need these silly posts.
This is why stuff like Dynatrace exists, because people don't even think to log enough to help themselves I guess. It's a good business if you can get it.
William Louth is right, though - this stuff is modern caveman. This is why our field is so immature - people don't know how to do the basics, we tell ourselves how to do the basics all the time, and we never ever really seem to get it.
If you were creating a baseline of information that a competent programmer would have to know, what would be in that baseline? SQL, Logging, C, Java, OCaml?