We found a division by zero bug in FFmpeg with a vibecoded fuzzer

Re:We found a division by zero bug in FFmpeg with a vibecode... by simonjuk on Thursday August 27, 2026 @05:05PM (#49471255)

In my experience, there are two ways to use AI: speed or quality. Speed is where you give the AI a task to do and you review it; quality is where you write the code yourself and you get AI to review it. Both are valid for different situations.

[ Parent | on HN ]

Re:We found a division by zero bug in FFmpeg with a vibecode... by merb on Thursday August 27, 2026 @05:26PM (#49471486)

My plan for bigger things is mostly:

Generate multiple solutions- they do not to work 100% correctly. And than I check which I would prefer. Which is more to our applications taste.

And than I would take the vibe output as a kind of a ‚plan‘ which I use to implement but not follow 100% and at the end I take my solution and review it. I gain speed with that because I often can quickly see the pros and cons of a solution way better than when I would manually do it and hang on a major roadblock and also I even see such roadblocks in the vibe output - it’s mostly the part with an unnecessary amount of new code that looks nonsensical.

[ Parent | on HN ]

Re:We found a division by zero bug in FFmpeg with a vibecode... by UltraSane on Thursday August 27, 2026 @06:36PM (#49472178)

Using a LLM whose output is slowed to the rate of a human programmer as a pair programming partner is a very interesting experience.

[ Parent | on HN ]