Architecture Decision Record
AssessTechniques
A short document that records a single software architecture decision, its context, rationale, and consequences.
Why it's here
Placed in Assess: 2 article(s) of evidence from 1 source(s), led by framework updates, with 0 in the last 30 days. Confidence 38%.
Evidence (2)
- 5Martin Fowler·7/6/2026researchThoughtworks retreat highlights the shift to agentic software development
Martin Fowler reports on Thoughtworks' second Future of Software Development Retreat in Europe, where attendees largely agreed that agentic development is now real and already in production. The discussion has shifted from whether AI agents will change software engineering to how to use them effectively, including harness engineering, token costs, architecture, and the need for better abstractions and mechanical sympathy.
- 3Martin Fowler·3/24/2026framework_updateArchitecture Decision Records
The article explains Architecture Decision Records (ADRs) as short, structured documents for capturing a single architecture decision, its context, rationale, alternatives, and consequences. It recommends keeping ADRs brief, versioned in the code repository, and never editing accepted records; later changes should be documented as superseding decisions.