Move Fast and Document Things: Writing internal docs at fast-moving organizations
summary
Describes concrete fixes: stop guessing and snoop for the real problem (tooling was fine; assumptions and scattered docs were the issue), pick one canonical home for docs (wiki vs READMEs vs photos of whiteboards), tie documentation format to company values (learning vs longevity), and use small experiments (weekly show‑and‑tells, living style guides) to validate them. Evidence: onboarding goes from three days to get running to a new hire able to commit and deploy before lunch.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:45Types of technical docs
- 3:46Story: Slow-moving nonprofit
- 6:10Story: Digital agency
- 9:03Story: Fast-paced startup
- 13:21Identifying documentation issues
- 17:18Common documentation pitfalls
- 20:05Aligning values with documentation
- 25:09Implementing solutions and culture
related talks
33mWhat The Doc?!?! How to Write and Read Documentation That Allows You To Get Sh*t Done!
01h 24mWriting Documentation - Practices and Theory
38mThe Stuff You Don't Want to Write... Documentation
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?
39mWe're Agile, we don't do documentation
39mSave a Dev, Write a Doc!
29mHumanizing Your Documentation
44mCreating a Culture of Documentation