The Emperor Has No Docs
summary
Argues for a documentation‑first workflow that prevents the expert paradox by forcing names, edge cases and user intent up front; shows using the C4 model and the Google technical writing course to structure docs, and using Paradox/Confluence patterns so snippets stay in sync and are discoverable. Demonstrates a real case where documenting an API surface yields five distinct behaviors → five tests → trivial implementation, and uses BigDecimal and Uno rules as concrete surprises that prove code alone is not enough. Provides triggers and tiny habits that actually stick.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 5:06About the speaker
- 7:16From squire to developer
- 10:07Documentation frameworks
- 14:02Breaking the blank page cycle
- 23:31Building documentation habits
- 28:56Convincing stakeholders
- 34:32Fighting the documentation dragon
- 41:19The emperor’s secret
- 43:50Uno rules explained
- 47:34Q&A session
related talks
55mThe Emperor Has No Docs
01h 24mWriting Documentation - Practices and Theory
34mDocumentation Thinking Beyond the Docs: Lessons from Decision-Facing Technical Writing
36mTo document, or not document that is the question
39mWe're Agile, we don't do documentation
20mThe Curse of Documentation
33mWhat The Doc?!?! How to Write and Read Documentation That Allows You To Get Sh*t Done!
52mTechnically Speaking: improve your code with documentation