The Zen of Technical Writing
summary
Technical writing frames itself as practice borrowing concrete techniques from Buddhist ideas: documentation treats change as impermanence, approaching new domains uses a beginner's mind, and figurative thinking becomes a tool for clarity through symbolism and metaphor. Claims include treating obsolescence like sand paintings, reframing bug reports as good fortune, and learning unfamiliar topics (instruction set architectures, hardware) by writing into them. Delivery is anecdotal, reflective, and grounded in brief concrete examples.
AI-written summary · about
chapters (4)
related talks
21mAvoiding Anti-patterns in Technical Communication
37mFailing Well: A Practical Guide to Growth for Technical Writers
13mWe’re Not in Kansas Anymore: How to Find Courage while Following the Technical Doc Road
31mZen of Testing
36mThe Exceptions We Don't Catch in Technical Conversations
30mJudas Priest Ate my Scrum Master
49mKeynote: Debug your thinking
52mKeynote: Steps to Wisdom