This topic is genuinely contested — read the individual model responses for different perspectives.
Models agree on
- ✓Avoid generic questions; be specific
- ✓Provide context and background
- ✓Demonstrate prior effort or research
- ✓Craft a clear and specific title
- ✓Engage thoughtfully with commenters
- ✓Avoid low-effort topics like trivia or idea validation without details
- ✓Post during peak HN traffic hours: 10:00 AM – 2:00 PM PST
How to Ask Questions in Ask HN Effectively
Hacker News (HN) is a community of developers, founders, investors, and researchers who value specificity, effort, and intellectual rigor. To ask questions effectively, focus on crafting well-structured, specific, and context-rich posts that demonstrate your prior effort and respect the community's time.
Key Principles
- ·
Be Specific and Provide Context
- ·Avoid vague or generic questions like "What database should I use?" Instead, frame your question around a specific problem with clear constraints: "I'm building a read-heavy analytics dashboard expecting 10k writes/sec. Given a small team and AWS hosting, which database—ClickHouse or TimescaleDB—has lower operational overhead in production?"
- ·Include background information: your role (e.g., solo founder, senior dev), specific hurdles, and constraints (budget, tech stack, team size).
- ·
Demonstrate Effort
- ·Show that you've done your homework by detailing what you've already tried or researched: "I've looked at ClickHouse and TimescaleDB but need insights on scaling." This "proof of work" principle is critical to avoid being perceived as lazy.
- ·
Craft a Clear and Specific Title
- ·Use titles that summarize your question precisely: "Strategies for reducing S3 egress costs for a high-traffic media site" is better than "Need help with AWS."
- ·Avoid clickbait or excessive punctuation.
- ·
Structure Your Post for Scannability
- ·Use bullet points, code blocks, and concise paragraphs to make your post easy to scan.
- ·Remove fluff and get straight to the technical problem.
- ·
Engage Thoughtfully
- ·Respond to comments with clarifying questions or acknowledgments, not just "Thanks!"
- ·Update your post with solutions or insights gained from the discussion to add value for future readers.
Topics That Work Well
Ask HN thrives on questions that rely on collective wisdom rather than factual lookup:
- ·Career progression and salary negotiation
- ·Tech stack architecture decisions
- ·Industry trends and layoffs
- ·Productivity and workflow optimization
Avoid low-effort topics like trivia, personal idea validation, or specific code debugging (use Stack Overflow for the latter).
Timing and Etiquette
- ·Post during peak HN traffic hours: 10:00 AM – 2:00 PM PST on weekdays.
- ·Avoid spamming the forum; prioritize quality over quantity.
Common Pitfalls
- ·The "Lazy Poll": Vague survey-style questions like "What is your favorite programming language?" are often closed by moderators.
- ·Idea Validation Without Details: Avoid asking "Would you use this?" without providing a prototype or detailed context.
- ·Self-Promotion: Disguising product promotion as a question is heavily penalized.
Summary Checklist
Before posting, ensure:
- · Title is descriptive and specific.
- · Context and background are provided.
- · Prior effort or research is demonstrated.
- · Question is experiential, not purely factual.
- · Ready to engage in the comments.
By treating the community's time as a scarce resource and demonstrating effort, you can elicit high-quality, actionable responses from Ask HN.
Follow-ups
You just saw open-source models answer
Want GPT-5, Claude, Gemini & more on the same question?
Sign in free to run any question against frontier models — side by side, same synthesis, honest comparison.