I could imagine something like this but for software/infrastructure architecture, where it would impose a formality/standard of language that would be useful for exchanging ideas, especially in earlier stages of remote collaboration.
This also works really well with the box/tree description I give to people who are new to computer science or systems administration, and looking to understand more. Basically, it's useful to think of stuff in computers as both a series of boxes within each other, and as a tree with a base and branches. Folders start with a big box that contains smaller boxes as you `cd` into other folders, but they're also a tree because you start at the root and travel along branches as you cd.
I wonder if something like this can be used to model the structure of technical documentation and therefore test its validity.
Reminds me of Gay Deceiver's organization system from The Number of the Beast - I've always wanted to implement something like that, but I lacked the skill when I had the time, and now (maybe) have the skill but (certainly) lack the time. Well done!
This looks interesting. Might be worth looking at older systems like pic and graphviz for inspiration. One gripe if the author is here: the chosen font and colors are near unreadable. Thank heavens for reader mode.
Hmm, I tried to post a comment earlier: did comments get erased from here? Anyway, this looks neat, and it might be worth looking at older drawing tools like Pic and GraphViz for inspiration.
I could imagine something like this but for software/infrastructure architecture, where it would impose a formality/standard of language that would be useful for exchanging ideas, especially in earlier stages of remote collaboration.
This also works really well with the box/tree description I give to people who are new to computer science or systems administration, and looking to understand more. Basically, it's useful to think of stuff in computers as both a series of boxes within each other, and as a tree with a base and branches. Folders start with a big box that contains smaller boxes as you `cd` into other folders, but they're also a tree because you start at the root and travel along branches as you cd.
I wonder if something like this can be used to model the structure of technical documentation and therefore test its validity.