Startups / software / traveling / skydiving / running

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.

memebuilding • prev manifold.xyz, twilio.com

I joked after that instead of trying to both develop at the same time I should have been vibecoding the most killer marketing campaign, web thru slides thru memes, while he built the app.

The true duo.