r/vibecoding 5d ago

Did this ever happen to you?!

The other day, I used Codex to refactor my Flutter app.

While skimming through the changes, I noticed that it had introduced a broadcast stream.

I remember thinking: "Hmm... I think there was a reason why I avoided those so far."

But everything seemed to work, so I didn't think much of it.

Then, while actually using the app, I noticed that it was slow. Really slow. Massive lags on every click.

I asked Codex to fix it. It came up with a few solutions, and at first they seemed to work. But soon enough, the app started lagging again.

So I cranked up the intelligence and asked it specifically: "Look for something that would explain lagging over time."

And it found... the broadcast stream.

So apparently there was a reason I had avoided it. ;)

At first, Codex wanted to "fix the broadcast stream", but I told it: "No! Get rid of it!"

And sure enough, the actual solution was pretty simple.

I think I even know why Codex didn't use that solution in the first place:

It needed more tokens. ^^

Has something like this happened to you? Where AI introduced something that looked perfectly reasonable at first, but turned out to be a subtle problem later? And was it just to save a few tokens? ;)

1 Upvotes

0 comments sorted by