The too many faces of Architecture
summary
Claims that software architecture becomes workable when teams treat it as an evolving, shared responsibility and when architects periodically touch the codebase; recommends concrete practices like code reviews, pair programming and peer architecting, and running small proofs of concept to validate choices. Argues architecture decisions matter more than design ones for scalability and cost, shows how occasional coding or targeted reviews surface realistic tradeoffs, and frames evolution over rigid upfront specs.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:13Architecture beyond technical
- 2:55Defining architecture
- 6:07Architectural decisions
- 7:30Developer perspective
- 9:15Architecture myths
- 9:58Who is an architect
- 13:28Collaboration and expertise
- 15:52Soft skills in architecture
- 17:20Becoming an architect
- 18:21Architecture for developers
- 20:46Shared architecture responsibility
- 21:08Architects close to code
- 23:13Final thoughts
related talks
40mThe (too) many faces of architecture
01h 09mAgile Software Architecture
41mArchitecture and Agility: A Shared Skillset!
45mSoftware Architecture for Humans!
45mArchitecture: The Stuff That's Hard to Change
50mCoevolution of Architecture & Code - Closing The Gap
33mSet Design: Putting the "Art" in "Architecture"
50mTowards an Evolutionary Architecture