←back to thread

All vibe coding tools are selling a get rich quick scheme

(varunraghu.com)
129 points Varun08 | 1 comments | 09 Sep 25 22:06 UTC | HN request time: 2.733s | 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. captainkrtek ◴[09 Sep 25 23:45 UTC] No.45191109[source]▶
I think this is spot on and aligns with my experience.

I've seen less experienced devs crash and burn trying to commit massive amounts of vibe coded slop without consideration to: how much of it was necessary? how does it conform with our code base / style? how much does it take advantage of existing code and patterns? and so on.

I think if you are using one of these tools and experienced, it should be difficult to tell you are using one at all. The code I produce looks like stuff I would write, and I understand all it wrote, I don't want to outsource to producing tons of code that I don't even understand.