The Illusion of Waves: When “Looks Right” Isn’t “Built Right” ft. VibeCodeArena

There’s something fascinating about challenges that feel visual but are actually deeply mathematical underneath. The “Ripple Wave Visualizer” prompt sits exactly in that category. At first glance, it sounds like a UI problem—draw some circles, animate them, make it pretty. But the moment you start thinking about what a ripple actually is, you realize you’re not building a UI anymore. You’re attempting to simulate a physical phenomenon. And that’s where things got interesting. Two models took on this challenge. Both produced working outputs. Both rendered ripples on a canvas. Both had controls, interactions, and animation loops. But under the surface, they reveal two very different interpretations of the same problem—and more importantly, two different limitations of AI-generated code. Let’s unpack this properly. What Was Asked vs What Was Built The prompt wasn’t vague. It explicitly asked for: Ripples behaving like real waves Overlapping waves with interference Organic motion using sin