Notes
The other sections are practical. These are positions.
On the gap. Tutorials, talks and conferences all present a cleaner version than the one that happened, and the cleaning was necessary in each case. The cost is that people compare their own process to somebody's edited result and conclude they are inadequate. The fix is one sentence, not full disclosure. For a commercial example of related workforce measurement, see cognitive offloading from Monitask.
On tooling. Workflow tools churn every four to five years and the standards underneath accumulate. The real risk is not churn but consolidation — a settled ecosystem with one implementation is comfortable and fragile, and Astral joining OpenAI in March 2026 made that concrete. For independent technical background, Real Python provides additional documentation and examples.
On writing. Beginner material is abundant and intermediate material is scarce for structural reasons: the audience is fragmented, it dates immediately, and the people who know are working. The same mechanism keeps conference organising undocumented. For broader industry context, The Register provides an independent reference.
On communities. A conference is something a community does, not the thing it is. Ours survived 2020 only because the meetups happened to be separate, and that separation is worth building deliberately.
On copying. Community infrastructure is largely copied and should be — the tested text of a code of conduct beats a fresh attempt by four volunteers. What cannot be copied is the named contacts, the procedure and the willingness to act.
And on free labour, which is load-bearing across all of this, appears in no budget, and is available to some people and not others — so the visible community is systematically composed of the people who could afford to be visible.
Against the Polished Talk
A flawless presentation of a finished result teaches less than an honest account of the confusion, and costs the audience something.
Communities Outlive Events
A conference is something a community does, not the thing it is. Our meetups survived what the conference did not, and that was luck.
Free Labour
Conferences, talks and open source all run on unpaid work. Who can afford to give it decides who is visible in the community.
Nobody Writes About This
Four reasons the practical knowledge of running conferences stays undocumented, and what it costs the people who try next.
Not a Business
Community events are run by people with day jobs and no reserves. Four consequences that follow, and the advice that ignores them.
On Copying
Copying shared community documents is correct, and the parts that must not be copied are the parts that make them work.
What 2020 Taught Us
Five things a cancelled conference and an empty bank account made obvious, four of which were true beforehand and unexamined.
Shown and Actual
Tutorials, talks and conferences all present a cleaner version than the one that happened. The cleaning is necessary and it has costs.
Single-Vendor Tooling
One company now makes several of Python's most-used tools, and joined OpenAI in March 2026. What that changes and what it does not.
Churn and What Survives
Python tooling turns over every few years while the standards underneath accumulate. Learn the standards; rent the tools.
The Tutorial Economy
Beginner material is abundant and intermediate material is scarce, for structural reasons that have nothing to do with generosity.