Thinking Architecturally
summary
Argument: decide technologies by proving trade-offs not by hype. Use a lightweight architectural briefing, run a hands‑on POC inside your repo constraints, then trial on a safe real project; measure the hard things you care about (upgrade effort, testing, perf, security). Practice rotate repair repave for patching and track versions (policy: current major or -1). Rely on a curated technology radar and 20%‑style time, and favor tools you can both add and clearly remove.
AI-written summary · about
chapters (15)
- 0:00The architect's journey
- 1:57Avoiding the hype cycle
- 3:20Strategic technology adoption
- 5:29Cultivating expertise
- 8:45Patterns and hype cycles
- 10:36Learning through experimentation
- 13:13Strategic project management
- 15:02Managing time and focus
- 18:16The value of attention
- 21:49Humility in engineering
- 24:18Specialized generalists
- 27:39Structured evaluation
- 30:23Practical proof-of-concepts
- 33:16Security and self-care
- 35:47Making informed trade-offs
related talks
25mThinking Architecturally
49mCultivating Architecture
46mArchitecture Transformation Challenges
28mThe lean architect: Experimenting your way to better decisions
59mHow to Think Like an Architect
37mArchitecting for Tomorrow: A Pragmatic Perspective
44mDeliberate Architecture
56mTowards an Evolutionary Architecture