Forming Communities

“They thought I’m one, but I’m many.”
— Bakry

Recently, I found myself collecting scattered notes about communities, the ones I joined, the ones I reshaped, and the ones I built from instinct and frustration. the more I reflected, the more I realized that my relationship with communities has never been passive. I rarely just participate. I observe, evaluate, and eventually attempt to restructure.

When I entered university, many Sudanese tech communities followed a familiar model. they organized workshops, exhibitions, and speaker sessions. some were part of global initiatives like [Google Developer Student Clubs (GDSC)]( https://gdg.community.dev , and others were local initiatives such as the School Student Exhibition (SSE) .

These communities were excellent at inspiration, they brought in impressive speakers. they hosted events that sparked ambition. they created environments where students could briefly feel closer to something global and powerful.

But inspiration, I realized, is not the same as transformation. a workshop can excite you for a week. An exhibition can impress you for a day. but skill requires repetition, structure, and discomfort. the dominant model optimized for stimulation, not mastery.

That observation became the seed of my involvement. when I joined GDSC and SSE, I did not join to attend. I joined to experiment. could we shift from inspiration heavy programming to skill heavy infrastructure? could we deliver modular, consistent material that allowed someone to actually build something from scratch?

Because listening is easy, building is different, over time, we began emphasizing structured sessions, project based learning, and continuity. Instead of one off events, we tried to design learning paths. Instead of applause, we aimed for competence. The difference was subtle but powerful: exposure creates excitement; execution creates confidence.

Observe

That period taught me something essential: before building anything, become an external observer. detach yourself from the emotional wave. study the system. ask whether its trajectory leads somewhere meaningful. most people inside a community are too immersed in its rhythm to see its structural flaws.

Need

Another principle emerged: communities must begin with a real need. If you cannot clearly articulate what gap you are filling, your initiative will become redundant. Many communities fail because they replicate existing structures without differentiation. Momentum driven by novelty fades quickly. Momentum driven by necessity sustains itself.

Leadership

Leadership, however, determines whether that necessity translates into impact. before committing to any community, I learned to evaluate the leader. are they adaptable? are they fully invested? are they capable of long-term thinking? sometimes I joined initiatives simply because I trusted the character of the person leading them. leadership shapes atmosphere. atmosphere shapes output. a committed leader unconsciously creates discipline. a distracted one unconsciously spreads confusion.

Team

Then comes the team. a community’s health is determined not just by its mission, but by how its team is structured. there are lots of variables to account for when picking the team, younger members bring energy and vibrancy. they experiment freely. but they require space and mentorship. senior members bring precision and reliability. they execute efficiently. but too many seniors can create a mechanical atmosphere.

Balancing those dynamics is delicate, in earlier years, I leaned too heavily toward performance. I pushed teams aggressively. long hours. high expectations. constant output. what I failed to recognize was that communities are ecosystems, not factories. without emotional ventilation, pressure accumulates. only in recent years did I start incorporating intentional breathing space, informal interactions, humor, moments of ease. productivity without sustainability is fragile.

One of my earliest experiences with community structuring began when I joined an editing collective called 249 Unit around 2018. We learned tools like Adobe After Effects , Sony Vegas , and DaVinci Resolve . At first, we were roughly at the same skill level. Growth was collaborative and simple.

Then expansion created chaos, new members entered at different levels of seriousness. goals diverged. without structure, friction happened. there was no formal leadership system, only founding members and early participants. I was young, but I sensed decay, so I introduced a five tier ranking structure based on skill and contribution. we created application forms for newcomers, clear levels replaced vague belonging. surprisingly, structured competition increased motivation rather than harming cohesion. momentum returned. growth regained direction.

Looking back, that was likely my first conscious experiment in community architecture, a few years later, that instinct matured into something more ambitious.

At sixteen, a friend of mine called Mustafa repeatedly suggested we build our own advertising agency. eventually, I agreed. we called it Dart . I gathered designers, editors, and account managers from my network. ee secured our first client, a Sudanese restaurant named Katkoot.

This was no longer a learning club. It required contracts, pricing models, workflow systems, and accountability. before Dart, I had worked as a freelance editor for Sudanese gaming creators. I studied high level editors obsessively, how they priced their services, how they structured revisions, how they positioned themselves. Dart became an application of those observations.

That experience solidified something in my mind: talent is abundant; structure is rare, communities collapse not because members lack ability, but because systems lack clarity. passion without infrastructure burns out. Infrastructure without humanity suffocates.

Over time, I realized that my involvement in communities was never purely social. It was architectural. I am drawn to how systems behave, how incentives shape action, how culture emerges from repeated patterns, how leadership decisions ripple through groups.

“They thought I’m one, but I’m many.”

In communities, I have been a learner, a critic, a builder, a reformer, and sometimes a quiet observer. each role revealed something about collective behavior.

If there is one conclusion I keep returning to, it is this: communities are living systems. They require clarity of purpose, disciplined leadership, thoughtful team design, and respect for human limits. they must solve real problems. they must evolve with their environment. and they must remember that every metric hides a human being behind it.

I continue building not because I crave belonging, but because I am fascinated by design, not just product design. not just system design. but human design, at scale.