I really like the idea of visualizing code in any other way than text and have given it some thought from time to time. However, I think the problem here can quickly become that you tend to fall in love with a bad idea. No one, and I don't mean that in bad faith, wants to look at these diagrams. Usually they do not communicate the meaning they intend to do, and I find that I have to spend some time understanding what exactly is meant by any type of box or arrow.
What people might want to look at is their mental visualization of the code or math they are working on (or their LLM made for them). At least to me, that is much more tied to what the data will look like at runtime and how different parts from different data-structures will interact with each other.
If you were to visualize a flutter app, and nowhere in that visualization the tree-like structure of the widget-tree would appear as such, that would collide with my mental model of how such an app functions.
This visualization will be induced by reading the code, much like reading a novel will produce pictures in your head. I'm not sure LLMs are the technology that will produce code-movies you would rather watch.
Location: Germany
Remote: yes
Willing to relocate: yes
Technologies: c/c++,openGL,currently looking into frontend(flutter,hmtl/css/js) and rust
Hi, I'm an autodidact that learned programming by himself. I have been coding on and off for about 5 years now. Looking to get any professional experience in the field. I am a creative thinker and can learn anything independently, usually gathering deep insight on the way. I am familiar with the basics of algorithms/data-structures and higher math and I have a keen interest in greenfield projects and software architecture.
Résumé/CV: I do not have a cv but if you email me, I'd be happy to share some code samples.
