Technical Writers Circle
Clear writing about hard technical work.
Good engineers rarely write, and good writers rarely understand the systems. Documentation is often the first thing cut and the first thing users need. Members here write the docs, guides and essays that close that gap.
Open to every member. Join now and help shape what it builds next.
What we work on
Four problems define this community’s work right now. Every sprint, review and essay here comes back to one of them.
Documentation that ships
API references, guides and runbooks that live inside real systems and get read.
Essays from the field
Long-form writing for TechOps News about what actually happens when you build here.
Peer review
Line-by-line edits from people who write for a living, so every draft gets sharper.
Writing as a career
Building a paid technical writing practice, with portfolios clients and employers trust.
Questions we are working through
No one has settled these yet. They come up in every sprint, and members argue them out in essays and reviews.
- How do you explain a complex system without dumbing it down?
- Who should own the docs: engineers, writers or both?
- How do you write well for readers working in their second or third language?
Our impact
- Essays published on TechOps News
- 6
From the field
All essays · 26 min of reading- Start with the decision, not the modelMost AI projects that stall were never wrong about the model. They were vague about the decision the model was meant to improve. How to start from the decision, with a worked example.
- Retrieval before fine-tuning: making an LLM answer from your own documentsIf you want a language model to answer from your company's documents, start with retrieval, not training. A worked example, from the first document to the first honest measurement.
- Test your AI feature like you would test a payments flowNobody ships a payments change because it looked fine in a demo. AI features deserve the same discipline. A worked example of building an evaluation suite your team will actually use.
Your first build
New members pick one of these for their first month. Each is small enough to finish and real enough to show an employer or an investor.
A getting-started guide
Take an open-source tool with weak docs and write the guide you wish had existed.
- Docs
- Markdown
- Testing
An essay from your work
Turn one real problem you solved into an essay for TechOps News, edited by the circle.
- Essay writing
- Editing
- Research
An API reference
Document a real API end to end, with runnable examples and error cases.
- APIs
- Examples
- Structure
Words you will hear
New here? These come up in your first week. Plain meanings, no jargon.
- Docs-as-code
- Writing documentation in the same repository and review process as the code itself.
- Runbook
- Step-by-step instructions for operating a system or handling an incident.
- Style guide
- Shared rules for tone, terms and formatting, so many writers sound like one.
- Information architecture
- How content is organised so readers can find what they need.
Who you will meet
- Technical writers and editors
- Engineers who want to write
- Developer advocates
- Product and documentation managers
How the community runs
- Every week
Build sprint
Bring a real problem from your work in the sector. Leave with progress, reviewed by people who have shipped the same thing.
- Every week
Office hours
Drop in with a model that will not converge, a regulator question or a hiring decision. Practitioners answer.
- Every month
Demo day
Members show working systems to the community, mentors and invited investors. Demos, not decks.
The team behind it
Lead the Technical Writers Circle
We are looking for experienced practitioners to lead this community: host one session a month, review members’ work and shape what it builds next.
Tell us about your workJoin the Technical Writers Circle
One payment of $15 makes you a member for life: every community, its sprints, reviews and events. No subscription.