How about running the code first by a separate agent that is “trained” to find bugs and security holes? Or does it not work like that? I recently heard someone talk about a setup he had with multiple agents runnings , 1 product agent, 1 design agent , 1 dev agent and a QA agent with each their own tasks across different LLM providers.
Login to reply
Replies (1)
They are all experts in all of these fields. I spin up new agents constantly.
I suspect that the root of the problem is not the agents ability to write good code but rather its reluctance to get rid of already-written code and instead rather *add on top* of the project. This accumulates waste that kills the project over time.
When I tell the agent to "don't hesitate to change existing code if your new approach would benefit from it" it seems to be a bit more daring.