Software Development as an Emotional System
summary
Claim: software development functions as an emotional system where anxiety is inevitable and grows in groups, driving short-term compromises that break long-term goals. The actual product to manage is the development lifecycle and team interactions, not just code; treat team processes like code by measuring churn, missed milestones and defect spikes, then refactor them. Key practices: resist the siren song of the quick fix and adopt systems thinking so an emotional system can be refactored to reduce rot.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:24Emotions are not feelings
- 0:44Groups are emotions
- 1:04Software development is an emotional system
- 1:36Anxiety is inevitable
- 1:58Quick fixes
- 3:14What we actually create
- 4:05Conclusion
related talks
34mDevEmoOps: An emotionally integrated approach to the software development lifecycle
47mThe Psychology of Software Teams
18mCombining DevOps and Emotional Intelligence
44mThe socio technical developer
28mOne weird trick to becoming a better software developer
23mMental Health for Developers
52mYour Brain on Software Development
19mEmotional Intelligence for Engineers