Why Hacker News matters for builders
Hacker News is where the tech industry discovers new ideas, debates technical decisions, and evaluates products. A front page post can generate 100K+ visitors, hundreds of qualified leads, and lasting credibility. YC founders, VCs, and technical decision-makers check HN daily.
Unlike other platforms where engagement is fleeting, HN discussions have lasting impact. Comments from years ago still influence technical decisions today. Building karma and reputation on HN establishes you as a thoughtful contributor in the tech community.
The challenge: HN's community is sophisticated and skeptical. They've seen every marketing tactic and can spot inauthenticity instantly. Success requires genuine expertise, intellectual honesty, and respect for the community's culture.
Understanding HN's unique culture
Hacker News has a distinct culture that values intellectual rigor, technical depth, and contrarian thinking. What works on other platforms often fails spectacularly on HN.
Core HN Values:
- Substance over style: Technical depth and original thinking matter more than polish or marketing.
- Intellectual honesty: Acknowledge limitations, admit mistakes, and present balanced perspectives.
- Contrarian thinking: Challenge conventional wisdom with data and logic, not hot takes.
- Anti-hype: Skepticism of trends, buzzwords, and marketing narratives. Show, don't tell.
Critical insight: HN rewards nuance and expertise. A comment that says "this is more complex than it appears" with technical details outperforms "great post!" by orders of magnitude. The community values people who add depth to discussions.
Commenting strategy: Building karma and credibility
Comments are the primary way to build karma and reputation on HN. Unlike submissions (which are risky and often fail), thoughtful comments consistently earn upvotes and establish credibility. Here are the four most effective commenting approaches:
Add Technical Depth
Share specific technical knowledge, implementation details, or edge cases that others might not consider. For example: "This approach works well until you hit 10M+ records, then you need to consider partitioning strategies and query optimization." The community values comments that demonstrate expertise and add substantive value beyond the original post. Avoid generic observations — focus on specifics that only someone with real experience would know.
Share Relevant Experience
Provide context from your actual work with specific details that prove authenticity. For example: "We tried this at [company] and ran into [specific problem]. Here's how we solved it..." Real-world experience is highly valued on HN because it provides practical insights that theoretical discussions miss. Include the challenges you faced, the trade-offs you considered, and what you learned from the experience.
Provide Balanced Critique
Point out limitations or trade-offs thoughtfully. Example: "This is clever, but there's a trade-off: [specific downside]. For use case X, consider [alternative]."
Why it works: Nuanced critique shows intellectual honesty and helps readers make informed decisions.
Ask Clarifying Questions
Ask thoughtful questions that advance the discussion. Example: "How does this handle [edge case]? I'm curious about [specific technical detail]."
Why it works: Good questions demonstrate engagement and often surface important details.
Submission strategy: Reaching the front page
Submitting content to HN is high-risk, high-reward. Most submissions get zero upvotes. But a front page post can drive 100K+ visitors and establish lasting credibility.
What Works on HN:
- Original research: Data analysis, benchmarks, or investigations no one else has done.
- Technical deep dives: Detailed explanations of how something works under the hood.
- Contrarian perspectives: Well-reasoned arguments against conventional wisdom.
- Show HN projects: Genuinely useful tools or interesting experiments (not MVPs or landing pages).
Title matters enormously. Use the exact article title or a clear, descriptive alternative. Avoid clickbait, questions, or marketing language. "How We Reduced Database Costs by 90%" beats "You Won't Believe This Database Trick."
Timing matters. Submit during US business hours (9am-2pm PT) when the community is most active. Weekend submissions get less traction. Monitor your post for the first 30 minutes — if it doesn't get early upvotes, it likely won't reach the front page.
Common mistakes that get you downvoted or banned
HN moderators actively enforce quality standards. Understanding what behaviors trigger downvotes or bans helps you contribute effectively while staying in good standing with the community.
Undisclosed Self-Promotion
Submitting your own content without disclosure is the fastest way to get banned. The solution is simple: always disclose affiliation. "I built this" or "I wrote this" is perfectly acceptable and respected by the community. What gets you banned is pretending to be a neutral third party when you have a vested interest. Transparency builds trust — deception destroys it.
Marketing Speak and Hype
Buzzwords, hype, and promotional language get downvoted instantly. The community can spot marketing copy from a mile away. Write like a technical person, not a marketer. Focus on substance and specifics, not superlatives and claims. Instead of "revolutionary AI-powered solution," say "uses GPT-4 to analyze code patterns and suggest refactorings." Show, don't tell.
Low-Effort Comments
Comments like "Great post!" or obvious observations add no value and get downvoted. Every comment should either add technical depth, share relevant experience, provide balanced critique, or ask thoughtful questions. If you can't add substantive value to the discussion, it's better not to comment at all. Quality over quantity is the rule on HN.
Flame Wars and Personal Attacks
Getting into heated arguments or attacking people will damage your reputation and potentially get you banned. Critique ideas, not people. You can disagree strongly while remaining civil and respectful. Focus on the technical merits of arguments, acknowledge valid points from the other side, and avoid inflammatory language. The goal is productive discussion, not winning arguments.
Ready to build credibility on Hacker News?
Teract helps you write thoughtful HN comments that add technical depth and demonstrate expertise.
Try Teract — it's free10 free credits · No credit card
How to contribute consistently without burning out
Writing thoughtful HN comments takes time. A substantive comment with technical depth requires 10-15 minutes of careful thought. Commenting on 5-10 threads daily means 1-2 hours of writing.
The solution: AI writing assistants that help you articulate technical knowledge faster. But generic tools like ChatGPT produce obvious AI-written content that HN's sophisticated community spots immediately. You need a tool that helps you express YOUR expertise in YOUR voice.
Teract understands HN's culture and helps you write comments that add technical depth without sounding like marketing. It references your real experiences and expertise, producing comments that sound like you wrote them. Reduce comment creation time from 15 minutes to 3 minutes while maintaining the substance HN demands.
Your 30-day Hacker News growth plan
Here's a practical 30-day plan to build credibility on Hacker News through commenting before attempting submissions:
Week 1: Understanding the Culture
Week 2: Building Karma Through Comments
Week 3: Strategic Submissions
Week 4: Balance & Reputation
Expected results after 30 days: 500+ karma, established reputation as a thoughtful contributor, and 1-2 successful submissions. The key is patience — HN rewards consistent, substantive contributions over time, not quick wins.
Example of a successful Show HN that reached the front page:
The difference between an audience and a community is which direction the chairs are pointing. Communities form when people feel their contributions matter.
Chris Brogan
Author & Speaker
