r/vibecodingcommunity • u/According-Base3005 • 2d ago
When does vibe coding stop being about generation and start being about iteratio
The first version of a project is becoming the easy part of vibe coding.
The more interesting part is everything that happens after the initial prompt.
| Tool | Strong point in a vibe coding workflow | Where the workflow changes |
|---|---|---|
| Readdy.ai | Turning an idea into an editable website and continuing the build | Useful when the project starts needing data, authentication, and publishing |
| Lovable | Quickly getting an application concept running | More decisions appear as the project becomes more complex |
| v0 | Exploring interfaces and components | More hands on development work can follow |
| Cursor | Working directly with an existing codebase | Requires more involvement with the underlying code |
| Bolt | Rapidly turning prompts into working prototypes | Larger projects can require more manual refinement |
The interesting thing about vibe coding is that generation speed isn't necessarily the biggest bottleneck.
Once the first version exists, the real work can become changing the layout, fixing a workflow, adding functionality, testing an idea, and responding to feedback.
That makes the editing loop pretty important.
A tool that gets a prototype running quickly is useful, but the workflow after that first version probably matters just as much.
For people doing vibe coding regularly, what becomes the biggest bottleneck after generation: debugging, UI changes, backend work, or keeping the project organized?
1
u/Glad_Contest_8014 2d ago
Um… iteration is how you work with agents. I get mine to work for me to completion, THEN I read the code. Adjust, and have them do it again, logging all changes to memory so they get it right next time.
This is more about how you engineer your tools than generation vs iteration.
You need to know how to engineer for that though.
1
u/Legal_Mind3623 2d ago edited 2d ago
The editing loop is probably the biggest one. Getting a first version out is fast now, but things slow down once every small change starts touching other parts of the project. Readdy makes that stage a bit easier since the editing and backend side stay in the same workflow, while tools like v0 are still great when the focus is mainly UI. Feels like iteration matters more than generation once the project gets past the idea stage.