ADRs: Because Context Isn't Just for LLMs
summary
Demo builds a chore‑tracking web app to force concrete choices and then records them as ADRs, shows builds a chore-tracking web app, explains the Nygard template and shows ADR CLI commands with exact init/new/supersede syntax, and lists concrete consequences like documents trade-offs like Postgres vs MySQL and a Windows incompatibility for one CLI. Recommends storing ADRs in the repo, keeping entries short, and using AI only to assist not replace human trade‑off reasoning.
AI-written summary · about
chapters (10)
- 0:00Chore tracking project
- 3:44Software choices by context
- 5:57What are ADRs
- 8:27ADR components
- 10:57ADRs with CLI tools
- 13:29ADRs benefits
- 15:35Documenting decisions best practices
- 17:41Trade-offs in decisions
- 18:44Resources for architecture
- 19:26Closing
related talks
42mIntroduction to ADRs
43mGetting Started with Architectural Decision Records
54mHow'd we get here? A guide to Architectural Decision Records
37mArchitecture Decision Records - How not to get lost in the past
14mArchitecture Decision Records: Make Peace with Your Docs
43mWorking Efficiently with Architecture Decision Records (ADRs)
15mCreating effective and objective architectural decision records (ADRs)
13mBDD, ADR, PRD, WTF: Capturing Decisions for Humans and AI Alike