Democratising Software Architecture
summary
Argues for Continuous Architecture where architecture work happens every sprint and decisions as first-class artifacts (use ADRs or a searchable wiki), not big up‑front blueprints. Recommends five concrete practices: provide technical leadership, focus on quality attributes, drive architectural decisions, manage technical debt, and implement feedback loops. Shows platform examples — Google Maps and Cushion — where building a platform (not a single app) enables pivots and continued evolution, and reports that this approach actually reduces late‑stage rework.
AI-written summary · about
chapters (11)
- 0:00The evolution of software
- 2:20Defining modern platforms
- 5:56Architectural shifts
- 8:17Architectural overload
- 11:27Continuous architecture
- 14:47Principles for agility
- 19:36Decisions as artifacts
- 23:57Styles and patterns
- 28:36Documentation standards
- 33:01Five pillars of practice
- 41:31Conclusion
related talks
38mPractices for Effective Continuous Software Architecture
45mFive things every developer should know about software architecture
37mArchitecting for Tomorrow: A Pragmatic Perspective
38mAgile Architecture
45mFive things every developer should know about software architecture
45mArchitecture and the Architect AD2022
48mDown the Ivory Tower towards Agile Architecture
49mCultivating Architecture