I have been building things for as long as I can remember. I grew up in Delhi taking things apart to see how they worked, then putting new things together out of whatever I could find — a ten-power telescope, a telegraph transmitter, a barometer — assembled mostly from parts scavenged out of the scrap market and Chor Bazaar on ten rupees a day of pocket money. The same itch led me, years later, to bootstrap a small developer tool, grow it to customers in forty-nine countries, and sell it; it has me building products for clients today, government projects among them. I mention this only to establish that I am, by temperament, a person who likes concrete problems — the kind with answers you can measure. You can tell whether the build shipped, whether the bug is fixed, whether the tool found its customer.
So an essay about something as soft, as resistant to measurement, as community is out of character for me, and I want to be honest about that at the outset. I am suspicious of essays like this one; the genre runs toward the sentimental, and sentiment is usually where rigor goes to die. But I have now spent sixteen months building a community called Barakah HQ, and the experience has convinced me of something I would have dismissed as soft a few years ago: that the social environment a person is embedded in is among the most powerful forces determining what they become — frequently more decisive than raw talent, and, I suspect, sometimes more decisive than circumstance. It has also convinced me that we systematically underinvest in that environment precisely because it resists measurement. You cannot put a community on a balance sheet. You cannot A/B test a friendship. And so we file it under nice-to-have — a garnish on the real work — when in fact it is frequently the substrate the real work grows out of.
In this essay I try to make that claim precise rather than inspirational. I start with a framework — an analogy from chemistry, and two terms the whole argument reduces to. I then describe the problem the community was built to solve, the four mechanisms by which I think a community acts on a person, and the design choices we made to amplify some of those mechanisms and not others. Finally, I look at the evidence, including the strongest objection to it, and end with what the name means and where the whole thing can go wrong. I should say plainly, in the spirit of not overselling: everything here could be wrong. I have run no controlled experiment, and I am close to the last person who should be trusted to evaluate his own community dispassionately. What I have tried to do is ground the argument in mechanisms rather than moods, and to be honest about the places where the mechanisms give out.
Rooms, seeds, and supersaturation
Here is something about talented people that took me too long to understand, and that I am still not sure I understand correctly. A person can be completely ready — full of skill, full of drive, holding far more than anything they have shipped would suggest — and still produce nothing for years. Then the change, when it finally comes, can be sudden and nearly total. We treat being ready and breaking through as a single event. They are not even close to the same event, and the gap between them is what this essay is about.
The clearest way I have found to describe the gap comes from chemistry. Dissolve enough sugar into hot water and cool it gently, and the water will hold far more than it has any right to carry — supersaturated, past saturated, yet still and clear and apparently doing nothing. It can wait that way more or less indefinitely. What it is waiting for is a seed: a single crystal, a fleck of dust, a scratch on the glass. The moment one arrives, the whole solution locks into structure faster than the eye can follow. Nothing was added. Everything needed was already dissolved in there. What was missing was a nucleus — and the nucleus, almost always, arrives from outside.1
The analogy gives me the two terms I will use for the rest of the essay. The room is the set of people you are surrounded by. The seed is the thing one of them does — ships, says, survives — that causes the person watching to crystallize. Nearly everything below reduces to a claim about those two words: that talent is far more abundant than it looks, that most of it is sitting quietly in solution, and that the scarce input is usually not more talent. It is a room in which the right seeds fall.
1. The problem of the isolated builder
Start with the observation that motivated the entire project. There is an enormous amount of latent talent that never compounds, for no reason more exotic than that it sits alone. A capable engineer in a tier-two city; a designer with real taste and no peers who can see it; a founder with a working product and no one to tell them whether the next move is brave or foolish — these people are not short on ability. They are short on a room.
Isolation has a specific failure mode, and it is worth naming precisely, because the imprecise version — “they lack support” — misses what is actually going wrong. It is not that the isolated person does nothing. It is that they calibrate to the wrong reference points, or to none at all. They aim at the ceiling they can see, and the ceiling they can see is low, because no one around them has gone higher. Such a person is a supersaturated solution that has simply never been seeded — holding everything required and, for want of a single nearby crystal, staying clear and still. Ambition, I have come to think, is not purely an internal trait. It is partly a social inheritance:2 you absorb the size of the goals that the people near you treat as normal. Put a talented person in a room where everyone has only ever taken a salaried job, and a salaried job becomes the summit of the imaginable. Put the same person in a room where three peers have quietly launched products and found their first paying customers, and something shifts. Building stops being mythical. It becomes a thing that people like you simply do.
I know this failure mode from the inside, because I lived in it for years. Most of what I built as a kid, I built alone — there was no one nearby for whom homemade telescopes were ordinary, and later, no room of people for whom a bootstrapped product was simply a thing one did. I got further than I had much right to, but I got there the slow, lonely way, calibrating against a ceiling I had to imagine rather than see. Barakah HQ is, in no small part, the room I wish I’d had.
That, in a sentence, is the thesis. We did not set out to give anyone new abilities. We set out to change the room.
2. What a community actually does to a person
The question worth asking about community is not whether it matters — “community is powerful” is both true and useless — but by what mechanism. From what I have watched, there are four. I will not pretend the list is exhaustive; I’d guess there are others I have not isolated. But these four are concrete enough to reason about, and, more importantly, concrete enough to design for.
The reference class. The first mechanism, and I think the most important, is the one already implicit above: a community resets your sense of what is normal. Members will sometimes share a milestone with an apology built into it — this may look small from the outside. A first ten thousand rupees from a product. A first thousand pre-orders. A first remote role. Each time, the person qualifies the win, as if to lower expectations in advance. And each time, I think they have it exactly backwards. These milestones are not small. They are the precise moments at which an abstraction — an idea can become a product; a product can create value for a stranger — turns into a lived fact, both for the person who lived it and, just as much, for everyone watching them live it. A community is a machine for converting other people’s milestones into your own enlarged sense of the possible.3 A milestone shared in the group is a seed crystal dropped into the solution. And crystallization, once it begins, tends to spread.
This first mechanism is not unique to communities; it is how places have always worked on people. Paul Graham observed that great cities whisper an ambition to everyone living in them — Cambridge tells you to be smarter, New York to be richer, Silicon Valley to be more powerful — and that even the strong-willed absorb the message of wherever they happen to stand.4 A community is the same instrument at a smaller scale, with one enormous difference: nobody gets to compose a city’s message, but a room’s message can be chosen, and guarded, on purpose. The design choices in the next section are mostly that — the composing and the guarding.
Trust as infrastructure. The second mechanism is less romantic and more economic. High-trust environments lower the cost of every useful transaction. A referral, a warm introduction, feedback that does not flatter you, a quiet warning about a client who does not pay — these flow freely only where people are known and accountable to one another. In a crowd of anonymous usernames, generosity is close to irrational; you give, and the giving disappears into the void. Among people whose names, faces, and reputations are on the line, generosity becomes the sensible default, because it is remembered and, over a long enough horizon, returned.5 This is why our curation is strict — full names, verifiable profiles, real offline presence — not out of snobbery, but because trust is the actual product, and trust does not survive anonymity.
Identity, and what you become. The third mechanism is the slowest and, I suspect, the deepest. We become, over time, something like a weighted average of the people we spend our hours with. Not metaphorically — actually. You absorb their habits, their standards, their tells. One member wrote that the community was how he found remote work, and that he now prays on time and keeps his other obligations even while he works. I keep returning to that line, because it captures something the productivity literature usually steps around: a community does not only change what you produce. It changes who you are while you produce it. The standards you are surrounded by quietly become the standards you hold yourself to — in the work, and in everything adjacent to the work.
The opportunity surface. The fourth mechanism is the most measurable, which is probably why it is the one people reach for first. Most real opportunities arrive through people rather than through application forms; this is the old finding about the strength of weak ties, and it has not stopped being true.6 A community is, mechanically, a larger and warmer surface for opportunity to land on. Jobs, freelance projects, co-founders, first customers, the person who happens to know the one thing you needed to know — these do not appear because you optimized your résumé. They appear because you were present, known, and useful in a room full of people doing adjacent work. Widen the room and you widen the surface. That part really is almost arithmetic.
3. The design choices, and why they are choices
If those are the mechanisms, then designing a community is mostly the question of which mechanisms you amplify and which you allow to decay. And most online communities do decay, in depressingly predictable ways: they grow too fast, dilute their signal, fill with people who consume but never contribute, and chase the visible high of virality over the invisible compounding of consistency. We made a small number of deliberate bets against each of those failure modes. I want to present them as choices, not as obvious best practices, because each one cost us something real, and a reader running a community of their own should be able to see the price.
Quality over quantity. We grow by application and referral, slowly and on purpose. Roughly four hundred members across eight focused groups is not a figure we are trying to multiply by ten this year.7 Smallness here is not a limitation we are tolerating until we can scale it away; it is a feature we are actively protecting. A room loses its character the moment it admits people who do not add to it — and that loss is close to irreversible. You cannot un-dilute a culture.
Enforcement, quietly. Curation controls who enters; it says nothing about what happens when someone already inside breaks the trust the room runs on — and someone eventually does, in any room, however carefully gated. We handle it in escalating steps: the offending messages are deleted first, correction without ceremony, because most breaches are lapses rather than character; repeated violations end in removal. Removal is rare, and it should be. But a community that cannot bring itself to remove anyone is, in the end, governed by its least trustworthy member. The gate gets all the attention. The exit does more of the work than anyone admits.
Contribution over consumption. A lurker shapes no one and is shaped by no one. The entire machinery I described above runs on people putting things in — questions, answers, work, feedback, presence. So we try, in a hundred small ways, to make contribution the norm and pure consumption feel slightly out of place. This is not a moral stance about freeloading. It is a structural one: a community of spectators is not a community, it is an audience, and audiences do not seed each other.
Structure for signal. We split conversation into domains — product, design, code, marketing, AI, hiring, the casual channel, even fitness — so that relevance stays high and the cost of paying attention stays low. The enemy of a community is not silence. It is noise: the slow erosion of the sense that what gets posted here is worth reading. Structure is how you fight it, and the fight is never finished.
Consistency over hype. Nothing here is engineered to go viral. The work is regular meetups, month after month, across Delhi NCR, Hyderabad, and Bengaluru; steady engagement; relationships that are years deep rather than a weekend long. Compounding is unglamorous by nature — it looks like very little is happening, right up until the moment a great deal has happened. To be clear, this is the part most people are temperamentally unwilling to do, which is exactly why it works.
Paid for by its own people. There are no sponsors to please and no revenue line to optimize. When a meetup needs money, the community raises it from itself — the last Bengaluru meetup ran on some thirty thousand rupees put together by members. I want to keep it that way for a structural reason, not a romantic one: trust is the product, and the surest way to corrupt a trust product is to make the members the inventory — to sell access to the room to someone outside it. A room paid for by its own people answers to its own people. The rupees are small. What they buy — incentives that point in the same direction as the purpose — is not.
Real-world presence. And underneath all of it: people meet in person. You cannot be meaningfully shaped by a username. You can be shaped by someone you have shared a meal and a problem with, who remembers your name and asks, months later, how the thing you were stuck on turned out. The meetups are not a marketing activity dressed up as community. They are the part where the abstraction of network becomes the reality of people I know. And because the isolated builder of Section 1 mostly does not live in a metro, the meetups are now spreading to where he does — beyond Delhi NCR, Hyderabad, and Bengaluru, into the tier-two and tier-three cities, one at a time. A room within reach of a train ticket is a different promise than a room within reach of a flight.
4. The evidence, such as it is
I am wary of overclaiming, so let me be careful about what I actually know, and careful first about what I do not. In sixteen months a particular pattern has repeated often enough that I no longer think it is luck — but I cannot prove that any single outcome would not have happened anyway, and I should meet the strongest version of that objection before I lean on the pattern at all.
The best possible counterargument to everything above — and I want to state it as strongly as I can, because as far as it goes it is correct — is that I have the causation backwards. A curated, high-trust, application-only community does not produce capable, driven people. It selects them. The people who apply, who pass the curation, who stay engaged for years, are precisely the people who were going to ship the product and find the remote role regardless. On this reading the community is not a cause at all; it is a filter, and I am admiring the filter for the quality of what it let through.8 I find this argument genuinely hard to dismiss, and I think anyone who runs a community and has not felt its force is not being honest with themselves.
Here is the most I can honestly say against it. Selection and treatment are not mutually exclusive; a thing can sort for talent and also act on the talent it sorts for. The pattern I keep seeing is not that capable people join and then succeed — that would indeed be consistent with pure selection — but that capable people join, sit clear and still for a while exactly as before, and then crystallize shortly after a specific seed: a particular milestone posted by a particular peer, a particular introduction, a particular evening at a meetup. The timing is the tell. If it were pure selection, the breakthroughs should be scattered at random across people’s tenure. Instead they cluster suspiciously close to identifiable seeds. I cannot prove this rises to causation. But it is the kind of pattern that, after sixteen months, I no longer think is luck.
As for the outcomes themselves: members have shipped products and found their first revenue. Others have crossed real sales thresholds on features they were not sure anyone wanted. People have moved into remote roles they would never have heard about otherwise, and freelancers have picked up project work through nothing more exotic than being known in a room of people who needed it. Founders in the group are building across an unreasonable range of domains — fintech and faith-tech, space and agriculture, developer tools and education — and a handful have gone all the way to an acquisition.9 None of this is a unicorn. All of it is the ordinary, compounding output of capable people who stopped working alone.
The most telling evidence, though, is not in any metric, and I am aware that saying so is convenient for a man without a control group. It is in the language people use when they describe what happened to them. Almost without exception, the word that recurs is gratitude — to one another, and, in our community, to God. People do not say I optimized my network. They say something closer to doors opened that I did not open myself. I think that is worth taking seriously rather than rounding off as a figure of speech, even granting that it is exactly what you would expect people to say either way.
5. On the name
The community is called Barakah HQ, and the name is not decoration. Barakah is the idea of blessing — of a quality of growth and benefit in a thing that exceeds what its visible inputs should produce. A small amount of time, of money, of effort, that somehow yields far more than its size predicts: the solution holding more than the water had any right to carry. It is, almost by definition, the part of an outcome you cannot fully account for on the spreadsheet.
I named the community after that idea because it names the thing I keep observing and cannot otherwise explain. When people gather in good faith, hold themselves to a standard, help one another without keeping a ledger, and stay consistent over a long time, the results compound past what the inputs justify. Whether you read that as the natural arithmetic of trust and weak ties, or as something placed in the gathering from above, the empirical shape is the same10 — and for the people in our community, those two readings are not in tension. The work and the faith are not separate tracks. The same person is trying to ship a good product and to keep their prayers, and the community is the place where both ambitions are taken seriously at once. I have come to think this is not a constraint on the building. It is part of why the building holds.
6. The mechanisms run in reverse
I said at the start that I would be honest about where the mechanisms give out, and the most important place is this: the same forces I have spent the essay praising run, without any change of mechanism, in reverse. A community shapes the people in it — and it can shape them badly. The reference class that lifts ambition can also enforce a stifling conformity. The trust that enables generosity can curdle into a closed circle that keeps good outsiders out. The standards that pull people up can harden into a status game that wears them down. Every mechanism I described as a means of growth is, pointed the wrong way, a means of harm. The seed is indifferent to what it propagates. Drop the wrong crystal into the solution and it sets just as fast and just as completely, into a shape no one wanted.
This is exactly why the design choices are not optional decoration. They are the steering. To be clear about the claim: a community without deliberate values does not stay neutral and wait for you. It drifts — and the drift is rarely kind. So the lesson I take from sixteen months is narrower, and more demanding, than “community is good.” It is this: people are shaped by their rooms whether or not anyone is paying attention, so someone had better pay attention. The room will form its members either way. The only real question is whether it forms them toward something worth becoming.
Which raises the question that worries me more than any other in this essay: what happens when the someone paying attention is one person, and that person gets busy, or tired, or is simply needed elsewhere? Founder dependence kills more communities than dilution and noise combined — the room holds because one pair of hands holds it, and the day the hands are withdrawn, everything I have described quietly unwinds. I do not have a finished answer. What I have is a direction: slowly, and mostly without being asked, members have begun taking on responsibilities that are really apprenticeships — hosting the meetups, holding the standard in their own groups, doing the unglamorous work of paying attention. Succession in a community is not announced; it is grown, and from the inside it looks exactly like this. If Barakah HQ still holds in ten years, it will be because the attention became the habit of many people rather than the burden of one.
That is the work, as far as I can tell. Not to manufacture talent, which cannot be done, but to gather the people who already hold it in solution, hold the standards high, keep the trust intact, make sure the seeds that fall are the right ones — and then stay consistent long enough for the crystallization to spread.
I have leaned on a chemistry metaphor throughout, and I want to end by taking it literally, because I think the literal version carries the whole argument. A supersaturated solution does not crystallize because you command it to, or because you want it badly enough, or because you wait for the chemistry to get easier. It holds everything it needs and stays clear all the same. What it lacks is a seed — and the seed is almost never the solution’s own doing. It falls in from outside: a speck carried on the air, a fragment of a crystal that set somewhere else first. The entire argument of this essay is contained in that single fact. The talent is already in solution. What is scarce is the seed, and the seed is other people.
That is the most a community can do for a person, and I have come to think it is very nearly everything. It does not add what was not there. It is the fleck that falls at the right moment, the fragment of someone else’s crystal, the conditions under which what was already dissolved can finally take shape. We did not build the talent. We built the room where the seeds fall, and we kept the company in it good. The milestones that look small from the outside, the doors that seem to open on their own — all of it has felt, more than once, like barakah.
- I should flag where this metaphor misleads, since I am about to rely on it so heavily. A supersaturated solution is passive: it cannot seed itself, and it has no say in which crystal falls in. People are not like that. They have agency, they can go looking for their own seeds, and the best of them partly seed themselves. So the analogy understates individual will and overstates how much the room is doing. I keep it anyway, because the one asymmetry it captures — that the limiting input is usually external, usually small, and usually not more of what was already dissolved — seems to me basically right. ↩
- I do not want to claim ambition is purely a social inheritance; temperament and circumstance plainly matter, sometimes enormously. The narrower claim is that the social component is large, underrated, and unusually tractable — you can change someone’s room far more cheaply than you can change their temperament or their circumstances. It is the variable with the best ratio of leverage to cost, which is a different thing from being the only variable. ↩
- There is a version of this that is purely informational — you learn that the thing is doable. But I suspect the larger effect is emotional and identity-level rather than informational. People usually know, in the abstract, that products can be built. What a community changes is whether that abstract knowledge feels like it applies to them. ↩
- Paul Graham, “Cities and Ambition” (2008). His observation was about cities: each great one amplifies a different ambition, and you catch the message from the air, in a hundred small cues nobody consciously sends. The corollary this essay leans on is that a message which arrives ambiently can also be designed — a room inside a city can carry a different whisper than the city around it, which is good news for builders in cities that whisper nothing much at all. ↩
- To be clear, anonymity is not worthless; some of the most valuable communities ever assembled — much of open source, much of the early internet — run on it, and produce staggering amounts of value. What anonymity does not reliably produce is the specific, relational, remembered-and-returned kind of generosity I am describing here. The two can coexist. I am making a claim about one of them, not ranking the two. ↩
- Mark Granovetter’s 1973 work on weak ties remains the cleanest statement of why acquaintances, rather than close friends, are the usual conduit for new opportunities: your close circle mostly knows what you already know, while the looser edges of your network reach into information you do not have. A large-scale experiment published decades later broadly confirmed the effect, with the wrinkle that the most useful ties were moderately weak rather than the very weakest — which, if it holds, is close to an argument for exactly the mid-strength relationship a curated community manufactures on purpose. ↩
- These figures — roughly four hundred members, eight groups — are a snapshot, and a snapshot of a deliberately slow-growing thing goes stale in a predictable direction: it undercounts, and it does so a little more every month. I cite the order of magnitude rather than the precise number, because the number is not the point. The smallness is the point, and the smallness is on purpose. ↩
- The rigorous version of this objection is econometric: I have no control group, no randomization, and no way to observe the counterfactual in which the same people never joined. Every piece of evidence I offer is therefore consistent with pure selection. I argue in the main text for a treatment effect layered on top of the selection effect, but I want to be explicit that argue and believe are the correct verbs here, and prove is not one of them. ↩
- I’ll resist listing names and numbers here, partly out of taste and partly because any snapshot goes stale; the public showcase and the members’ own stories carry the specifics for anyone who wants them. The point is the distribution, not any single data point. ↩
- For my own part, the metaphysics is not underdetermined at all: the surplus is from God, and the arithmetic of trust and weak ties is the means He set it in – a believer is not asked to choose between the mechanism and the Giver of the mechanism. I keep both readings in the main text for the reader who does not share that premise, because the thing to do is identical either way: gather good people, hold the standard, keep the trust intact, stay consistent. An essay need not convert its reader to be useful to them. ↩