Almost None to Some: Driving DISQO's Doc Culture as a Solo Documentarian
summary
Solo technical writing moves Disco from almost no docs to some by shipping an internal docs hub (Slate/Hexo/wiki style), running docs-as-code with markdown + git + merge requests, and treating doc releases like code deployments. Five tactics: find comfort in incompleteness, influence not force (RFC to treat docs as tech debt fails in a low‑maturity org), empower contributors via onboarding and markdown/git training, form a monthly tech‑doc guild, and keep a visible developer blog — all working to raise contribution and visibility.
AI-written summary · about
chapters (15)
- 0:00Start
- 5:36remind ourselves of the limits of our resources
- 8:51joining stand-ups demos and post-mortems
- 9:30create surveys
- 12:04designing the architecture for our internal documentation hub
- 13:51create a technical writing documentation
- 15:20establishing key partnerships
- 16:47finding at least one ally per job title within your organization
- 20:49develop standards for different types of documentation
- 21:45start a slack channel
- 30:14scrum sprints
- 34:59offloading that glue work onto other people
- 36:04starting a documentation initiative in an organization
- 36:50creating a distinctive identity
- 38:08balance respecting and maintaining the post author's voice
related talks
24mWho Writes the Docs?
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?
36mTo document, or not document that is the question
40mDocumentation as User Experience
47mThe Things You Don't Want to Write - Documentation
38mThe Stuff You Don't Want to Write... Documentation
13mTechnical documentation – how can I write them better and why should I care?
44mUseful and Beautiful Developer Docs and How to Create Them