One Does Not Simply Make Architecture Decisions Alone: ADRs and Architec
summary
Claims that architecture is literally a set of decisions and that writing them down reduces bias, with the startling anchor 35,000 decisions a day. Shows an ADR template (metadata, context, options, consequences), walks a real choice between React, Vue, Svelte where React chosen because design system supports it, and runs an advice process: weekly 30–60 minute meetings to gather actionable advice. Demonstrates ADRs feeding coding agents (VS Code + GitHub Copilot via MCP) so agents follow ADRs like using AWS AppConfig feature flags.
AI-written summary · about
chapters (12)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 0:30Introduction: We Make 35,000 Decisions a Day
- 3:00What is Architecture? Decisions Over Diagrams
- 6:10Thinking Fast vs Slow: Bias in Decision-Making
- 9:20Why Writing Improves Decisions
- 12:00What is an ADR? Structure & Key Components
- 16:30Example: Choosing a Frontend Framework
- 22:00Seeking Advice: Revealing Blind Spots
- 26:00Architecture Decision Models (Dictator vs Collaborative)
- 29:30Architecture Advice Process Explained
- 32:00ADRs + AI: Giving Context to Coding Agents
- 34:00Final Takeaways: Better Decisions Together
related talks
42mIntroduction to ADRs
47mMaking architecture decisions, the Agile Way
43mGetting Started with Architectural Decision Records
39mA commune in the ivory tower: A new approach to architecture
45mArchitecture and the Architect AD2022
46mCreating Effective and Objective Architectural Decision Records (ADRs)
27mJudging ‘It’s About Balance’ — The Path to Technical Excellence Through ADR Practice
43mWorking Efficiently with Architecture Decision Records (ADRs)