| ▲ | fork-bomber 4 hours ago | |||||||
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. | ||||||||
| ▲ | pietervdvn 4 hours ago | parent | next [-] | |||||||
> 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. | ||||||||
| ||||||||
| ▲ | zahlman 2 hours ago | parent | prev [-] | |||||||
> … 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? | ||||||||
| ||||||||