In software - rarely do you know beforehand that you're building a chair.
Even when you're building in an existing category of products (say, databases), there are still lots of variations and trial and error needed to get "what we need" defined clearly.
I'd say "vibe coding" is just a new name for "exploratory programming" or good old "prototyping"
Even when you're building in an existing category of products (say, databases), there are still lots of variations and trial and error needed to get "what we need" defined clearly.
I'd say "vibe coding" is just a new name for "exploratory programming" or good old "prototyping"