Comment by deadbabe

> Vibe coding, on the other hand, is competing against hand coding, and for many use cases is considerably more efficient. It’s clearly replacing a lot of hand coding.

Vibe coding, like 3D printing, is great for little small batch runs of boutique code. Small toy apps and throwaway projects.

Vibe coding is shit for doing actual maintenance on important projects that actually run the world. It is shit for creating anything that is of robust long lasting quality. It is shit for creating code you can trust. It is shit for creating code that won’t suddenly reveal flaws and inefficiencies at scale and require an entire proper rewrite just when your product is finally gaining traction. Vibe coding has not been around long enough to make these problems obvious yet, but the time is coming. A few high profile failures will hit the media and then suddenly everyone starts coming out of the woodwork with their own vibe coding horror stories and thus the AI bubble collapse begins.

What people will eventually realize, is that if you’re building a serious business with software that must run reliably for years, it really doesn’t give you any advantage being able to vibe code something in a week vs carefully building something out over a few months. Being unable to vibe code your way out of non-trivial maintenance issues is a death sentence for your business, you will need people who know what they are doing eventually.

Relying on vibe coding causes you to have a talent debt, and though you won’t feel it when you’re first rolling out a business, eventually, the bill comes due…