A place for developers to talk about building on Farcaster.

/dev

I did ~4h of vibecoding at agi house saturday, takeaways:

It's slowwwww, each run is about 2-10m so you only get a handful per hour and they often fail or don't work correctly. Brutal feedback loop so I would recommend doing 3 or so projects at once to stay engaged.

Progress isn't iterative. A few times I ran prompts that improved one dimension but degraded another or broke the app entirely. Since each change is so sweeping, finding yourself out of that mess can be tough or plain slow. A few times I just reverted wholesale, cursor's built in checkpointing super helpful there.

@martinamps and I tried to multiplayer vibecode a bit across two machines and despite the beautiful makeshift rsync script it failed bad. It was cool that cursor could self heal when it detected a file changed mid run from a sync'd change though. Would be cool to have an environment optimized for multiplayer vibecoding.

I think a lot would be solved by faster agent runs (groq?) and limiting scope per run.

Use an agent like cursor, bolt or replit to build an app.

Ignore the code. Just prompting and vibing.

memebuilding • prev manifold.xyz, twilio.com

I've done this till I ran out of the o1 quota. But it's only ever worked for tightly scoped things.

Yeah, works great for scoped things and scaffolding.

Prob smarter agents having access to more signals via mcp and some parallelization could help.

But it’s part of the fun of vibecoding I guess.