Hacker News new | past | comments | ask | show | jobs | submit
verdverm | on: We should be more ambitious with the software we build
> I've been attempting to build something that ... pushes the model ... never understood ... one-shot builds

Same, and I have found some of the failure modes in the realm of eyes free coding and limited auditing. I often see it more as pushing the process than the model, as I tend to bounce around models for the benefits diversity provides.

Have you also found there is a point where they hit code complexity and start churning without progress? (at which point you have to step in to help the bot step back and think big picture, which usually takes a few sessions)

blueblazin | parent | next
Yes! I absolutely have! And I've been thinking a lot lately about how to prevent them from collapsing into this state. It is getting better with newer and better models though. But yes, there comes a point when the codebase size and complexity crosses a threshold and we enter a churn state with very little progress.

I was motivated to make the codebase visualizer linked above to help me understand how the various pieces of the system that is being vibe coded connect with each other.

Now I'm thinking about how I can build something similar for agents. How can we teach "systems thinking" to a model?

loading story #50228382
cwnyth | root | parent | next
I just have it constantly update real-world analogues for keeping track of everything. I have it create guides, note cards, flowcharts, running to-do lists, etc. with every change.

It helps us keep track of things, why not AI, too?

loading story #50227940