Who Writes the Docs?
summary
Asserts that documentation succeeds when responsibility shifts: developers testers product managers and support staff actually produce and maintain docs while specialist writers coach and focus on hard problems. Describes concrete practices: tagging text in the repo with a Tibet comment to flag copy needing attention and treating docs as part of whole team quality. Promotes a documentarian mindset—empathy for new users, choice of the right tool, early questions about what users need—and reports that doing this makes prototypes usable and feedback measurable.
AI-written summary · about
chapters (9)
- 0:00Documentation culture intro
- 1:48Documentation value
- 3:38Need specialist writers?
- 7:14Turf vs expertise sharing
- 11:36Team docs responsibility
- 13:21Documentarian mindset
- 15:26Team without documentarians
- 18:37Colleagues as documentarians
- 21:52Specialists' added value
related talks
01h 24mWriting Documentation - Practices and Theory
28mStop writing docs; start helping!
44mCreating a Culture of Documentation
20mOh My Docs!
39mDevelopers Documentation: your hidden strength
40mDocumentation as User Experience
47mThe Things You Don't Want to Write - Documentation
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?