Hacker News Strategy
Relevant source files
The following files were used as context for generating this wiki page:
Hacker News (HN) is recognized as a highly influential developer community within the project's marketing framework. The strategy focus is on authentic presence, technical depth, and avoiding marketing-centric behaviors that lead to content being flagged or penalized. Successful engagement requires understanding the unique culture of hackers, founders, and deep tech enthusiasts who frequent the platform.
Sources: skills/hacker-news-strategy/SKILL.md:1-12, skills/hacker-news-strategy/README.md:1-10
Community and Culture
HN users value technical transparency and novelty over corporate messaging. The audience is composed of several distinct segments, each with specific interests:
| Segment | Primary Interests |
|---|---|
| Founders | Fundraising, growth tactics, startup war stories |
| Senior Engineers | Deep technical content, architecture, systems |
| Tech Leads | Engineering management, scaling, processes |
| Indie Hackers | Solo projects, bootstrapping, revenue |
| Researchers | AI/ML, distributed systems, PLT, security |
Sources: skills/hacker-news-strategy/SKILL.md:15-28
Values and Anti-patterns
The platform operates on a strict set of cultural values. Content that demonstrates technical depth, genuine novelty, and "building in public" is generally well-received. Conversely, HN users and moderators actively penalize clickbait, corporate PR speak, and self-promotion disguised as content.
Sources: skills/hacker-news-strategy/SKILL.md:30-44
Submission Types
The strategy categorizes submissions into three primary types, each with specific requirements for success.
Show HN
Designed for creators to share things people can try. Requirements include a live demo or detailed walkthrough, and the creator must remain available for 2-3 hours to answer technical questions.
Sources: skills/hacker-news-strategy/SKILL.md:50-62
Launch HN
Reserved for major company launches or funding announcements. These must include deep technical details ("under the hood") and avoid PR speak.
Sources: skills/hacker-news-strategy/SKILL.md:68-75
Regular Submissions
Used for sharing technical blog posts, "war stories" with lessons, original research, or contrarian technical takes.
Sources: skills/hacker-news-strategy/SKILL.md:77-87
The HN Algorithm and Mechanics
The ranking of a post is determined by a combination of early upvotes, comment engagement, and automated penalties.
This diagram illustrates the factors influencing a submission's visibility and potential penalties.
Sources: skills/hacker-news-strategy/SKILL.md:118-138
Timing and Mechanics
Peak activity occurs between 10 AM and 12 PM PT. While weekends have lower traffic, they also offer less competition. Initial momentum is critical; a lack of early engagement often causes a post to "die" quickly.
Sources: skills/hacker-news-strategy/SKILL.md:112-125
Engagement Strategy
Authentic engagement is divided into the initial submission phase and long-term reputation building.
Comment Management
For a self-submission, the creator should immediately post a top-level comment providing backstory and technical context.
Hey HN, [your name] here, [role] at [company/project].
Quick backstory: [1-2 sentences on why you built this]
Technical context: [What's interesting under the hood]
Happy to answer any questions about [specific technical areas].
Sources: skills/hacker-news-strategy/SKILL.md:143-157
Reputation Building (The Long Game)
Reputation is built through a three-stage process to gain karma and community trust.
| Timeframe | Action |
|---|---|
| Month 1 | Comment only. Build karma through genuine engagement. No submissions. |
| Month 2-3 | Submit interesting third-party content. Show contribution to the ecosystem. |
| Month 3+ | Occasional submissions of own work mixed with other contributions. |
Sources: skills/hacker-news-strategy/SKILL.md:188-195
Content Optimization
Title Principles
Titles should be specific, concrete, and factual. Sensationalized titles are often edited by moderators to be neutral.
| Bad Title | Optimized Title |
|---|---|
| "The Best Way to Handle Errors in Node.js" | "Error handling patterns in Node.js production systems" |
| "We Made Deployments 10x Faster" | "How we reduced deployment time from 20min to 2min" |
| "Show HN: Our Amazing New Feature" | "Show HN: [Feature] – [What it does]" |
Sources: skills/hacker-news-strategy/SKILL.md:90-110
External Context Integration
Before launching on HN, the repository advises auditing the project's GitHub presence. HN users frequently check the README.md, license, and build status of a project on GitHub before deciding to upvote.
Sources: skills/github-presence/SKILL.md:5-15, skills/hacker-news-strategy/README.md:38-40
Monitoring and Tools
The strategy relies on specific tools for research and real-time monitoring:
- Octolens: Used to monitor HN for mentions of the product, competitors, and relevant keywords to participate in discussions authentically.
- HN Search (Algolia): Used to research past successful posts on similar topics.
- HN Front Page Check: Used to monitor rank and visibility during a launch.
Sources: skills/hacker-news-strategy/SKILL.md:238-245, skills/developer-audience-context/SKILL.md:162-165
Summary
The Hacker News Strategy emphasizes a technical-first approach, prioritizing transparency and community participation over traditional marketing. Success is contingent on providing high-value technical content, maintaining an active and respectful presence in comments, and strictly adhering to platform rules regarding voting and self-promotion. By following the "long game" of building karma, developers can establish the credibility necessary for successful project launches.
Sources: skills/hacker-news-strategy/SKILL.md:1-12, skills/hacker-news-strategy/README.md:1-15