December 18, 2025

Ship by vibes, judged by comments

Two Kinds of Vibe Coding

Vibe Coding Wars: let AI drive or keep hands on the wheel — and everyone’s yelling

TLDR: A developer let an AI build a faster, fancier fractal viewer, embracing “vibe coding” where you don’t read all the code. The community split: some say it’s just speed with chaos, others call it burnout bait, while a few insist smart prompting can make AI-assisted coding worth it.

A solo dev says they handed the keys to an AI to supercharge a tiny Mandelbrot set viewer, pushing it from a neat 780 lines to a “tower of complexity.” The AI (Anthropic’s Claude) moved math to the graphics chip for speed and juggled tricks to keep pictures crisp. Sounds cool, right? The comments turned it into a reality show.

First, the definition police arrived. “There’s only one kind of vibe coding,” snapped wrs, arguing vibe coding literally means don’t look at the code. The author’s “two kinds” idea got dunked as vibe-washing. Then came the burnout confessions: WhyOhWhyQ said the thrill wore off and it became QA-testing a bad engineer, leaving nothing shippable and a lot of regret. Cue the meme squad: bloppe joked we need a book of “I vibe-coded this toy project, software engineering is dead” posts. Ouch.

On the hopeful side, predkambrij preached prompting as an art, saying better instructions and self-testing can make AI work shine. But Dr_Birdbrain asked the uncomfortable questions: Is it easier? Faster? More reliable? The room fell into a split: speed and sparkle vs. sweat and uncertainty. The vibes? Loud, divided, and very online.

Key Points

  • The author defines two forms of “vibe coding,” focusing on ceding cognitive control to an AI agent.
  • A Mandelbrot viewer originally built in 2009 and later expanded to 780 human-written lines was slow and limited by JavaScript fp64 precision.
  • Using Claude, the LLM-assisted version adds GPU acceleration and hybrid CPU/GPU perturbation algorithms to improve speed and depth.
  • The agent-generated code implements and benchmarks nine perturbation approaches, selecting per zoom level and compute availability.
  • Supporting features include quad-double precision arithmetic and an adaptive float32+logscale complex representation with GPU buffer management.

Hottest takes

“No, there’s one kind of vibe coding” — wrs
“It turned into QA testing the work of a bad engineer” — WhyOhWhyQ
“I vibe-coded this toy project. Software Engineering is dead” — bloppe
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.