| I like your thing. I have been forcing my bot to give me Mermaid diagrams, swim diagrams, markup tables of schemas, code, logic etc... I like where you guys are going, but what I think would be really fun - would be a Node Based diagram logic, where the boxes that you show in the diagram are Code-geometry-Nodes - and could be connected with code blocks as such. Watch @HarryBlends videos on Geometry Nodes in Blender for Inspiration: https://www.youtube.com/@harryblends https://www.youtube.com/watch?v=a-4oCHe-hDE These are the best graphic/node based visuals for describing structured relationships in maths I've ever seen. To give you some CyberPunk FutureVision of what your outpus could be like -- if it turned all the code nodes into atomic code legos and rather than drawing the diagram from the code - I can use the diagram to create the code. -- WRT "...some code goes to anthropic..." while answering another, seems like you guys would do well to know these guys: https://news.ycombinator.com/item?id=41381498 https://www.usevelvet.com/ As well as these guys: https://news.ycombinator.com/item?id=41322281 https://github.com/instantdb/instant |
In designing CodeViz we were inspired by the Maya hypershade, which closely resembles the diagram-based blender tool that you shared.
https://help.autodesk.com/view/MAYAUL/2024/ENU/?guid=GUID-22...
These examples show how taking a diagram-based approach to software development can abstract away complexity with minimal loss of control over the end result. I love your image of "atomic code legos," and these legos can still always be edited the level of code when needed.
And yes, if CodeViz can generate architecture diagrams from code, the inverse can and will be possible: generating code from architecture diagrams.