diff options
Diffstat (limited to 'topics/engineering')
| -rw-r--r-- | topics/engineering/using-architecture-decision-records-in-genenetwork.gmi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/topics/engineering/using-architecture-decision-records-in-genenetwork.gmi b/topics/engineering/using-architecture-decision-records-in-genenetwork.gmi index c88398b..34a9777 100644 --- a/topics/engineering/using-architecture-decision-records-in-genenetwork.gmi +++ b/topics/engineering/using-architecture-decision-records-in-genenetwork.gmi @@ -3,7 +3,7 @@ * author: bonfacem * reviewed-by: fredm -> One of the hardest things to track during the life of a project is the motivation behind certain decisions. A new person coming on to a project my be perplexed, baffled, delighted, or infuriated by some past decision. +> One of the hardest things to track during the life of a project is the motivation behind certain decisions. A new person coming on to a project may be perplexed, baffled, delighted, or infuriated by some past decision. > -- Michael Nygard When building or maintaining software, there's often moments when we ask, "What were they thinking?" This happens when we are trying to figure out why something was done a certain way, leading to speculation, humor, or criticism[0]. Given the constraints we face when writing code, it's important to make sure that important decisions are well-documented and transparent. Architecture Decision Records (ADRs) are one such tool. They provide a structured way to capture the reasoning behind key decisions. |