My experience has been that code generated "vibe coding" is prototype worthy, but code driven to be developed with Test Driven Development mindset and with forced architectural decisions is generally supportable.
The middle ground, trying to vibe code it, then declare it enterprise grade is doomed to disaster.
Yeah, I'm kind of AI-negative, but I found this very well presented and thought out. I'm not convinced that the fix for AI-heavy workflows is a good harness or an established codebase, but it seems difficult to show it for certain at this point.
Nice breakdown.
My experience has been that code generated "vibe coding" is prototype worthy, but code driven to be developed with Test Driven Development mindset and with forced architectural decisions is generally supportable.
The middle ground, trying to vibe code it, then declare it enterprise grade is doomed to disaster.
Yeah, I'm kind of AI-negative, but I found this very well presented and thought out. I'm not convinced that the fix for AI-heavy workflows is a good harness or an established codebase, but it seems difficult to show it for certain at this point.