Dungeons, Dragons and Developers
summary
Compares D&D mechanics to software teams and makes concrete claims: a lopsided team of “wizards” who favor algorithms fails while a balanced party of fighters, rogues and clerics succeeds. Uses Kubernetes, machine learning and a mandated “block of chain” (blockchain) as concrete tech examples, shows tradeoffs with the river-crossing choices (rope, build a bridge, fly, workaround), demonstrates costs of knowledge silos when one person hides a troll’s fire weakness, warns against crunch (exhaustion), and notes luck like a natural 20 or 1 still matters.
AI-written summary · about
chapters (27)
- 0:00Intro
- 2:58Dungeons & Dragons
- 4:25The dungeon master
- 5:06Our story begins with you
- 5:23Your alignment
- 6:40My alignment?
- 7:08Wizards
- 8:18Our party
- 9:44The quest
- 13:47Quest requirements
- 15:02Fight your side
- 16:00Ok, let's get going!
- 17:14Hey folks, can I join you?
- 20:37Losing the path
- 21:16Crossing the river
- 22:53Decisions need context
- 23:42Hey DM, can we try?
- 25:00Sometimes you roll a natural 20
- 25:24And sometimes you roll a natural 1
- 25:38Be prepared
- 26:23Use past experience
- 28:59The final hill
- 29:31Exhaustion
- 31:46Reaching your goal
- 33:29Victory, reward & reflection
- 35:22Summary
- 37:04Outro
related talks
45mDungeons Dragons & Developers
37mDungeons, Dragons & Developers
06mDungeons and Dragons....and DevOps
46mDungeons & Dragons & Development: How Playing Games Makes...
50mDungeons and Developers: Uniting Experience Levels...
02mSimilarities Between D&D and Learning a New Tool as a Dev
31mDungeons and Developers: Uniting Experience Levels in...
31mDungeons and Developers: Uniting Experience Levels in...
