4 ms·
They're busy building stuff without blogging about it. It's tough to assess a change in culture when your heuristics are limited by selection bias favoring loud
by TechBro8615 3y ago
They're busy building stuff without blogging about it. It's tough to assess a change in culture when your heuristics are limited by selection bias favoring loud contributors over productive builders. That's not to say there aren't great hackers who blog; but there are certainly bloggers who are bad hackers, and by definition they're more immediately visible than great hackers who don't blog.
I'm sure there is a term for this phenomenon, but usually you see it within corporate bureaucracies - the skills that take you to the top are not necessarily the skills that make you good at your job. You get promoted by getting noticed. And creating value is one way of getting noticed. But you don't need to get noticed to create value. Same goes for any builder culture.
So take the opinions of the bloggers with a grain of salt. Eschew the RSS feed for the GitHub commit log. Read the source code, not the blogs. There you'll see that hacker culture is alive and well. Indeed, it's thriving.
- monksy 3y agoI completely disagree with your claims here. Communicating about your work, your discoveries, your work is one of the aspects of being an engineer. Developing and maintaining a blog takes work. Grinding out code alone is not productive, nor is it a long term successful way of achieving anything in this industry. My take of this situation is that people are overworked, and community has become overly regulated, unrewarded, and suppressed. (Language/tone policing, spam, aggressive individuals encouraged in groups, bad group membership policies [CoCs used as bullying devices more than simple rules to follow], dev advocates stepping on everything)