I am building a developer community — a bootcamp-plus-community for people learning the trade properly. It is real and unfinished, so this post is a progress report rather than a lesson. I have no outcome to report yet.
What I can report is that the part I assumed would be hard is not the hard part.
What I expected to be hard
The platform. Content, structure, assessment, the engine that routes somebody through a track suited to their weaknesses. That is engineering, it is the thing I am good at, and I was quietly looking forward to it.
It is a solved problem. Off-the-shelf tools do most of it, and what they do not do I can build. Two weeks of work, generously.
What is actually hard
Being the reason somebody comes back on a Tuesday when they are tired.
A community is not an artefact. It is a repeated behaviour by people who owe you nothing, and it decays by default. Every week it needs a reason to exist that is larger than the friction of showing up, and nothing about being able to build software helps with that.
The uncomfortable version: the skills are close to opposite. Building rewards going quiet for a long stretch and emerging with something finished. A community punishes exactly that. Disappear for three weeks and you do not come back to a slightly stale project; you come back to a room that has learned it can do without you.
The one thing I am reasonably confident about
Communities that work seem to be organised around a thing being done, not around a topic.
A community about a subject is a forum, and forums die quietly. A community around a shared activity with visible progress — people shipping, being reviewed, being stuck in public — seems to hold, because there is a reason to return that is not social obligation.
That is why mine is built around assessment and a route through it rather than around lessons. Not because I have proven it works. Because when I look at the ones that lasted, that is the property they share, and it is the only design decision I would defend right now.
What I would want to know before calling this a career
Whether it compounds or resets. A software system I built five years ago still runs. Does a community I built five years ago still exist, or is it a treadmill where stopping means it is gone in a quarter?
I genuinely do not know. Ask me in two years and I will have a real answer instead of a hypothesis, and if the answer is that I could not sustain it, I will write that post too.
Where I come into this
Nothing being sold here either, but the free website check is open to anyone: a minute, no signup, and it reports what your own pages are doing wrong. Useful whether or not you ever speak to me.
No advice to sell here yet — I am mid-build. If you have run a community that lasted more than a couple of years, I would like to ask you what held it together. That is a receipt I do not have and would rather borrow than guess at.
Post 8 of 10. The next two are jobs I hold, and I have receipts for both.
