Hacking Your Emotional API
summary
Models emotions as an HTTP-like emotional API with hardwired core endpoints and life-built middleware that can be refactored; shows a concrete example where losing a job triggers 100 calls to fear and 20 calls to sadness. Offers an actionable toolbox: naming feelings, a rubber‑duck aloud exercise, a feeling wheel, weekly emotional retros, and escalating group practices. Cites studies: suppression intensifies reactions, training improves behavior, grades and long‑term health, and individual feelings usually peak around 20 minutes.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 1:11Welcome
- 1:56Why
- 3:30The Emotional API
- 5:12The Metaphor
- 6:02The Unpleasant Truth
- 6:39Powerlessness
- 7:08Executive Function
- 7:39Short Term Memory
- 8:12Emotional Hygiene
- 9:47Emotional Intelligence
- 10:44Emotional Toolkit
- 11:38Level 1 Misconceptions
- 12:06Background Job Queue
- 12:54Feeling
- 14:23Emotional Debt
- 14:43Emotions Last 20 Minutes
- 15:18Action Things
- 15:32Rubber Duck Debugging
- 16:21Talking About Feelings
- 16:43Rubber Duck
- 17:22Feel Wheel
- 17:58Talking Through a Feeling
- 18:45Working With Others
- 19:22Mailing List
- 19:40Summary
- 19:59Soft Skills
- 20:23Next Steps
- 21:31Relationships All Start With You
- 22:00Thank You
related talks
45mHacking Your Emotional API
38mYour Emotional API
27mYour Emotions Are Not an Anti-Pattern
37mProgramming Empathy: Emotional State Machines
27mYour emotions are not an anti-pattern
23mMental Health for Developers
34mDevEmoOps: An emotionally integrated approach to the software development lifecycle
45mDeveloping Resilience