Écrivez l'architecture avant d'écrire le code
Une page de prose coûte un après-midi et règle les débats qui se régleraient sinon dans une pull request trois semaines plus tard.
Brouillon. Cet article accompagne la section Articles comme gabarit de mise en page, et il est exclu de la recherche et de l'assistant du site tant qu'il ne porte pas un vrai texte.
Cet article est publié en anglais. Le reste du site est traduit, pas les articles, parce qu'un raisonnement technique traduit automatiquement vaut moins que le même lu dans la langue où il a été écrit.
The argument against writing the design down is always speed. It is a bad argument, because the alternative is not "start sooner"; it is "discover the disagreement later, in code, when reversing it is expensive".
What the document is for
Not the diagram. The diagram is the easy half and the half that gets shown. The useful part is the paragraph under it explaining which parts genuinely need a model and which parts are better off deterministic, because that is the decision the whole system is downstream of.
What it is not for
It is not a specification to be followed to the letter, and treating it as one produces the padding that a technical reader notices immediately. It is a record of what was decided and why, so the next person, who is often you, can tell the difference between a considered choice and an accident.
This post is a placeholder shipped with the writing section. Replace the body with the real piece; the frontmatter above is the only thing the site reads.