DevEmoOps: An emotionally integrated approach to the software development lifecycle
summary
Argues that software delivery omits engineers’ emotions and offers a concrete practice set from six years of field research: use resilience and cognitive systems engineering to identify boundary conditions, measure signals like missed keys or forgotten meetings, and share adaptive capacity by reassigning people during outages (example: an on‑call manager recruits a senior engineer to unblock a weekend incident). Recommends explicit tactics—relax goals, defer or delegate work early, and enable dynamic reconfiguration across teams and vendors—to avoid collapse and sustain graceful degradation.
AI-written summary · about
chapters (9)
- 0:00DevEmoOps introduction
- 3:24Emotional stress and cognitive systems
- 9:23Building systems that make it okay to not be okay
- 13:15Personal stress boundaries
- 20:40Recognizing saturation
- 23:50Maladaptive patterns
- 24:55Sharing team capacity
- 30:49Dynamic reconfiguration
- 32:34Summary and call to action
related talks
18mCombining DevOps and Emotional Intelligence
05mSoftware Development as an Emotional System
19mEmotional Intelligence for Engineers
28mOne weird trick to becoming a better software developer
27mYour Emotions Are Not an Anti-Pattern
37mProgramming Empathy: Emotional State Machines
40mDev (depresiya) Ops
13mLeading with empathy: Turning good developers into great engineers