A Defence of Technical Excellence
summary
Argues that internal quality drives a reinforcing loop of confusion, bugs and slowed delivery, and models that loop with causal loop diagrams using the browser tool Loopy. Recommends concrete practices—event storming, test‑driven development, living docs, residuality theory—and builds a lightweight glossary tool called contextive. Cites empirical signals: DORA finds AI amplifies existing strengths or dysfunctions, and a study shows AI-assisted issues take 19% longer despite developers expecting ~24% speedup. Practical claim: invest in practices that preserve team-held theory to stop decay.
AI-written summary · about
chapters (16)
- 0:00Technical excellence defense
- 4:42Intuition pumps and iron triangle
- 9:17Systems thinking and diagrams
- 16:00Organizational complexity feedback
- 21:17Technical debt vs confusion
- 26:16Defending excellence theory
- 29:06Eventstorming domain understanding
- 30:51Resilient architecture theory
- 34:42Lightweight documentation
- 37:50TDD and code theory
- 38:32Observability runtime theory
- 40:15Feedback leverage points
- 42:41AI tools programming limits
- 46:30LLM ethical considerations
- 49:38Key takeaways
- 50:19Allyship and closing
related talks
41mA Defence of Technical Excellence
27mTechnical Excellence: Why does it not stick even now?
45mDeveloper Joy – How great teams get s%*t done
47mValue: Why we have it Backwards
36mEngineering Intent: Solving the AI Productivity Paradox
46mThe Case for Technical Excellence
14mSmarter #Testing for Better Speed & #Quality with DORA Metrics
27m'The Art of Software Development'