Practices from trenches for embracing evolutionary architecture in wild
summary
Shows concrete practices: codify a decision matrix (fast vs slow) and FAQ, embed architecture-as-code and ADR templates into pull requests, and convert variances to failed CI tests so deviations are tracked automatically. Creates working groups whose members allocate 30% time to coaching, pairing and tooling, runs demo/showcase and challenger sessions, and enforces constraints like shelf‑life (e.g., 1–3 years) to force tradeoffs. Reports a migration outcome where platform tooling made decisions enforceable and reversible in practice.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:25Viveks background
- 2:20Questions
- 3:36Key message
- 5:23Content
- 6:14Define Trench
- 7:48Radically New
- 8:06Principles
- 9:38Continuous learning
- 10:30Continuous feedback
- 11:34Design for inclusion
- 13:00Design for understandability
- 14:10Slow and fast thinking
- 18:57Going slow
- 20:55Constraints
- 23:03Engagement
- 25:30Cheap decisions
- 27:56What is architecture
- 37:00Question
related talks
49mCultivating Architecture
48mDown the Ivory Tower towards Agile Architecture
01h 03mEvolutionary Software Architectures
38mAgile Architecture
01h 00mEvolutionary Architectures
42mBuilding Evolutionary Architectures: Principles and Practices
35mPrinciples of Evolutionary Architecture
39mPrinciples of Evolutionary Architecture