4 ms·
The point is not that we should code using visual tools, but that our code should be visualizable. And for debugging, we write textual pretty printers for data
by vaughan 4y ago
The point is not that we should code using visual tools, but that our code should be visualizable.
And for debugging, we write textual pretty printers for data structures, but wouldn't it be better to have them graphically visualized.
Keep the best of both worlds.
- dtagames 4y agoI don't think so. No list of tables, graphs, lines, boxes, globes, or whatever "visually" improves code and it never really has. That's why none of those products are very successful. It would be great if there were some kind of documentation generator that produces boxes and lines out of real code. Today's tools want you to code AND draw boxes, which is really dumb -- or just draw boxes and hope the code underneath works, which is even worse. There are some exceptions. Synthesizer programming is often done visually. So is programming instruments with LabView. But for general programming, no, visual is not the way.