Be a Salmon

on YouTube ↗06m

" summary

Argues that writers must go upstream and change product wording before it lands in docs, not just polish it later. Describes pitching UX teams, pairing with ux writers, and drafting a first API design guidelines document and functional writing snippets to set consistent endpoint and UI text. Shows that creating those artifacts and processes actually reduces downstream rewrites and forces clearer names and messages rather than retrofitting bad copy.

AI-written summary · about

" chapters (6)

1. 0:00Intro
2. 1:00Tech Writers
3. 1:20Filter feeders
4. 4:00Upstream
5. 4:50Be a Designer
6. 5:40Conclusion

" related talks

• 43mFrom travel content to technical content: my journeyKate Santo · Write the Docs Prague 2021
• 22mWrite Prose, Not just programsPuneeth Chaganti · PyCon India 2020
• 35mEngage or Die: Four Techniques for Writing Indispensible DocsKelly O'Brien · Write the Docs Prague 2014
• 39mSearch First-Writing for non-writersHeidi Waterhouse · Open Source Bridge 2013
• 34mMoonshot mindset: A tech writer's guide to thinking big and breaking free from the GDZKate Wilcox · Write the Docs Berlin 2026
• 36mThe Invisible Work: What It Takes to Be the First (and Only) Tech Writer on the TeamAlina Desiatnikova · Write the Docs Portland 2026
• 50mDocs leadership: How to become a stronger leader for your teamJenn Leaver · Write the Docs Prague 2021
• 29mWhat I have taught developers about writingDavid Hooker · Write the Docs Prague 2014