4 ms·
I've seen this a lot with our junior developers who are just out of college. My take on it is that the oversharing generation is encouraged to "put something ou
by bb101 11y ago
I've seen this a lot with our junior developers who are just out of college. My take on it is that the oversharing generation is encouraged to "put something out there" and make it sound authoritative. Then it is discussed and either supported or shouted down.
Unfortunately the blog posts stick around for a lot longer than they ought to, making it very hard for Googling newbies to decide whether they can trust the advice or not.
Reminds me of the old adage "the more you know, the less you know". Works in reverse!
- nothrabannosir 11y agoDave Cheney is not exactly a junior developer. He's a prominent member in the Go community, often considered a member of the core Go team. I disagree with his post, too, but to brush it off as (or even relate it to) inexperience and junior devs is slightly out of place.
- SeriousM 11y agoTo be honest, I judge someone on the things he/she does (write), not on the position he/she holds. The blog post sounded like it's written by an unexperienced guy, someone that lives in a perfect bugfree world or who didn't dealt with long running projects yet.
- mikekchar 11y agoNot to mention that I have seen death matches on this topic in most companies I've worked in. It is not a topic where everybody agrees ;-) It is a situational thing. To rebound the inappropriate junior dev comment, I have found that more senior developers can often get away with a lot less logging because the behaviour of the application is more apparent from the outside. I think your logging system has to be flexible enough to handle both philosophies because expecting someone to be able to write systems with minimal logging when they don't know how to do it is unreasonable.