Skip to main content

#architecture

Log entries with this tag, newest first.

  1. Decision recordMulti-tenant platforms

    One repository, several solutions

    Splitting a product line into repositories is a permissions decision wearing an architecture costume. Azure Repos permissions stop at the repository, so if nobody has to be kept from reading part of the code, one repository with several solution files keeps the compile-time safety that packages trade for version drift. The decision record, the reference matrix, and the test that holds it.

    9 min read

  2. Decision recordEngineering systems

    Pre-MVP: make it right, never comply

    Before the first release there is nothing to stay compatible with. Code that adapts to older code, an older schema or stale development data is a defect, not a kindness. The rule, how it was found, where it has held and where it is shaping decisions not yet built, and the day it should end.

    6 min read