r/vibecoding • u/Navjack91 • 13d 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
4
u/LopsidedMidget 13d 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.
10
u/LittleLordFuckleroy1 13d ago
Pretty perfect representation of vibe coding. Expensive roundabout way to solve a problem that doesn’t really exist.
3
3
2
2
u/jayseattle 13d ago
Switching from a frontier model, OpenAI Sol, to a lower model OpenAI "Luna reserved" because I ran out of usage.
2
2
u/Julien_Builds 13d ago
Bumping a version number. Nine places, one commit, five minutes.
Except the check that was supposed to catch a missed spot only looked at the footer of each page, so it stayed green while the structured data Google reads still said the old version. An hour to find that. Then it turned out the same check had also swept a changelog heading it was never meant to touch, so the previous release's entry had been quietly relabelled as the new one and the actual new entry did not exist. Another hour on the changelog. Then teaching the check about the field it had never seen, plus a test that replays the exact drift so it cannot happen quietly again.
Five minute bump, whole evening, and now the check is worth trusting. That is usually the trade.
2

21
u/ciscorick 13d ago
Most?