I kno you're not suggesting the visual system would drive coding at all or that it'd be a way to visually code (see: scratch). You seem to mean it as a visualization of the current code base. I'm hoping Google's code wiki is the first step in this direction. One thing I always thought was a problem with visual systems like this was understanding the codebase's architectural design at a level yu can't programmatically get out via a syntax tree analysis. Google's code wiki seems to be using an LLM to figure out the high-level structure of the code and then building the flowchart and diagrams from that understanding. Obviously there's gonna be issues and misunderstanding but I think that's the first step in the direction you're talking about. First it's text, mermaid diagrams and 2d. Next it's a 3d visual world of your codebase. AWESOME stuff. Someone @ Google.