3 ms·
4 days into vibe coding a POC in a framework and language I don’t know, but with 40 years of coding experience: It’s amazing! The scenario is perfect, a use ca
by nialse 1y ago
4 days into vibe coding a POC in a framework and language I don’t know, but with 40 years of coding experience: It’s amazing!
The scenario is perfect, a use case that is not currently supported but may well make sense. It’s basically sketching out an idea to let business evaluate its market viability, and to gather further end-user input.
Will the code reach production? It just might, but it at least needs review and refactoring by a developer seasoned in the framework. They might even want to rebuild it, and then they have the yard stick which to measure their output. And if they need a specification, it can be generated from the code in which ever specification format required by their processes.
The key here is that I’ve been able to iterate on the POC many times in a short time. The idea sketch has been refined, necessary details added, while others removed. Functionality swapped in and out while testing different approaches.
Right now vibe coding in this way requires substantial experience in software development to frame the problems and solutions to the AI. Without my understanding of the domain (both the software domain and the actual domain) vibe coding the POC would not have succeed.
My greatest concern is that it looks and works too good and thus will be kept as is even in production. As the old adage says: There are no temporary solutions, just more or less permanent solutions. A temporary solution that works is a permanent solution.
- TheEdonian 1y agoExcept we all know that that vibe coded POC will never be rewritten and if it's a market fit will be pushed to production by management.
- Ekaros 1y agoAnd then it will crash and burn because things like security was forgotten. Or something like multi-tenancy was not designed in from ground...
- closewith 1y agoThat's the current state of the human art, so no regression here.
- nialse 1y agoThat is what I’m alluding to. But also, I work in a security aware industry, so those things will be vetted. And my own experience make me address some of the potential concerns already in the POC. The real divide going forward will be between vibe coding with experience across domains vs vibe coding without IMHO.
- omnicognate 1y agoThe whole point of vibe coding is that you don't review or attempt to understand the code. If you do, you're a developer using AI as a tool, which the video is not arguing against - indeed, he links to another video he's made explaining one way of doing that. You could call that "vibe coding with experience" but it just devalues the term, I think, and certainly misses the point in this particular case.