Metaphors are Everywhere: Ideas to Improve Software Development
summary
A real case shows one dominant shooter who breaks league records for three‑pointers but drops team win rate by about 30 percentage points because he hoards the ball, teaching the cost of an ego player vs a blue work teammate who does rebounds, screens and sets others up. Fiction writers use editors, writing groups and throwaway 10,000‑word monologues; Sanderson’s rule that limitations beat powers guides design. Game studios run 90‑minute company playtests monthly, and trading‑card balance patches arrive every few months, forcing constant deck‑building tradeoffs of tempo versus long‑term value.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:12Injury to metaphors in software
- 5:25Basketball team dynamics
- 8:33Ego players harm teams
- 10:58Glue work value
- 12:43Team composition beyond skills
- 14:53Story writing patterns
- 19:50Logical consistency in worldbuilding
- 22:38Code reviews and writing feedback
- 25:06Limitations make tech interesting
- 27:54Unfinished projects in fiction
- 29:00Game dev vision and collaboration
- 31:28Playtesting and UX awareness
- 32:51Jobs as past reactions
- 34:16TCGs as software metaphors
- 37:44Tempo versus value
- 40:31Why metaphors connect
- 42:59Final takeaways and call to action
- 43:21Q&A
related talks
54mDev psychology: your own brain is your worst enemy
19mThe Power of Metaphors
57mHard truths and soft skills: 10 pieces of advice for novice game devs
39mGame Theory and the Art of Teamwork in Software Development
01h 01mLies Developers Tell Themselves
40mMetaphors We Compute By
58mProtecting Your Pixel Heart: Making Games with Empathy
45mDungeons Dragons & Developers