Judas Priest Ate my Scrum Master
summary
Claim: a measurable gap in value perception separates engineers and technical writers, backed by applying Brooks, Conway, Pareto and Lehman laws to docs and code. Evidence: contributor metrics show sudden drops, a startup case shows documentation reduces support calls and saved money, and refactoring attention to docs restores product stability. Concrete takeaways include treating docs as product, adding writers affects ramp and communication like engineers, and specific team restructures that actually work.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:38Technical Writing
- 5:15Sturgeons Law
- 6:27Community Management
- 11:08Show of Hands
- 11:39Brooks Law
- 13:51Conway Law
- 15:23Software Evolution
- 17:34Pareto Law
- 18:42Technical Writers
- 19:17Push
- 21:19Maintain familiarity
- 23:55Tools and processes
related talks
47mThe Psychology of Software Teams
38mThe Human Element in Development
48mA Teacher, an Economist and a Developer Walk Into a Bar
31mStorytelling for Engineers
37mFailing Well: A Practical Guide to Growth for Technical Writers
52mThe Developer Rhapsody
26mDeveloper Joy – How Great Teams Get s%*t Done
46mCracking the cadence of your software engineering 1:1s