Avoiding Anti-patterns in Technical Communication
summary
Lists four concrete anti-patterns: keeping it brief (example: “Notebook won’t run” Slack messages that force extra triage), chasing likes (99% accuracy illusion from <1% positive class in a binary classifier), useless analogies (culturally specific refs like Taylor Swift or Will Smith that don’t map), and focusing only on tricky internals instead of user-facing changes. Recommends practical fixes: keep essential context, state the desired outcome, and measure useful engagement (comments or reproductions), not vanity metrics.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:48What is an anti-pattern
- 3:15Why technical communication matters
- 4:17Anti-pattern one keeping it brief
- 7:05Anti-pattern two chasing likes
- 11:17Anti-pattern three useless analogies
- 14:13Anti-pattern four focusing on tricky bits
- 17:44Key takeaways and audience focus
- 19:14Q&A session
related talks
46mCommunication antipatterns and where to find them
38mTeam Meetings That Don't Suck - Avoid Retrospectives Antipatterns
59mRetrospectives Antipatterns
49mRetrospective Anti-Patterns
26mCommunication: What are you Thinking About?
33mHow to Write Useful Technical Texts
41mNobody Likes Working With You
17mWelcoming People (and Other Hard Problems)