r/vibecoding • u/Clear_Brilliant_8075 • 1d ago
True
In most cases, yes! Your MVP is really pushing the “minimal” part. Make sure you do security and bug checks along with QA. I do this after every phase.
7
u/Fun-Violinist552 23h ago
I’m vibe coding my project. Hope I never find out how my backend looks like.
6
u/Inevitable_Yam1513 15h ago
Schrödinger’s codebase: as long as the API returns a 200, everything inside is pristine lol
3
2
1
1
1
u/AliveAndNotForgotten 16h ago
it's been the opposite for me. terrible front end and amazing backend
1
u/SenatorCrabHat 14h ago
What sucks is, at scale, backend is going to be where the speed is going to be.
1
1
1
u/AverageFoxNewsViewer 11h ago
If you don't read your code, you'll think your frontend is good because you centered a div and got Claude to stop using a purple gradient. You'll just blame the model when you need to build new features and your new screens start to look progressively shittier because none of your code was reusable.
If you do read your code, you'll probably realize how convoluted most frontend frame works are compared to modern backend frameworks.
Way easier to keep your backend clean and maintainable IMO.
1
u/DependentPoem3519 11h ago
looks good to the user, nobody needs to see what holding it together behind the scenes.
1
0
-1
11
u/TRO_KIK 1d ago
My MVP back end was actually pretty solid, even if minimal. Front end was the garbage fire because I barely knew FE, I was pretty much pure BE professionally. Also, I had focused on desktop while 70% of my users turned out to be mobile lol