What I've learned by dealing with a Dungeon Master
summary
Identifies the Dungeon Master anti‑pattern where one entrenched author controls design, hoards domain knowledge and resists change, and shows concrete fixes: proxying communication, introducing continuous integration (deployment pipeline rewrites take ~6 months, CI fully works after ~12 months), making slow architectural refactors, building a small internal framework to speed features, and using knowledge surgery—careful, shared test additions—to surface bugs and convert the DM into a peer; most measures partially succeed.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:47What Is the Dungeon Master
- 4:21Types of Dungeon Master'S
- 5:19How Can We Identify a Dungeon Master in Our Organization
- 5:47Defensiveness or Resistance To Change
- 23:55How Does the Dungeon Master Affect a Team
- 25:30Becoming a Dungeon Master
related talks
06mDungeons and Dragons....and DevOps
37mDungeons, Dragons & Developers
45mDungeons Dragons & Developers
37mDungeons, Dragons and Developers
37mIt's All Just a Game
02mSimilarities Between D&D and Learning a New Tool as a Dev
46mDungeons & Dragons & Development: How Playing Games Makes...
35mPlease Understand Me