Re: About vibe coding
FrigidFoxtrot <[email protected]>
| Newsgroups | comp.ai |
|---|---|
| Organization | A noiseless patient Spider |
| Message-ID | <[email protected]> |
On 3/22/2026 9:05 AM, Oguz Kaan Ocal wrote: > ?Is it just me or is "vibe coding" basically just high-level rubber > ducking that actually types back? I see people acting like they > discovered a new dimension of engineering because they can prompt a Claude- > 3 or whatever to spit out a React component without knowing what a hook > is. ?The "vibe" is fine until the state management goes recursive and > you have no idea why because you never learned the stack. It's just black- > box orchestration. ?Are we actually coding or just "vibing" our way into > a massive technical debt bubble? > -- > > > > > ----Android NewsGroup Reader---- https://piaohong.s3-us-west- > 2.amazonaws.com/usenet/index.html > "Tech Debt" is what I think of every time I hear vibe coding. You just get a pile of spaghetti. Except it's worse, because unlike a human, the AI is going to just make up whatever post-hoc explanation is statistically most-likely for whatever crazy stuff it did. It is pretty good at spitting out a workable POC (provided it's a relatively simple thing you're trying to do). So it's nice speculatively trying those small side ideas that you want to try, but just don't have the bandwidth to do. I'd never want to deploy one of those though; blindly trusting code that I never looked at, from an entity that is known to produce absolutely dogshit code, is just too sketchy for me. Once you get the POC done and you see what worked (or didn't), then you open your IDE and actually write code that you're not ashamed of.