←back to thread

All vibe coding tools are selling a get rich quick scheme

(varunraghu.com)
129 points Varun08 | 2 comments | 09 Sep 25 22:06 UTC | HN request time: 0.001s | source
Show context
cramsession ◴[09 Sep 25 22:47 UTC] No.45190469[source]▶
The trick is that you have to be a good coder to get the most out of "vibe" coding. It works great for me, but I deploy all of the knowledge I've acquired over the decades as a professional developer. You need to know how to architect systems, what data structures and algorithms to ask for, how to design a product, many facets of graphic and user interface design, how to parcel out work, how to parallelize tasks. Even which ideas are worth pursuing is an intuition you build up over years. "Vibe" coding really is magic and I'm highly scaled, but I don't see how it could possibly work for all but the most senior developers. In some sense, it's like writing LISP macros on steroids.
replies(10): >>45190657 #>>45190885 #>>45191035 #>>45191109 #>>45191139 #>>45191169 #>>45191530 #>>45191570 #>>45192419 #>>45196027 #
1. dingnuts ◴[09 Sep 25 23:37 UTC] No.45191035[source]▶
What you're describing is not vibe coding. I realize some people call anything with an LLM generating code "vibe coding" but it's not and I'm going to die on this hill.

1 it's not the meaning Karpathy used originally, which was for creating software through prompts WITHOUT looking at the source code

2 it's not the meaning people outside programming circles mean, either, which is identical to Karpathy's original definition

the title of the article is talking about 2 and is completely correct.

YOU, on the other hand, are talking about an upgrade to IntelliSense. Use a different term. You're describing regular programming, with a new IDE tool.

If it's not going to replace programmers and allow regular people to create software without looking at the code, it's not vibe coding. Full stop.

replies(1): >>45191118 #
2. JimDabell ◴[09 Sep 25 23:46 UTC] No.45191118[source]▶
Amen. The difference is vast when it comes to discussions like this.

If you’re talking about AI-assisted development, then an AI agent being able to do 80% of the work is a fantastic win. The developer can pick up the remaining 20% and come out massively ahead.

If you’re talking about vibe-coding, then an AI agent being able to do 80% of the work is useless. What’s a non-developer going to do with something that still has 20% of the development left to do? It’s not 80% useful, it’s 0% useful.