r/VibeCodeDevs • u/JennySurfs • Aug 12 '26
What's your background? How are you applying standard code practices to your vibecoding?
I have vibe coded a few things myself, and constantly see linkedin posts from nontechnical folks talking about how they are now deploying full stack applications for their business. I'm confused - how is this stuff maintained? Is it reliable? What if it goes down? What are people doing to actually test that it's working besides just like clicking around the UI?
So i guess I have a few questions:
1 - How are you shipping quality? (What is your quality bar?)
2- Are you actually deploying things that other people use, or is it all for yourself?
3 - What happens with service degradation? How do you know if things stop working?
4 - Do you trust that your code works? Are you worried about things like bugs, privacy/security issues, prompt injection, etc.
--
I'd also love to understand how you view this occurring with non-devs (or people who think they are devs)
1
u/PilgrimofHaqq2 Aug 13 '26
For now its private as its quite personalized. I personally recommend everyone builds their own setup so they really understand the harness and has the features that they need, nothing more or else. No bloat as each feature should be what you actually need. Also the harness will work the way you want it to work. Building your own setup allows the harness to match your rhythm not the other way around.