Launching to Hacker News, Dev.to, and GitHub
How technical communities actually evaluate a launch post, and the specific mistakes that get one buried.
Communities that punish marketing
Technical aggregators and developer communities are among the most valuable launch venues available and among the easiest to get wrong. The audience is large, technically sophisticated, and disproportionately likely to adopt and recommend new tools. It is also fluent in recognising promotional language and reflexively hostile to it.
The result is that the same product gets a completely different reception depending on framing, and the framing rules are unwritten but consistent.
Plain beats clever
A title that plainly describes what the thing is outperforms any clever or enthusiastic framing. Superlatives, growth language, and anything resembling a tagline mark the post as marketing, and marked posts are ignored or flagged before the content is considered.
This feels counterintuitive to founders trained to write compelling copy. In this context, the compelling thing is accuracy.
Link to something evaluable
A landing page with a signup form performs badly because it asks for commitment before evidence. A repository, a technical write-up, or a working demo performs well because it lets the reader form their own view, which is what this audience wants to do.
Being asked for an email before seeing anything reads as an attempt to capture rather than to share, and the audience responds accordingly.
The first hour decides
Ranked aggregators determine visibility within roughly an hour, which makes timing genuinely consequential and makes your availability during that window non-negotiable. A post that goes up when you are asleep is a post that was not really launched.
Prepare for the actual questions
Licensing, dependencies, performance, and comparison to the obvious alternative. These come every time. Precise answers — including honest ones about what you have not benchmarked — convert skeptical readers into users at a rate that surprises founders the first time.
Criticism handled well outperforms a good post
Some feedback will be blunt and a portion of it will be correct. Conceding a valid criticism directly earns more credibility than the original post did, and threads that begin hostile frequently turn favourable when the author engages honestly. Defensiveness reliably does the opposite.
Never solicit votes
Vote manipulation is detected on every major platform, and penalties commonly extend to banning the domain rather than the account. It is a permanent cost for a temporary and usually marginal gain.
The playbook
Write the title as a description, not a pitch
Technical communities reject promotional language reflexively. A plain, accurate title describing what the thing is outperforms any clever framing, and superlatives are the fastest way to have a post ignored or flagged.
Link to something substantive
A landing page with a signup form performs badly; a repository, a technical write-up, or a working demo performs well. The audience wants to evaluate the work, and being asked for an email before seeing anything reads as a bait.
Post when your audience is awake
Timing genuinely matters on ranked aggregators. Weekday mornings in the US typically produce the most engagement, and the first hour determines whether the post is seen at all — which makes availability during that hour non-negotiable.
Prepare for the specific questions
Technical audiences will ask about licensing, dependencies, performance, and how it compares to the obvious alternative. Have precise answers ready, including honest ones about what you have not tested.
Take criticism without defending
Some feedback will be blunt and some will be right. Acknowledging valid criticism directly earns more credibility than a good post does, while defensiveness is the most reliable way to turn a thread against you.
Never ask for votes
Vote manipulation is detected and penalised on every major technical platform, frequently by banning the domain rather than the account. Asking colleagues to upvote is among the most costly mistakes available in a technical launch.