3 ms·
I would actually be really interested in a bi-directional workflow, such that I would also be able to perform system redesign by changing the diagram's connecti
by falcor84 3y ago
I would actually be really interested in a bi-directional workflow, such that I would also be able to perform system redesign by changing the diagram's connections - the tooling will then automatically update the interface and the tests such that I wouldn't be able to commit my changes until the implementation matches the diagram.
- Sophistifunk 3y agoIMO the source code to aspects of the system that are best shown as graphs should be the graphs.
- jakewins 3y agoI realize this isn’t what you’re arguing for, but as a cautionary anecdote on this topic: Paul alludes to it in his post about Healthcare.gov from the other day, but this was apparently one of the major parts of the failure there - endless lines of code generated from UML diagrams, making reading the code hard and things like “can we add a trace statement here” difficult. Optimising for diagrams-as-source-of-truth has drawbacks for debugging and maintainability of the running code https://www.pauladamsmith.com/blog/2023/10/the-10-year-anniversary-of-the-healthcare.gov-rescue.html https://www.pauladamsmith.com/blog/2023/10/the-10-year-anniv...