Community as infrastructure
A serious technical community is not an audience or a marketing channel — it is the trust layer, the research surface, and the market map for the work that flows through it.
The “community” word does a lot of work, most of it lazy. Marketing teams use it to mean an audience. Growth teams use it to mean a funnel. Product teams use it to mean the people on Discord who file bugs for free.
The communities that actually matter to the people inside them are doing something else. They are functioning as infrastructure: a place where reputation accumulates slowly, where introductions cost less than they should, where it is possible to learn the shape of a market by listening rather than by paying a research firm to summarize it.
This has consequences:
- Treating the community as a channel will destroy it. The instinct to extract attention, however gently, breaks the conditions that made the community valuable in the first place.
- The right metric is not engagement. It is whether members can do things faster and with more trust than they could without the community.
- Infrastructure is boring on purpose. The communities that compound do not optimize for the post that goes viral; they optimize for the question that gets answered correctly three years from now.
The interesting design question is what a community looks like when it is deliberately built as infrastructure from day one, rather than discovered to be infrastructure after the fact.