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.
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.
… so, as long as it isn't actually "vibe" coding?
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.
why is it bad that customers hear the truth?
I believe that train has sailed on this association.