To become a better writer, read as much as you can

The open source world has a writing problem. It's not the code — the code is usually fine. It's the READMEs that read like legal disclaimers, the commit messages that say "fix stuff," and the documentation that assumes you already know the entire architecture. This article's advice — read more to write better — is the exact medicine for that disease. Every maintainer who's ever complained about their project's adoption should look in the mirror and ask: when's the last time I read someone else's docs to see what good looks like? There's a deeper truth here that connects directly to the open source ethos: the best writers in this space are also the most voracious consumers. Think about the maintainers whose projects you use — they're the ones who've read every blog post, every source file, every issue thread that came before them. They've internalized the patterns of good technical communication the way a musician internalizes scales. The source article at https://nappertime.com/the-golden-rule-of-becoming-a-better-writer/ nails this: reading isn't passive consumption, it's active study. The Hacker News thread adds a dimension worth noting — some commenters will push back, saying "I write to think, not think to write," and that's fair. But the core point survives the criticism: if you want to write good docs, you need to have read bad docs and wished they were better. That's where the empathy comes from. It's the difference between writing for an audience and writing at an audience. This advice scales beyond prose. Read other people's code the way you'd read a novel — for the style, the decisions, the choices that went into it. That's how you develop a writer's voice in code. The article might be aimed at general writing, but for the open source crowd, it's a double-edged sword: read more, write more, and your contributions will finally say something worth reading.