The Stuff You Don't Want to Write... Documentation
summary
Argues that documentation must be written alongside code and baked into the definition of done so each two‑week sprint produces usable notes, and demonstrates using Markdown + Mermaid + Azure DevOps Wiki to keep docs with the repo. Shows a real onboarding doc that lets a new team member be productive the next day, contrasts that with four or five hundred printed pages nobody reads, and claims this workflow reduces interruptions and stale knowledge.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:11Documentation in tech teams
- 7:26Who creates documentation and when
- 13:07Improving documentation
- 22:49Demo: Docs with code
- 38:20Q&A
related talks
47mThe Things You Don't Want to Write - Documentation
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?
51mWriting the Darn Docs
01h 24mWriting Documentation - Practices and Theory
36mTo document, or not document that is the question
26mWe're Agile, We Don't Do Documentation
29mMove Fast and Document Things: Writing internal docs at fast-moving organizations
44mUseful and Beautiful Developer Docs and How to Create Them