Build in Public Communities
How to choose a relevant room, learn its norms, and participate without treating people as distribution inventory.
Choose by relevance, not size
The best community is not necessarily the largest. It is the place where people understand the problem, can evaluate the artifact, and are willing to exchange context.
Useful starting places include:
- Indie Hackers for independent products and business journeys;
- Product Hunt for discovering and launching technology products;
- Hacker News and Show HN for technically interesting work with a functioning artifact;
- DEV Community for developer-focused explanations and learning notes;
- focused subreddits, forums, Slack groups, Discord servers, and local meetups related to the actual problem;
- GitHub Issues and Discussions when the conversation belongs beside a technical project.
Read before posting
Observe what the community considers useful. Read its rules, recent conversations, accepted formats, and moderation expectations. A post that works on your profile may feel like spam in a focused forum.
Participate before asking
Answer questions, share evidence, correct mistakes, and help another person without attaching your link every time. Contribution creates context for later work.
When you do share a project:
- explain why it belongs in that room;
- disclose your relationship to it;
- include enough detail for discussion without requiring a click;
- ask a question the community is qualified to answer;
- remain available after posting.
One healthy rule
Do not enter ten communities to broadcast one announcement. Choose one or two relevant places and become a recognizable, useful participant.