fasteddie31003 parent
I've been playing around with vibe coding and I think a lot of the issues brought up could be fixed by an architecture abstraction layer that does not exist today. My idea would be something like an architecture-graph (Archigraph working title) that would recursively describe how an application works or should work. Then when an agentic coder is doing a task they can easily see the bigger picture of how an application works and hopefully writing better code. Anyone interested in working on this with me?
That abstraction layer that does not exist today looks a lot like the many high level architectural design languages that were hot in the 90s. Never heard of UML?
I bet there is an LLM based version of Rational Rose currently under development somewhere.
I'd be interested to see how tools like Cursor/Windsurf and even Copilot are modeling this internally. This idea seems to be a natural extension to having a hierarchy/team of agents all working on a common goal. In this case I would imagine one agent serves as the architect or reviewer, and another generates code to meet spec, and they fight back and forth until converging/diverging.
I've been thinking about this myself, although just planning to reuse what's already there.
How do you picture the human in the loop?
"Vibe Coding" is not Software Engineering.
It is "Slopware Engineering".
I was playing with the idea about setting up something like this!
Give me a shot