The pragmatist’s guide to low-stress architecture diagrams
There's a hurdle that makes working with software architecture diagrams harder than it first seems.
Whether it's a formal system, such as UML, or something you make up on the fly, every software architecture diagram relies on standards. That leaves you with a choice to make.
Why create software architecture diagrams?
There are three core reasons why architecture diagrams make sense for even moderately sized codebases:
* Coherent vision: they provide a clear statement of direction and of decisions made
* Collaboration: they make it easier to onboard new developers and to work across different parts of a large codebase
* Outward communication: they&