David Farley Interview
summary
Argues for continuous architecture to match continuous delivery and testing, claiming current systems are often big balls of mud with tight coupling that hinders change. Skeptical of manifestos but supportive of debating concrete models and practices, pushes for ongoing experiments to improve techniques. Emphasizes measuring success by ability to deliver value to organizations, not architectural purity, and calls for practical steps to tease systems apart, validate approaches, and evolve better design habits.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 0:27Why did you decide to come
- 0:55What are your thoughts on the manifesto
- 1:14What are your thoughts on the current state of software architecture
- 2:00What are the biggest challenges in software architecture
related talks
45mDemocratising Software Architecture
38mPractices for Effective Continuous Software Architecture
44mDeliberate Architecture
58mThe past, present and future of Architecture
37mArchitecting for Tomorrow: A Pragmatic Perspective
50mTowards an Evolutionary Architecture
38mAgile Architecture
25mThe (too) Many Faces of Architecture