We need visual programming. No, not like that.

Visual programming often fails because it attempts to replace code syntax, which developers already handle well with textual representations. Success would be more likely if it focused on aspects developers already visualize, such as state transitions, memory layouts, and network requests. Effective code visualizations are essential but often ad-hoc and not integrated into standard workflows, unlike tools such as DOM element inspectors and flamegraphs in profilers.