How to Participate in Hacker News Discussions

Hacker News has a distinct culture. The best contributions come from people who share what they genuinely know, have built, or have experienced — not from those trying to game the system. This guide covers how to participate in a way that the community values.

Understand the culture first

Before posting, spend time reading. Browse the front page, open comment threads, and pay attention to what gets upvoted and what doesn't. You will notice patterns:

• Specific knowledge beats general opinions. A comment like "I worked on this protocol at $company, and here's what we learned" gets far more traction than "I think this is good/bad."
• Directness is respected. HN values clear, no-nonsense writing. Skip the preamble and get to the point.
• Intellectual honesty matters. Saying "I don't know" or "I changed my mind" earns more respect than bluffing.

The community has a low tolerance for snark, self-promotion disguised as discussion, and generic comments that could apply to any topic.

Writing good comments

Share what you know from experience

The most valued comments on HN come from personal experience:

• "I built something similar and ran into X problem — here's how I solved it."
• "I've been using this tool in production for 2 years. The biggest gotcha is..."
• "We tried this approach at my company. It worked for X but failed for Y because..."

You don't need to be an authority. Honest, specific accounts of what you've seen or done are more useful than broad claims.

Be specific

Vague comments add noise. Instead of:

This is a bad idea.

Say:

This approach has a problem with tail latency because every request has to wait for the slowest shard. We hit this at scale and ended up switching to eventual consistency for this particular read path.

The second comment teaches something. The first one doesn't.

Disagree constructively

Disagreement is welcome on HN, but how you disagree matters:

• Respond to the argument, not the person. Address the idea directly.
• Explain your reasoning. "That won't work because..." followed by specifics.
• Acknowledge what the other person got right. "You're right about X, but I think Y is a concern because..."

Avoid dismissive one-liners. If you think someone is wrong, take the time to explain why — your explanation might help other readers too.

When you don't have expertise, ask questions

Not every comment needs to be an answer. Good questions are just as valuable:

• "How does this compare to X approach?"
• "What happens when you need to handle Y edge case?"
• "Has anyone measured the performance impact of this?"

Genuine curiosity contributes to the discussion just as much as expertise.

Sharing your own work

Show HN posts

"Show HN" is the standard way to share something you built. The community appreciates:

• A clear description of what it does — not marketing language, just what it is
• Why you built it — the problem you were solving, the gap you noticed
• What's interesting about the implementation — technical details that peers would appreciate
• Honesty about limitations — "It doesn't handle X yet" builds more trust than claiming it does everything

Responding to feedback on your Show HN

When people critique your work:

• Don't be defensive. Criticism on HN is usually genuine and technical.
• Engage with the specifics. If someone points out a flaw, acknowledge it and discuss how you might address it.
• Thank people for good feedback — even when it stings. The person who found a real bug did you a favor.

Sharing blog posts and articles

If you're submitting your own writing:

• Make sure the content is genuinely useful or interesting to a technical audience
• Use the actual title — don't write clickbait headlines
• Be present in the comments to answer questions and discuss

Things to avoid

• Astroturfing. Don't create accounts to upvote your own posts or ask friends to do it. The community and moderators notice, and it damages your credibility permanently.
• Self-promotion without substance. Dropping a link to your product without context or genuine reason to share it will be downvoted.
• Argument for the sake of argument. If you find yourself in a back-and-forth that's going nowhere, step back. Not every point needs to be countered.
• Generic comments. "Great article!", "This.", "+1" — these add nothing. Upvote instead.

Participating when English isn't your first language

Many Hacker News readers and contributors are non-native English speakers. If you're hesitant to participate because of language:

• Clarity matters more than perfect grammar. A comment with simple, clear English and good technical content will be well-received.
• Write your thoughts in your language first, then translate. This helps you organize your ideas before translating.
• Haiker can help. It translates stories and comments into your language, and when you write a reply in your language, it can translate your draft to English before you post — so you can participate in discussions naturally.

Download Haiker

Participate in Hacker News discussions in your language. Haiker auto-translates posts, comments, and your replies.

Download on the App Store | Get it on Google Play