Hacking Your Documentation: Who Should WTFM?
summary
Argues that dedicated technical writers measurably improve security and productivity: Google Cloud finds teams with good docs are 2.4× more productive and 3.8× better at implementing security practices, while organizations waste about $2.5M/year searching for information. Technical writers act as distillers, not subject‑matter experts, run draft content past SMEs, reduce developer/tester burnout, cut support tickets, and speed remediation; practical routes to hire or become one include documenting GitHub projects and producing a small portfolio.
AI-written summary · about
chapters (9)
- 0:00Introduction and agenda
- 1:07The value of documentation
- 2:38Who should write the docs
- 4:55Benefits of technical writers
- 7:01Addressing counterarguments
- 8:33The role of a writer
- 10:19Starting a career as a writer
- 14:01Advice for practitioners
- 15:40Key takeaways and Q&A
related talks
12mWhy Work with a Tech Writer?
25mTechnical Writing for Developers and Engineers
21m7 Values of Effective Tech Writing Teams
36mTechnical writing in English
44mCreating a Culture of Documentation
34mDocumentation Thinking Beyond the Docs: Lessons from Decision-Facing Technical Writing
30mTechnical Documentation
01h 24mWriting Documentation - Practices and Theory