cards42.org
Cards for Analyzing and Reflecting on Doomed Software
Paths not taken
Every day, decisions are taken that often have a long-term impact on our software system. Each of these decisions is based on several alternatives, of which, however, only one can ever be selected as a solution approach. The selected solution is usually described in an architecture documentation and is therefore comprehensible. But what about the alternatives, which have also been considered but were not chosen? These should also be documented so that the decisions made can be understood in the long term.
Now, think about which paths you deliberately did not follow in your software. Write them down on the card and describe the reasons for the rejection of the individual alternative.
More information
- Michel Keeling lists “Paths not taken” as one of dozens of activities in his marvelous book Design It!
- Introductory page for the topic ADR
- Initial presentation of the idea of ADRs