Hacker News Reader

Comment by superkuh | Hacker News Reader

I understand the audience this person has written for: professional developers. In that context, sure. But for everyone except professional developers vibe coding is amazing.

It gets the things they want to do done. No paying someone else, no asking for help on $chatprotocolchannel, no getting a friend to help. It's just there. It doesn't matter if it's ugly. It doesn't need to be monetized, doesn't need to be worked on by a team of people. It just needs to work... enough.

Vibe coding may not be for you. But vibe coding is so that we don't need to bother you for trivial things (like porting a 12 .c file X11/cairo program to a single .pl file cariro/gtk program).

View on HN

> It gets the things they want to do done

As long as you stick within pretty strict limits. I'm seeing more and more folks from non-programming backgrounds who are running up against the limits of vibecoding - and they aren't prepared for just how expensive some of the larger mistakes will be to fix, if they end up having to bring actual software engineers in to fix/scale their products

Yeah, I can see that. But for human people not at work there are no products. There are no "expensive" mistakes. There's just the ability to automate tasks and do simple things they, I, couldn't do before. No reason at all to involve any businesses now.

Or at least before $project would take weeks instead of an hour. I don't know C but now I can just have an LLM translate/port it to perl and I can fix the mistakes in that domain where I do have skill.

Even for professional developers I am not buying this argument. I think there is an argument to be made that we actually don't know how to work with these tools effectively and repeatably yet. But as the tools improve and we figure out the processes more that may change. It might not too, but I am leaning more toward it working better when we figure out how to use it than not.

e: Not a q for parent, but maybe for others. Are we supposed to be making a distinction between "vibe coding" and "coding with an AI agent"? What is the difference?

According to Wikipedia, vibe coding is "fully giving in to the vibes, embracing exponentials, and forgetting that the code even exists" and "If an LLM wrote every line of your code, but you've reviewed, tested, and understood it all, that's not vibe coding in my book—that's using an LLM as a typing assistant"

I have no issues with that and I made it very clear. Vibe coding for non-technical people is great.

> But for everyone except professional developers vibe coding is amazing.

I think I might argue the opposite but sure.

You missed the point, he is saying after a point vibe coddling simply doesn’t work because llms are hitting a ceiling

Reply on news.ycombinator.com