You’ve just spent hours crafting a beautiful TUI for Hacker News. Your code is solid. Your features are innovative. Then you post it, and the first comment is: ‘When I saw you couldn’t even make the effort to tell your AI to at least make the README pretend to be written for humans, I immediately knew this was slop.’ Ouch. That comment isn’t about your code. It’s about your signal.
Your code can be perfect, but if your README smells like AI, you’ve already lost the community. The commenter is entirely right. And it reveals a truth most developers refuse to accept: in open source, authenticity is a form of social capital – and AI-generated content is its biggest enemy.
You’ve probably felt that twinge of frustration when you see a project with a slick, generic README. You know, the one that starts with ‘This is a modern, high-performance TUI for Hacker News’ and then lists features in bullet points that sound like a press release. Something feels off. You can’t put your finger on it, but you trust the project less. That’s not your imagination – it’s your brain detecting a lack of human effort.
The irony? Most developers think the criticism is about the quality of the code. It’s not. It’s about the community’s need to see that you care about the same things they do: craftsmanship, curation, and the willingness to do the boring work. The README is the handshake. If it’s cold and robotic, why would anyone trust you?
Take the Hacker News TUI project by alin9661. The code might be brilliant. But the first reaction from the community wasn’t ‘Wow, cool features’ – it was ‘This is slop.’ Because the README was clearly AI-generated, and in a community that prizes human curation, that’s a death sentence.
The moment you outsource your README to an AI, you’re telling the community: ‘I don’t care enough to speak to you directly.’ And that’s the real problem. Not the code quality. Not the features. The signal.
So what do you do? Write your README yourself. Even if it’s messy. Even if it’s imperfect. Because the community doesn’t want polished text – they want proof that a human being cared enough to write it. That’s the difference between a project that gets ignored and one that gets shared.
Your next open source project’s success depends not on the code you write, but on the story you tell. And the story starts with a README written by a human – warts and all.
FAQ
Q: Isn't an AI-generated README just a time-saver? Why does it matter if the content is accurate?
A: Accuracy isn't the issue – it's trust. The community wants to see human effort as a signal of investment. A README is a handshake, not a press release. An AI-generated one feels like a bot reaching out, not a person.
Q: So should I never use AI to help with documentation?
A: Use AI as a drafting tool, but always rewrite and personalize. The final version must sound like you – not like a robot. The community can tell the difference, and they'll judge you for it.
Q: But what if my code is so good that the README doesn't matter?
A: That's a fantasy. First impressions dominate. If your README repels the community, no one will ever get to your code. The README is the gatekeeper. Even brilliant code can't save a bad first impression.