Working Efficiently with Architecture Decision Records (ADRs)
summary
The talk explains using Architecture Decision Records (ADRs) to make documentation practical and useful by recording design decisions and their context. It contrasts ADRs with large centralized wikis, showing how ADRs keep documentation concise, findable, and tied to the codebase to avoid under- or over-documentation.
AI-written summary · about
chapters (10)
- 0:00Introduction to ADRs
- 3:57What are architecture decisions
- 7:50ADR template and structure
- 12:03Example ADR
- 22:11Alternatives and consequences
- 26:01Documenting with AsciiDoc
- 31:57Managing ADRs in microsites
- 36:12Team decisions and transparency
- 39:03ADR benefits in teams
- 40:10Q&A
related talks
14mArchitecture Decision Records: Make Peace with Your Docs
31mLightweight Software Architecture
15mCreating effective and objective architectural decision records (ADRs)
27mJudging ‘It’s About Balance’ — The Path to Technical Excellence Through ADR Practice
54mHow'd we get here? A guide to Architectural Decision Records
46mCreating Effective and Objective Architectural Decision Records (ADRs)
45mArchitecture and the Architect AD2022
42mIntroduction to ADRs