vibe coding is great for a POC, but the defining difference between a POC and an MVP is that a POC is made to be thrown out, doesn’t have to work all the time (you can say “ah yup just need to give it a kick” when you’re showing it off and manually intervene)

vibe coding is good to show a basic, unmaintainable, non-production version of a feature of function, but then you need to take that and manually build it into your MVP - perhaps by copying some minor parts of the POC, but verifying every step

[–] the16bitgamer@programming.dev 12 points 4 days ago (1 children)

I just want to say that the V in this specific MVP wasn’t Viable

[–] pupbiru@aussie.zone 1 points 4 days ago

yeah viable is such a variable concept

i guess like… i have a friend that is a lab tech, and he vibe coded a stand alone HTML and JS page for their team to take CSV and filter it… the excel process they used before was horrendous… in that case, i guess that’s a viable product: it works, isn’t buggy (or at least bugs will become well known and able to be manually avoided or worked around)… i’d say that’s an MVP but wouldn’t be so if you wanted to productise it

[–] bytesonbike@discuss.online 3 points 4 days ago

I took it for a test run to build out a API as a proof of concept to my superiors to show what we can do.

I then started on a real version, saving the vibe code version as a backup in case I could cherrypick code.

After recreating the basic functionality again but properly, I looked at the vibe coded project and threw it in the trash. Had zero reusability.

[–] als@lemmy.blahaj.zone 4 points 4 days ago (1 children)

Damn, you really shouldn't say that people of colour are made to be thrown out. That's fucked up (/s)

[–] eager_eagle@lemmy.world 2 points 4 days ago

or "oh yup, just need to give it a kick"

[–] null@lemmy.nullspace.lol 1 points 4 days ago

Even before that, it's great for bouncing abstract ideas around for how you might go about defining that POC.