“Why did we decide this?” – every developer in history, 12 months after making a decision.
As technologists, we make architectural decisions all of the time. What we’re not good at doing is:
Enter ADRs. First proposed by Michael Nygard, Architectural Decision Records provide a way to capture these decisions as part of the codebase that you’re working on; where the rubber meets the road.
In this five minute ignite talk, we’ll go through the case for ADRs and a simple primer and how to get started using this technique in your projects.