MacGyvering your Docs
summary
Argues that activism methods scale documentation: map a concrete Theory of Change (backward steps, thresholds like converting 25% or even 5% of developers), use low‑cost people tools (LinkedIn outreach, supporter journeys) plus pragmatic tech (set up GitLab, run Robot Framework and CI), and measure outcomes not pages. Gives examples: a gitlab install that increases collaboration but users adopt it imperfectly, and warns about burnout, scope creep, and the preacher complex.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:58Deepest darkest feelings
- 5:47We need help
- 9:00What is MacGyvering
- 12:14Nonprofits
- 18:35Hard Words
- 25:49Flip Coring
related talks
24mDocs Advocacy is Dev Advocacy
40mDocs Tools for OSS Maintainers
40mFrom resistance to adoption: navigating the challenges of docs-like-code
29mHumanizing Your Documentation
29mMove Fast and Document Things: Writing internal docs at fast-moving organizations
20mDo Docs Better: Practical Tips on Delivering...
40mDocumentation as User Experience
37mTaking a step back: Analysing your documentation