←back to thread

129 points Varun08 | 1 comments | | HN request time: 0s | 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 #
level09 ◴[] No.45196027[source]
But is it really vibe coding if you’re carefully building step by step and checking everything along the way? I feel like the kind of vibe coding people usually mean is more about blindly iterating until things work and patching bugs as they pop up—where you eventually get an app that runs, but it’s so messy that even a senior dev would struggle to audit or fully understand it.
replies(1): >>45198584 #
1. cramsession ◴[] No.45198584[source]
The truth is I don't check everything along the way! That's part of my high scale, I can now work on a dozen projects instead of a couple because I'm freed up from having to read all of the code. A huge shift in mindset for sure, but it's been working great.