[minhmeoke]

Very cool, thank you! Creating diagrams using code rather than using drag-and-drop tools might be a good idea for more complex architectures as described here: https://www.ilograph.com/blog/posts/its-time-to-drop-drag-an...

- Can check the textual description of the diagram into version control and track how it changes over time

- Can easily diff 2 versions of the same diagram

- Adding elements to a large existing diagram using WYSIWYG tools can be tricky (eg: you may have to move or reroute existing elements to make enough space)

Another cool idea is to create multiperspective diagrams with different views for different purposes (eg: code structure, deployment, network architecture, security):

- Clarity. By breaking up diagrams into perspectives, diagram authors can bring much more clarity to a system. Individual concerns can be spread out over many perspectives, allowing each the space it needs without interfering with others.

- Extensibility. Multiperspective diagrams share a model, so creating additional perspectives from an existing diagram is incredibly easy, far easier than starting from scratch each time.

- Maintainability. A corollary to the above, individual perspectives can be modified without affecting the others. Diagrams that are easy to maintain get maintained, while diagrams that aren’t fall out of date quickly. Multiperspective diagrams greatly help in the fight to keep documentation up-to-date.

This is a cool demo: https://app.ilograph.com/demo.ilograph.Stack%2520Overflow%25...

For other textual diagramming tools and ideas, please see this thread: https://news.ycombinator.com/item?id=37222855

Disclaimer: I'm not affiliated with Ilograph, just stumbled onto their blog and I think they have a lot of cool ideas.