Why is this so hard: The cognitive and coordinative work of software development
summary
Argues that most software effort is hidden cognitive and coordinative work, backed by eight years of engineer studies plus forty years of cognitive systems research, and identifies five capabilities—recognize subtle signals, revise mental models, replan, reconfigure resources, and review—used during real outages (Crowdstrike, AWS, Cloudflare, GCP). Recommends concrete fixes: improved observability, decision‑support interfaces, simulations and game days, pair programming, and debriefs using the Etsy debriefing facilitation guide and the How We Got Here investigation guide to reduce error and burnout.
AI-written summary · about
chapters (19)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 0:24Introduction: Why Software Work Matters More Than We Think
- 2:20Software in High-Stakes Systems and the Real-World Consequences of Failure
- 5:00Why This Talk Is Also About Making Work Better for Developers
- 7:05What Cognitive and Coordinative Work Really Mean
- 10:00The Sociotechnical System Around Every Software Team
- 12:40Complexity, Competing Pressures, and Why Modern Work Feels So Hard
- 15:05Resilience, Adaptation, and Hidden Human Effort in Everyday Engineering
- 17:20Five Core Capabilities for Handling Complexity and Change
- 18:30Recognizing Subtle Changes and Why Noticing Problems Is So Difficult
- 21:10Expectations, Surprises, and the Need for Better Signal Detection
- 24:00Revising Mental Models in Real Time
- 26:10Why Knowledge of Complex Systems Is Always Incomplete
- 28:00Replanning, Goal Conflicts, and Trade-Offs Under Pressure
- 30:20Reconfiguring Teams, Resources, and Expertise During Incidents
- 32:10Smooth Coordination, Dynamic Reconfiguration, and Relaxing Constraints
- 34:20Learning Loops, Debriefs, and Reviewing How Work Actually Happens
- 36:00Practical Interventions: Cognitive Ergonomics for Software Teams
- 38:00Final Takeaways: Making Software Work More Resilient and More Human
related talks
47mThe Psychology of Software Teams
32mThe Cognitive Load Crisis: How Modern Web Systems Burn Out Teams
44mBehavioral Software Engineering
42mThe Future of Software Development
38mFallacies of Software Development
34mWhy Good Software Goes Bad
50mTactics and strategies on software development: how to reach ...
43mBetter Software Development Systems through Stress