The Dark Gods of Enterprise Architecture. To Warp and Back
summary
Examines why different approaches to corporate software architecture—formal design documents, ad-hoc team-driven designs, and sprint-based changes—nonetheless produce the same severe implementation problems (technical debt, failing projects). Uses examples from enterprise architecture practices to show how well-intentioned designs and short-term development cycles turn into long-lived, hard-to-fix failures and implementation ‘demons.’
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:57Dark gods origin
- 6:14Security god rituals
- 9:53Order god documents
- 11:20Perfection god idealism
- 13:57Emperor's arbitrariness
- 16:10Fighting the gods
- 18:59Q&A
- 26:26Solutions and compromises
- 31:09Corporate architect role
- 34:09Psychotherapy instead
- 36:18Conclusion
related talks
40mDark Gods of Enterprise Architecture: Tales from the Warp's Depths
43mModern Enterprise Architecture: architecting for outcomes "Modern Enterprise A..."
01h 48mCharting a Course Through Enterprise Architecture
38mModern Enterprise Architecture: Architecting for Outcomes
57mSoftware Architecture: The Hard Parts
33mDecoding Complexity:[...]
49mWhy software architects fail: and what to do about it
46mArchitecture Transformation Challenges