Architectural Decision Records (ADRs) are the key to documenting crucial decisions, enhancing team alignment. Learn the essentials of ADRs, including practical tips for creating clear, concise records
ADRs were a great addition to our codebase. We also use them to link relevant resources related to the accepted proposal/decision so new colleagues can go through them.
Appreciate the ADR topic, Fran. One thing that would be nice to touch on too is comparing to other terms, like RFC, 1-Pager, Technical Design Document, PRD, etc.
I feel like sometimes they get used interchangeably but they aren't actually.
Also, thanks for shouting out the recent High Growth Engineer article!
ADRs were a great addition to our codebase. We also use them to link relevant resources related to the accepted proposal/decision so new colleagues can go through them.
It's a much easier way to document than relying on people discovering by themselves!
The true power of ADRs lies not in the decision itself but in the reasoning behind it. It’s not just about what we choose, but why.
Exactly!
People can find what you chose just by looking at the code, but they won't find why you chose it unless you have it written somewhere
Appreciate the ADR topic, Fran. One thing that would be nice to touch on too is comparing to other terms, like RFC, 1-Pager, Technical Design Document, PRD, etc.
I feel like sometimes they get used interchangeably but they aren't actually.
Also, thanks for shouting out the recent High Growth Engineer article!
nice topic selection and thanks for sharing your ADR template - Fran.