The AWS Community Builder program is a recognition, but it is also an obligation.
The recognition is that you have been contributing to the technical community in meaningful ways - writing, speaking, helping others navigate the same technical problems you have been working through. The obligation is to keep doing it, and to do it in ways that extend what you know to people who need it.
The hat on the desk is a reminder of both.
What community building actually involves
The work of community building is mostly writing.
Writing documentation that people can actually follow. Writing tutorials that start where the reader is and get them somewhere useful. Writing posts that explain not just how to do something but why the choices that went into it matter. Writing questions in public forums where other people will find them and benefit from the answers.
None of this is glamorous. Very little of it has immediate visible payoff. A tutorial you write today might help a hundred people you will never meet, at times spread over years. The feedback loop is long and indirect.
The work is worth doing anyway, for the same reason that juggling in a field is worth doing even when no one is watching: the practice builds something.
Community contribution builds a shared body of knowledge that reduces the difficulty of the next person who faces the same problem. The value is cumulative and distributed in ways that do not always return to the person who contributed.
Technical community and juggling community
Both communities have the same structure: a practice that is hard to learn alone, that benefits significantly from the existence of people who have already learned it and are willing to share.
Every juggler learned from someone or something - a workshop, a video, a book, another juggler who showed them the throw. The skill propagated from person to person through communities where sharing the skill was the point.
Technical communities work the same way. The reason anyone gets good at cloud architecture, or machine learning, or software engineering is partly that people who knew these things wrote them down and shared them. Every tutorial and documentation page is a node in a network that makes the skill accessible to more people.
The desk as a map of the practice
A community builder’s desk is not a curated setup. It is a working desk with the things that belong to this work.
Technical tools on the screen. Community artifacts visible (the hat, the recognition of belonging to something larger). Physical practice props nearby. Coffee because the work takes time.
This is what the practice looks like when it is actually happening: ordinary, a little cluttered, sustained by habit and caffeine and the occasional reminder that it is connected to something larger than the immediate task.
The juggling and the community work and the technical work are all on the same desk because they are all the same practice, expressed in different forms.
Read next: The Ripple Effect - how one demonstration changes a room.