vibe coding is trash for MVPs… it’ll get you there, but as always the achilles heel of vibe coding is maintenance and bugs
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
vibe coding is trash for MVPs… it’ll get you there, but as always the achilles heel of vibe coding is maintenance and bugs
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
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.
Even before that, it’s great for bouncing abstract ideas around for how you might go about defining that POC.
I just want to say that the V in this specific MVP wasn’t Viable
Damn, you really shouldn’t say that people of colour are made to be thrown out. That’s fucked up (/s)
or “oh yup, just need to give it a kick”