“Vibe Coding” vs. Reality
121–130 of 312 posts
Re: “Vibe Coding” vs. Reality
#122Vibe Coding is a trigger word for devs who insist it's a pointless exercise because it doesn't do 100% of the job. Devs don't seem to realize that's not the point - the point is you can hire less devs if you're only worried about the remaining 20%. Also this article is immensely distracting.
Currently, AIs emulate a less skilled, junior developer. They can certainly get you up and running, but adding junior developers doesn’t speed up a lot of projects. What we are seeing is people falling into the “mythical man month” trap, where they believe that adding another coding entity will reduce the amount of work humans do, but that isn’t how most projects come out. To put it simply, it doesn’t matter if AI do…
a) More knowledge than the most senior developers b) Can work at ridiculous throughput 24/7
Re: “Vibe Coding” vs. Reality
#123Earlier quoted context omitted.
I work at a company relatively well-known in Startup-land and I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI. Devs are just coping so hard around LLMs its hard to watch. OTOH the few engineers who have embraced it are excelling.
> I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI. Totally believable bro
Re: “Vibe Coding” vs. Reality
#124Earlier quoted context omitted.
I work at a company relatively well-known in Startup-land and I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI. Devs are just coping so hard around LLMs its hard to watch. OTOH the few engineers who have embraced it are excelling.
I'd like to come back to this in a year to see how maintainable the codebase is.
Our code is better and more robust than it's ever been. Our rate of user-reported bugs have dropped more than 50% since we started "vibe" coding 6-ish months ago.
Re: “Vibe Coding” vs. Reality
#125I hate how what is effectively a stupid meme phrase became an actual term in a few days. > "Vibe Coding" might get you 80% the way to a functioning concept. But to produce something reliable, secure, and worth spending money on, you’ll need experienced humans to do the hard work not possible with today’s models. The problem is that 80% of the job is a proof of concept at best. 80% is effectively a QA walking into a b…
Re: “Vibe Coding” vs. Reality
#126This is the go community saying a computer will never best human go players. We already have examples of a model finding more performant sorts [0], given the right incentives and time, and the right system for optimizing (LLMs trained on “average code” probably aren’t it) the computer will best us at creating things for the computer. Is “vibe coding” real today? Not in my experience, with even Claude code. My hand ha…
The article is pointing out real limitations of vibe coding today (which you appear to agree with). It does suggest AI coding won’t be viable in the future. You should probably update your comment to say something like, “spot on”.
Re: “Vibe Coding” vs. Reality
#127You learn something new every day. Some days that thing does not piss you off. Today is not that day.
Re: “Vibe Coding” vs. Reality
#128Earlier quoted context omitted.
I work at a company relatively well-known in Startup-land and I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI. Devs are just coping so hard around LLMs its hard to watch. OTOH the few engineers who have embraced it are excelling.
Open mind here. Spill more details please. We're the 9 good or was their dead weight. Could the 9 to 2 have been done without AI anyway (because less work to do).
Re: “Vibe Coding” vs. Reality
#129Of course, I haven't seen a single vibe-coded thing that I'd want to spend money paying for yet, but that's probably more reflective of the difficulty of making something people want than whether or not you use vibe coding to do it.
Re: “Vibe Coding” vs. Reality
#130Earlier quoted context omitted.
I work at a company relatively well-known in Startup-land and I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI. Devs are just coping so hard around LLMs its hard to watch. OTOH the few engineers who have embraced it are excelling.
Is it already the part of the hype cycle where we just make shit up?