Documentation: The Missing Pieces
summary
Most documentation fails because it assumes knowledge and skips exact steps; fix it by spelling out acronyms, replacing foo/bar with descriptive names, and listing concrete environment requirements including exact versions, dependencies, whether a free tier suffices, and an estimated completion time. Capture and name screenshots to match steps and provide alt text, validate links, add quick-jump anchors, minimize distracting GIFs, and make examples platform-agnostic or provide a Docker setup so readers can reproduce results reliably.
AI-written summary · about
chapters (12)
- 0:00Introduction to documentation gaps
- 1:33SMH IDK acronyms problem
- 8:58Step skipper in tutorials
- 13:47Foo bar ambiguity issue
- 16:16Tell me what I need prerequisites
- 20:34Random screenshot hudis
- 22:43Oh you didn’t know that assumption
- 24:50No more 404s broken links
- 25:56Jump to recipe quick links
- 26:57Not now jiffy gifs distraction
- 29:06Works on my machine issue
- 30:31Summary best practices
related talks
29mDocumentation: The Missing Pieces
29mTaking Stock of Your Documentation
33mWhat The Doc?!?! How to Write and Read Documentation That Allows You To Get Sh*t Done!
48mBeyond Words: Crafting User-Friendly Documentation
37mHumanising Your Documentation
26mPractice Makes Perfect: Write Accessible Documentation
46mTechnically Speaking: Improve your code with documentation
51mWriting the Darn Docs
