4 ms·
I disagree especially because statecharts solve this with hierarchical states. You draw and think about a substate on its own, without all the higher-level comp
by sktrdie 9y ago
I disagree especially because statecharts solve this with hierarchical states. You draw and think about a substate on its own, without all the higher-level complexity. Then once ready you can include it in any subsequent layer - hence it’s composable and reusable.
Take a look at the “unclustering” section of the statecharts paper.
- politician 9y agoOnce you get into the realm of drawing lines, grouping things, and imagining flows you're programming. That it's graphical makes no difference. I've tried this approach before: the charts get complex fast, then your designers give up.
- fourthark 9y agoProbably would work better if the visualization is automatically derived from the code, so that it's a guide but it doesn't get in the way.
- diroussel 9y agoYes. I can this a self describing system. When the code or config can be used to generate reference materials, at run time or build time, to make understanding the system easier. Typically you don’t need to refere to these diagrams and outputs very often, but they are useful for: - on boarding new people to the team - deep reasoning when debugging or analysing a problem - putting on the board during a design session