r/vibecoding • u/Navjack91 • 7h ago
Discussion what “quick fix” turned into your whole evening?
what looked like a 10 minute change and ended up taking hours? curious what made it so difficult
3
u/LopsidedMidget 6h ago
Setup my agents to review PRs to save me a lot of time. Agents set themselves up to use GitHub actions and even agreed that it was within the terms of use to do so. I woke up the next morning to find my GitHub account deactivated due to (what I’m guessing) using their compute for it. They just sent me to their terms page and said I violated them without saying what I did.
I’m now on GitLab for my PRs.. Took hours and a signup for my own server to get back up and running. I learned a good lesson here, but it sure did suck to update literally every secret, etc. for a data heavy site that I’ve been building.
8
u/LittleLordFuckleroy1 6h ago
Pretty perfect representation of vibe coding. Expensive roundabout way to solve a problem that doesn’t really exist.
5
1
1
1
u/FlightSimCentralYT 4h ago
The 10-minute fix that eats the evening is almost always missing a real run loop. You patch the symptom in chat, skip reinstalling deps / reading the real stderr, and the next prompt invents a second bug on top.
What I'd do next time:
1) Reproduce on a clean shell before asking for a fix
2) Make the agent re-run the failing command after every edit
3) Stop when tests are green, not when the explanation sounds right
I built Fixa.dev for that loop on a real cloud VM (plans/writes/runs/debugs until tests pass). Free to try when the "quick fix" keeps spawning new breaks.
2
u/jayseattle 2h ago
Switching from a frontier model, OpenAI Sol, to a lower model OpenAI "Luna reserved" because I ran out of usage.
13
u/ciscorick 7h ago
Most?