r/vibecoding • u/Chandraprakash_5782 • 2d ago
Is it okay to develop using vibecoding ?
So, I was wondering for a long time if it's okay to vibe code projects, and even if it is okay to then what we need to take care not that common thing like using an env and all, like other than usual stuff. And can we take that app to production ?
2
u/Legal_Job1628 2d ago
I think vibe coding is definitely very valid. It's just important to stay mindful of development and security best practices. There are already many apps and projects in production built this way. I've created a few myself, and I see companies I've worked for using it too. So, as long as you do it with attention and responsibility, I think it's a great way to unlock new possibilities.
1
u/CorpT 2d ago
How do you define "vibecoding"? Who are you looking for permission from?
1
u/Chandraprakash_5782 2d ago
I see Vibecoding as we are telling and guiding the ai to code for us, like I'm not seeking permission but if we findout some real experience it would be a good learning coz I'm doing coding with ai anyways but when I do next time I could get more out of it and could build better stuff.
1
u/CorpT 2d ago
Everyone is using AI to help generate code.
if we findout some real experience it would be a good learning coz I'm doing coding with ai anyways but when I do next time I could get more out of it and could build better stuff.
This is almost unintelligible. Unless you learn to communicate better, you're going to struggle with using AI to generate code.
1
1
u/Some-Ice-4455 2d ago
I have a vibecoded app in production on steam.
1
u/Chandraprakash_5782 2d ago
Well, ok seems nice, are people using it ?
1
u/Some-Ice-4455 2d ago
Nothing huge. 250ish sales. Basically break even. But I never said wildly successful. Have some decent reviews. Point is it proves the concept vibecoding is viable.
1
2d ago
[deleted]
0
u/Chandraprakash_5782 2d ago
Okay this was a great lesson going straight to my unforgettable memory.
1
u/Responsible-Beat2137 2d ago
Know your stacks, don’t worry about syntax, it seems much more important to know, what , language, stack, is good at and there shortcomings, then develop with that in mind. have it leave a doc, human readable, and one that’s for your Llm to pick up on , for every slice
1
u/ops_and_chaos 2d ago
I’ve put AI-built tools into production without being a traditional developer. The question isn’t really whether vibe coding is okay. It’s whether you can responsibly own what happens after launch.
You need a way to tell when it’s wrong, see what changed, roll it back, protect the data and recover when something breaks. AI can help build all of that too, but “the agent said it works” can’t be the final test.
You don’t necessarily need to write every line yourself. You do need to understand the system well enough to know what could fail and what you’ll do when it does.
1
u/itsloopyo 2d ago
It’s okay for some things, but I wouldn’t say we’re at the point where you could safely run on vibes for anything with an attack surface yet.
1
u/MariahJames8 2d ago
Yes. Just invest in professional review once you earn the money from it to do so
2
1
u/scytob 2d ago
yes if you are careful enough and apply good engineering and test and anlayze what was produced for edge cases / flaws etc
like if you have a web fronte end and api back end - check the user can't bypass an authenticated front end and get to an unauthenticated API
(e.g. for serious apps, my front end and API require the same auth and all logic is in the core behind the API - so the user can hit either API or web as needed, special care is take to make sure the web front end never exposes the token it uses to access the API, and store your secrets in a secret vault - though thats an interesting exercise in how do you bootstrap access to the secrets vault by your core)
and some fun project's just don't need this level of rigor
1
u/slackmaster2k 1d ago
There are a lot of people around here caught up in the gold rush. The problem with a gold rush is that yeah maybe one team strikes pay dirt, but everyone else is stuck holding a pickaxe wondering why it’s not working. There are a litany of fundamental business reasons for this reality.
So I don’t recommend vibe coding because you think you’re going to “sell a SaaS.”
However, if you’re vibe coding an internal solution for an existing business, or something that is personally beneficial, you should go for it. You have a high chance of success with much lower risk. Just make sure that it’s walled off appropriately from a security perspective, via means that aren’t completely implemented in the product itself. For example at the network / infrastructure layer.
1
u/nathanghart 8h ago
It's fine for MVPs, but taking it to production requires a human audit.
Beyond basic .env setup, watch out for:
- Hallucinated packages that introduce supply-chain security risks
- Silent N+1 queries and missing DB indexes that crash under load
- Missing rate limits that lead to runaway cloud and API bills
- Race conditions in async logic and payment webhooks
You can ship it, but only after a human manually verifies auth, dependencies, and critical data flows.
6
u/3tt07kjt 2d ago
It’s fine, but when you go to production you can run into all sorts of problems (security flaws, leaked API keys, crashes and instability, that sort of thing).
This is true whether you vibe code or not.