upvote
I personally think that there's nothing wrong with vibe coding so long as there are as close to watertight ways, checks and balances to verify that the output is correct. And the best way to do that is to invest domain specific expertise in coming up with as comprehensive a test schema as possible.

If the test schema passes and if your original articulation of intent was correct, then what you have is already very good. From that point onwards, it's the question of accelerating development by just reviewing the output of the LLM and getting it into the right shape.

The combination of the review of the output of the LLM and the review of the test schema and its output, that is going to be a lot quicker to do than coding everything from scratch with a proper design paradigm.

reply
> the best way to do that is to invest domain specific expertise

And precisely that is the issue: people vibe coding something and releasing it to the world don't have this domain specific knowledge to build upon. It used to be that building the software would force the programmer to learn about the domain, but that link is broken now too.

reply
I don't disagree. My point is that for the domain experts, it is undeniable that Vibe Coding is a massive accelerator.
reply
> … so long as there are as close to watertight ways, checks and balances to verify that the output is correct.

… so, as long as it isn't actually "vibe" coding?

reply
Domain experts can also do vibe coding is the principal thesis of what I'm trying to say.

So there's vibe coding for the general populace, and there's vibe coding which domain experts can use to articulate problem statements in well-formed ways and articulate test schemes to ensure that their articulation of the problem is actually solved in the best way possible.

Hopefully that makes sense.

Industry happens because of domain experts for the large part.

If domain experts have a way to accelerate their wherewithal significantly, then industry progresses significantly.

The promise of LLMs and the promise of vibe coding is fundamentally that domain experts of industry can significantly accelerate progress.

The rest, who are not domain experts and who are not of the industry, are also progressing, but the value of the progress they have in terms of how they contribute to how industry contributes to society is fundamentally questionable.

reply
The term was defined to mean slop. If you are vibe coding you are not doing engineering. I assume most customers don't like hearing that the people working on their code aren't aware in any way of the code they are pushing.
reply
> I assume most customers don't like hearing that the people working on their code aren't aware in any way of the code they are pushing.

why is it bad that customers hear the truth?

reply
Vibecoding has come to mean "AI slop code" where the people producing it don't understand it, like at all. It can be poorly structured and hard to comprehend.

I believe that train has sailed on this association.

reply
The word “vibe” vividly conveys that, whatever its merits, the process of “vibe coding” is not rigorous.
reply
What do you mean "come to mean"? At what point did it mean anything else, and why would it have?
reply