←back to thread

129 points Varun08 | 1 comments | | HN request time: 0.374s | source
Show context
cramsession ◴[] 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. dorcy ◴[] No.45191530[source]
I was able to teach my interns more about architectural designs instead of coding. Teaching them more about DDD instead of going through what’s broken with this function. We might be close to a point where you can teach product people about these basic concepts, packages and saas tools, and have them vibe code a whole app.