Seven habits of increasingly technical technical writers
summary
Seven concrete habits land as actionable moves not platitudes: teach yourself how to learn, avoid saying “I am not technical” and instead say “I can’t do this yet,” turn overwhelm into curiosity and break big mysteries into smaller questions, ask structured specific questions in Slack, tinker locally (docs‑as‑code work with Docosaurus and a website replaced theory with debugging), note the 50th or 2,000th time builds evidence, and choose “good enough” over perfection.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:02Why technical skills aren't the secret
- 5:16Habit 1: Avoid essentializing experience
- 7:05Habit 2: Turn overwhelm into curiosity
- 9:10Habit 3: Balance reliance on others
- 13:23Habit 4: Learn by doing and embrace mistakes
- 17:40Habit 5: Notice impostor syndrome
- 19:25Habit 6: Don't let perfect block good
- 21:15Habit 7: Love the learning process
- 23:21Conclusion
- 25:30Q&A: Hiring habits
- 28:17Q&A: Burnout and self-worth
- 31:07Q&A: Learning new things
- 32:11Q&A: Personality traits
- 33:35Q&A: Tracking progress
- 35:42Q&A: Keyboard clackiness
related talks
31m7 Essential Tips for the Enlightened Tech Writer
35mEngage or Die: Four Techniques for Writing Indispensible Docs
29mTen Tips For Teaching Technical Topics
01h 01mHabits of a Highly Effective Technical Manager
48mEnding Keynote: 7 Principles of Productive Software Developers
37mFailing Well: A Practical Guide to Growth for Technical Writers
52mKeynote: Steps to Wisdom
05mTell Your Technical Story