The (too) Many Faces of Architecture
summary
Argues that architecture equals the significant decisions measured by cost of change and that organizational shape follows Conway's law, so improving communication fixes many architectural problems. Recommends concrete practices: architectural unit tests, code reviews, pair programming, quality gates and short architectural katas to train developers. Claims architects must combine leadership and wide expertise, stay involved in code, and that every developer is responsible for how architecture evolves rather than leaving it to a single role.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:03Toxic technical mindset traps
- 2:50Conway's Law and team structure
- 5:17Software architecture misconceptions
- 6:21Architecture with Grady Booch’s insight
- 7:24Layers of change in design
- 9:31Why developers need architecture knowledge
- 10:13Role of the architect
- 12:41Leadership in architecture
- 14:28Architects adapt like Darwin’s theory
- 16:56Developer and architect collaboration
- 18:41Shared responsibility in evolution
- 20:07Architects close to code
- 21:55Architectural challenges for teams
- 22:58Challenging stereotypes
- 23:41Call to action
- 24:48Q&A
related talks
24mThe (too) Many Faces of Architecture
46mTHE too MANY FACES OF ARCHITECTURE
49mWhy software architects fail: and what to do about it
48mArchitecture: The Stuff That's Hard to Change
45mConway's Law: when best practices aren't enough
45mTeam and Software: Making an Impact as an Architect
51mSoftware Architecture for Humans!
51mWhy We Need Architects (and Architecture) on Agile Projects