|
|
|
|
|
by LanternLight83
1402 days ago
|
|
Absolutely! UML gets a lot of discussion, but a more reflective model of a written program is something I long for. I love the feedback that I get from, say, writing a Tupfile and running `tup graph` to see an actual graph of all my recipes, complete with their commands, inputs, outputs, and interdependencies as understood by the build system. I haven't used Unity, but it looks like it has blender-like node-based programming that gives me the same feel, where each box ia just code but the connections between them are illustrated. Lastly, Emacs allows you to instrument function definitions with edebug, and stepping through the code or even just letting it run in a loop and observing the movement of the point-of-execution has given me a lot insight into packages that I've worked on. None of this is really "the thing", but each example gives me the same vibes, of showing how existing code or control flows are structured. |
|