No, you're not dense at all: Thank you so much for the feedback. It's more that when you're fish you're like "what do you mean 'water'?"
Point taken that I need to change my materials ASAP.
In my world, ADRs = Architectural DELIBERATION Records, and the emphasis is on being dense and on capturing the process over (or rather in addition to) the outcome. From complexity theory, we know that process is more generative than state.
An ADR, as Architectural DECISION Record, is a practice predating but popularized by Michael Nygard in early 2010s. It focuses on writing down the reason (and other options considered) for important decisions.
My framework is inspired, but different in a few respects but including:
- it's optimized for iteration, multi-party communication;
- the records are intentionally much more dense and verbose: They consider that what was non-obvious and deliberated carefully is as interesting as the final call;
- there is an emphasis on deep-linking the records and referencing questions, sections in code and across records.
Thanks for your attention, and I am going to make changes to the website so that the acronym is spelled out at least once!
Point taken that I need to change my materials ASAP.
In my world, ADRs = Architectural DELIBERATION Records, and the emphasis is on being dense and on capturing the process over (or rather in addition to) the outcome. From complexity theory, we know that process is more generative than state.
An ADR, as Architectural DECISION Record, is a practice predating but popularized by Michael Nygard in early 2010s. It focuses on writing down the reason (and other options considered) for important decisions.
My framework is inspired, but different in a few respects but including: - it's optimized for iteration, multi-party communication; - the records are intentionally much more dense and verbose: They consider that what was non-obvious and deliberated carefully is as interesting as the final call; - there is an emphasis on deep-linking the records and referencing questions, sections in code and across records.
Thanks for your attention, and I am going to make changes to the website so that the acronym is spelled out at least once!