Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

“Vibe Coding” vs. Reality

cendyne.dev

Post reply on HN
Print view View original

11–20 of 312 posts

Re: “Vibe Coding” vs. Reality

#11

Post by Trasmatta »

jgilias wrote: post #5
Trasmatta wrote: post #2

The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.

I feel exactly the same. On the other hand, the “speed up my work a lot” part is important, and shouldn’t be overlooked. Like, if someone reads this article and figures they don’t need to learn to use AI for their coding job, that’s the wrong conclusion to make.

Agreed, I feel that a developer who refuses to learn to work with AI tools will inevitably fall behind those that do. But I don't see AI being able to replace a developer who can work WITH AI anytime soon (at least on anything non trivial).

Re: “Vibe Coding” vs. Reality

#12

Post by pton_xd »

bobxmax wrote: post #4
Trasmatta wrote: post #2

The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.

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.

You likely should have replaced those devs years ago. Kudos to LLMs helping you figure that out though.

Re: “Vibe Coding” vs. Reality

#13

Post by stavros »

bobxmax wrote: post #4
Trasmatta wrote: post #2

The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.

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.

Re: “Vibe Coding” vs. Reality

#14

Post by cmdli »

bobxmax wrote: post #3

Vibe 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 does 80% of the work if that last 20% takes 5x longer. As long as you need a human in the loop who understands the code, that human is going to have to spend the normal amount of time understanding the problem.

Re: “Vibe Coding” vs. Reality

#15

Post by Trasmatta »

bobxmax wrote: post #4
Trasmatta wrote: post #2

The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.

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.

Are you a developer yourself?

Product people love the idea of being able to fire their dev teams, but I'm not sure they understand the implications (some of wich may not become clear for years).

Re: “Vibe Coding” vs. Reality

#17

Post by do_not_redeem »

bobxmax wrote: post #3

Vibe 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.

The problem is it's more work to figure out which 20% it did subtly wrong, than it is to just do things right in the first place.

https://twitter.com/leojr94_/status/1901560276488511759

https://twitter.com/leojr94_/status/1902537756674318347

Good thing this guy wasn't in charge of an actual business, because if he was it would have been killed overnight.

Re: “Vibe Coding” vs. Reality

#19

Post by nextts »

musicale wrote: post #7

"ever since I started to share how I built my SaaS using Cursor" random thing are happening, maxed out usage on api keys, people bypassing the subscription, creating random shit on db as you know I'm not technical so this is taking me longer that usual to figure out - (leo, 2025)

That one is almost a meme on Linked In. For fun I hope it is a long troll (like a long con but for trolling)

And most of linked in (as the algo show me!) is basically this HN post in 100 words or the polar opposite saying how software engineers have had their chips.

Re: “Vibe Coding” vs. Reality

#20

Post by dataflow »

Trasmatta wrote: post #2

The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.

> But it's nowhere close to being able to replace what I do.

I'm increasingly worried that that's not the same bar employers will have.

Post reply on HN