I'm increasingly persuaded that the best kind of architecture diagrams are ASCII text art. It seems to be the only format that others will edit.
I keep seeing an antipattern where someone draws a comprehensive diagram and it keeps getting used even as it becomes less accurate.
miniblog.
Related Posts
Has the JS ecosystem reached a point where people agree roughly what a good architecture looks like?
I don't see as many blog posts complaining about new framework churn and I'm wondering why.
What software designs require clean slate 'revolution' implementations, rather than evolution?
I can think of: borrow checking in a PL (existing code is unsafe), microkernels (architecture is too different from monokernels), and full REPLs (can't add type redefinition later).
I've heard the term 'mechanical sympathy' for the ability to write efficient code due to understanding how a CPU works.
Is there a legacy software equivalent? 'Architecture sympathy', where you've worked out the structure that the author intended and things begin to make sense?