Dungeons, Dragons & Developers
summary
Compares tabletop roles to engineering roles and claims teams with mixed skills beat a roomful of lone experts: avoid four competing “wizards,” prefer a balanced party with testers, communicators and backend leads. Cites concrete tooling mentions — caverns of kubernetes, master azure, even a mandatory block of chain requirement — to argue tech mandates often slow teams. Recommends regular half‑hour check‑ins, share tribal knowledge (no silos), prefer reusable fixes over one‑offs when appropriate, enable monitoring/logging in production, and avoid crunch; these practices lead to successful deployments.
AI-written summary · about
chapters (13)
- 0:00Intro
- 4:32Dungeons & Dragons
- 6:16The dungeon master
- 7:36Our story begins with you
- 9:31Wizards
- 10:58Our party
- 12:25The quest
- 16:25Quest requirements
- 23:48Losing the path
- 25:57Decisions need context
- 31:58The final hill
- 35:31Summary
- 36:38Outro
related talks
45mDungeons Dragons & Developers
37mDungeons, Dragons and Developers
06mDungeons and Dragons....and DevOps
50mDungeons and Developers: Uniting Experience Levels...
46mDungeons & Dragons & Development: How Playing Games Makes...
31mDungeons and Developers: Uniting Experience Levels in...
31mDungeons and Developers: Uniting Experience Levels in...
33mWhat I've learned by dealing with a Dungeon Master
