Isn't this backwards? I read "X as code" as "you can execute X (and observe some result)". But you can't execute these diagrams. What you can do is to "execute" code and observe visual diagrams as a result. So I think this should be "code as diagrams". Or simply "some diagram description languages".
I agree that it is not entirely self explaining. I ended going with Diagram as Code based on the Infrastructure as Code [1] principle which is the same concept; you write code to generate your infrastructure.
3 comments
[ 2.7 ms ] story [ 22.5 ms ] threadhttps://freetxtmind.github.io/
[1] https://en.wikipedia.org/wiki/Infrastructure_as_code