Topic
Architecture documentation
Why architecture diagrams go stale, what that costs, and the practices and tools that keep diagrams and documentation matched to the running system.
All posts
Latest writing
- The C4 model in practiceSeparate system context from container detail, use a copyable YAML example, and review the diagram for responsibilities the schema cannot check.Architecture documentation
5 min read - ERDs and sequence diagrams as codeCopy valid YAML for typed entities and an ordered login exchange, then review the schema and failure paths that syntax alone cannot verify.Architecture documentation
5 min read - Forking Excalidraw for structured diagramsHow structured ERD and API cards share geometry across editing and export, and why sequence diagrams use a separate element.Architecture documentation
4 min read - Why I built ArchDocsI wanted shared services to keep their identity across architecture diagrams, with YAML and a canvas editing the same document.Architecture documentation
4 min read - The real cost of stale documentationStale architecture docs never appear as a line item, yet they slow onboarding and incident response. A framework for naming that cost.Architecture documentation
9 min read - Your architecture diagrams are lying to youArchitecture diagrams go stale the moment they are drawn. Here is why they drift, the three ways they fail, and what actually keeps them honest.Architecture documentation
9 min read
Start
Try what we write about
No credit card required