The Games Developers Play
summary
Claims that naming patterns reduces repeat conflict and that awareness improves responses to emotional triggers The talk maps Eric Berne’s transactional analysis and the drama triangle, cites Berne’s 36 games (1957) and gives examples like now I’ve got you you son of a bitch, uproar and ain’t it awful Offers practical habits: Headspace meditation 5–10 minutes plus 5 minutes journaling in Day One (about a quarter hour) and reports improved calmness enabling more adult, less reactive code reviews and team interactions.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:49Modern developer myths
- 3:14Emotions vs rational coding
- 4:58Meet the speaker
- 7:05Illusion of control
- 8:28Transactional analysis
- 11:18Why models matter
- 12:02Code review conflicts
- 13:25Drama triangle dynamics
- 15:12Perpetual complaint game
- 19:31Breaking toxic patterns
- 21:19Mental health minute
- 22:49Stoic workday wisdom
- 24:13Emotions vs adult reasoning
- 25:37Software is team sport
related talks
44mThe Developer's Model for Talking to Managers
37mFixing the mistakes we -all- make as developers, leaders and teams
36mThe Developer's Model for Talking to Managers
48mIndividuals and Their Interactions...
52mDebugging Your Brain
39mGame Theory and the Art of Teamwork in Software Development
54mDev psychology: your own brain is your worst enemy
37mIt's All Just a Game