“I just chose words carefully”

Let's be real: most open source contributors think their job ends at the commit message. But this piece, which clearly struck a nerve with the HN crowd, makes the case that the real engineering happens in the words you choose before and after the code hits the repo. The title — "I just chose words carefully" — is deceptively simple. That's the point. The best communication in this ecosystem looks effortless precisely because someone sweated over every syllable. The open source world is littered with graveyards of projects that died not from bad code, but from bad communication. A maintainer snaps at a newbie contributor, a licensing debate turns personal, a core team member gets publicly humiliated in a GitHub issue. None of that is a technical failure. It's a failure of word choice. This article's author clearly learned that lesson the hard way — and the HN discussion around it (193 comments and counting) suggests plenty of others have too. What's interesting here is how this connects to the broader power dynamics in open source. The people who control the words often control the project. Linus Torvalds' infamous rants were tolerated because his code was brilliant, but they still reshaped the Linux community's culture for decades. More recently, we've seen entire forks happen because a maintainer couldn't find the right words to say "no" to a controversial feature. The technical fork is easy; the linguistic fork is the hard part. The source URL — https://unsung.aresluna.org/i-just-chose-words-carefully/ — deserves a read in full, because the HN comment section alone can't capture the nuance. My takeaway: if you're a maintainer, spend as much time on your RFCs, your deprecation notices, and your "thanks but no thanks" replies as you do on your code review. Your words are the user interface for your project's humanity. Get them right, or watch your community fork itself into oblivion.