The (too) Many Faces of Architecture
summary
Claims that Conway's Law drives system structure, that architecture is a set of significant decisions with a measurable layers of change cost, and that misbeliefs (architect as unreachable god or policing gatekeeper) cause repeated rewrites — one team rewrites five times until leadership changes. Advice: architects retain some code contact, run coding katas, pair programming, code reviews, and hand feature ownership to developers. Outcome: collaboration reduces churn and surfaces architectural risks earlier.
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 2:13Why focus on architecture
- 5:05Debunking architecture myths
- 7:14Defining architecture simply
- 9:42Significant decisions in architecture
- 11:48Architecture is not static
- 12:51What is an architect
- 16:05Architect as leader and expert
- 18:41Should every developer be an architect
- 20:46Architects should still code
- 22:52Soft skills and team collaboration
- 23:55Closing and contact
related talks
25mThe (too) Many Faces of Architecture
45mConway's Law: when best practices aren't enough
46mTHE too MANY FACES OF ARCHITECTURE
48mArchitecture: The Stuff That's Hard to Change
49mWhy software architects fail: and what to do about it
01h 02mThrough the Looking Glass
49mCultivating Architecture
45mSoftware Architecture for Humans!