Vibe coding is too much work.
I don't want to orchestrate a barnyard of agents to generate, refactor, validate, test, and document code I don't see, all while burning through a coal mine of tokens. I don't want to "live dangerously" or YOLO code.
I'm not a Luddite who hates AI or moving fast. I use Claude and Cursor daily; I've founded companies and worked as a startup engineer for over 20 years. But I wouldn't want to vibe code anything I might want to extend. Vibe coding leads you to uncanny valley of technical debt.
0:00 / 0:09 1×
source: YouTube It technically works...
The Magic Ruler
Imagine you find a "magic ruler" that lets you construct any building instantly, just by thinking of it. The ruler has one small flaw: it slightly changes the definition of an inch each time it measures something. It is great for building huts and cottages, but larger buildings are unstable.
Enticed by the potential of your magic ruler, you work to "manage away" any errors it creates. You discover that by referencing the measurements to one another, you can eliminate more than half of the errors. Encouraged, you add failure detection and create a workflow that regenerates broken structures until they work.
Despite these changes, each new project comes back with several obvious flaws that somehow avoided your detection.
... continue reading