|
|
|
|
|
by nyrikki
232 days ago
|
|
While I fully support your efforts to make better tooling, UML is the poster child for this. I highly encourage people working in this space to revisit those lessons. Obviously if you find a new way to work around the limitations please run with it. But limited scope, and targeted simplifications is the only way I have found, over application by trying to describe everything almost always ends up being more harmful in my experience. |
|
UML was made as a specification-through-visuals tool and I'm aiming at diagrams-as-communication tool. I.e. sure you can save them, but the use case I aim is that you hop on the video call, share screen and discuss specific concept with one of the diagram types.
Collaboration is a huge part of it, but since I've never seen my concept in realization I'm going to keep it hush-hush for a while :)