Six months later nobody remembers why: Reddit debate on architecture decision records
djgoel123 · reddit · 2026-10-29
A Reddit discussion on architecture decision records resonated with engineers: teams make database, queue, or service-boundary decisions that make sense at the time, but six months later the constraints have changed, new hires have joined, and nobody remembers the original reasoning — so stale assumptions get treated as permanent requirements.
The author's take:
- Not every decision needs a long document, but decisions with significant tradeoffs deserve a short record of context, alternatives, and reasoning
- Otherwise old assumptions harden into permanent-looking requirements
The author asks engineering leaders whether they use ADRs or something simpler, and whether they've ever reversed a technical decision after finding its original justification no longer applied.
More from coding & agent
- Routing coding agents' questions by decision type: 762 questions, only 59 needed the owner — DynoKore · 2026-10-29
- 1.2B tokens later: multi-agent coding run rebuilds a 3D game but hits diminishing returns — teortaxesTex · 2026-10-29
- Unreal Engine runs in the browser via a single Claude agent prompt — chongdashu · 2026-10-29
- Evals and Tracing 101: A Practical Guide for Engineers Building With AI — blaizedsouza · 2026-10-29
- Stop repeating yourself to every AI: a 4-step fix for syncing memory across Claude, ChatGPT and personal agents — jonathanmalkin · 2026-10-29
- hunch: GPU-free ~20ms Jev-like decisions built on EmbeddingGemma 2 — iamrobotbear · 2026-10-29