I’m very skeptical of “visualization” as a technique for understanding branching narratives (or code).
Visual aids can only really represent a few dozen things before they become as complicated as the thing you were trying to understand in the first place.
And when analyzing messy node diagrams, it’s not just the nodes we’re trying to visualize, but the lines connecting the nodes (the “edges”). We can only visualize a few dozen of those, and that typically means we can visualize only a handful of nodes at a time.
Visualization only works in trivial examples where you don’t need it; it fails in complex environments where you need it the most.
Instead, I claim that you want automated tests.
- Are there no more sections marked “TODO” here?
- Ensure that there’s a path from X to Y
- Ensure that there’s no path from X to Y
- Ensure that all the paths from X to Y meet certain criteria:
- All paths from X to Y pass through Z
- You can’t get from X to Y unless certain variables are high enough