Dungeons Dragons & Developers
summary
Compares a chaotic team of four wizards (senior devs hoarding skills) with a balanced party and argues that mixed roles beat everyone being a lone hero; shows real tradeoffs — quick script vs building a bridge, using Kubernetes, CI and a mandated GPT/large language model can be negotiated rather than imposed, and one engineer “saving the day” with an LLM still creates knowledge silos. Demonstrates pitfalls (Rogue steals the crystal of unending technical debt — trap = missed monitoring), stresses regular check‑ins, small retrospectives, and avoiding burnout.
AI-written summary · about
chapters (23)
- 0:00Welcome to the strange tower
- 1:04Simplifying Dungeons & Dragons for developers
- 3:53Dungeon master as PM
- 6:00Alignments and team dynamics
- 8:54Code wizard stereotype
- 11:45Dangers of solo heroes
- 13:55Plan first, code later
- 15:01Balanced teams succeed
- 17:28Handling unreasonable reqs
- 19:57Micromanagement kills
- 21:01Tuckman stages of growth
- 22:43New members shift dynamics
- 25:31Avoid meeting daydreams
- 27:58Choosing the right solution
- 29:42Breaking rules with purpose
- 32:10When projects go wrong
- 33:57Leverage past experience
- 36:03Cost of knowledge hoarding
- 38:10Exhaustion of crunch time
- 40:16Always check for traps
- 41:40Monitoring is not optional
- 43:01Learning from retrospectives
- 44:26Key takeaways
related talks
37mDungeons, Dragons and Developers
37mDungeons, Dragons & Developers
06mDungeons and Dragons....and DevOps
46mDungeons & Dragons & Development: How Playing Games Makes...
33mWhat I've learned by dealing with a Dungeon Master
11mHow to tame your team monsters!
37mIt's All Just a Game
27mYellow Brick Code: Lessons from The Wizard of Oz on Enhancing DevEx