Thinking Architecturally
summary
Explains how to weigh trade-offs with concrete rules: require a business problem and measurable payoff before adopting tech, avoid hoisting Kafka for 40,000 users as an example of premature scale, stop projects accumulating four UI frameworks, and record choices with lightweight decision logs so consequences become visible. Recommends using fitness functions to check that architecture goals are enforced in code, carving regular 15–30 minute “morning coffee” learning slots, and treating experiments as deliberate trials.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:13Architecture is people
- 6:43Evaluating new tech
- 11:39Legacy skills and patterns
- 15:11Avoiding new tech
- 18:19Commitment and mastery
- 21:52Strategic tech adoption
- 23:33Learning into routine
- 24:57Conclusion
related talks
43mThinking Architecturally
28mThe lean architect: Experimenting your way to better decisions
41mArchitecture decision making
56mEssential Architectural Thinking – Why, What, How, When and How Much?
59mHow to Think Like an Architect
46mPractical (a.k.a. Actually Useful) Architecture
47mMaking architecture decisions, the Agile Way
56mTowards an Evolutionary Architecture