Paved Roads - Architecting for Distributed Teams
summary
Argues for creating paved roads and automated fitness functions so distributed teams make repeatable, measurable decisions: example metrics include cyclomatic complexity limits (author saw a real value of 82), average service-call response targets (e.g., 100 ms), contract tests with Spring Cloud Contract, and chaos tests (Simian Army) to validate resilience. Recommends CI/CD pipelines (Concourse/Jenkins), service isolation for PCI compliance, and simple video “window” links between rooms — all buildable, automated practices that demonstrably improve productivity and reduce risk.
AI-written summary · about
chapters (6)
- 0:00Introduction to distributed teams
- 10:31Remote work realities and benefits
- 22:07Evolutionary architecture and fitness functions
- 37:36Automating pipelines and CI/CD
- 51:14Centers of excellence and expertise sharing
- 59:38Closing and Q&A
related talks
41mCultivating Architecture in an Agile World
48mDown the Ivory Tower towards Agile Architecture
49mCase study of a good enough architecture
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
46mArchitecture & DevOps
57mBuilding Systems that are #neverdone
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
01h 00mAgile Architecture