[openfuture]

Being young is hard, no need to judge to harshly, often a rivalrous blogpost-driven discussion can be turned into a cooperative exploration, which is exactly a way for them to gain the experience.

Quiet, or at-arms-length, dismissal hurts self-confidence and reinforces this blogpost-driven defense mechanism.

[_hardwaregeek]

It's definitely not the worst to be overly well read in programming literature. But oh man does it get old arguing with someone who is taking advice from a very niche, very particular field such as game development and applying it to general software development.

[finnthehuman]

>often a rivalrous blogpost-driven discussion can be turned into a cooperative exploration

They also often drive away any possibility of meaty conversation because everyone worth hearing from is drowning under a sea of underinformed responses written in a way that sounds like a convincing in-depth discussion to the even less informed passerbys.

I'm no sage, but it doesn't take a genius to see when Hacker News and /r/programming get swept away by a new silver bullet in software development. Then we all have to wait years before the enthusiastic youngsters are ready to hear a realistic conversation about the prima facie limitations of the new magic beans.