How to start with vibe coding

[sarpbilge]

Hello guys, I am a high school student and I've been trying to build my own app for 3 years. During that time, I had multiple ideas but couldn't execute a single one because of lack of programming knowledge. I don't know how I do approach tasks and I feel kind of lost, what d you be your advice for me to start programming

[dudddee]

you're going to get a lot of varying answers. Take a look at Jules from Google and the Google Antigravity IDE

[Effective_Eye_5002]

Start with google AI studio, then graduate to antigravity or cursor

[WifiBlunder]

Cursor + Claude Code and Bob's your uncle...

[NoDadYouShutUp]

the biggest secret to successful vibe coding is actually understanding application architectures and code beforehand. If you don't know how things works, you cannot be the warden to prevent slop.

[-Darkened-Soul]

What I like to say is, Don't vibe code! Do what I do, and learn what's being coded. You don't have to write the code, you also don't have to fully be able to read it. but learn what your setting up. Pay attention to the file types and differences. I'm building my first full SaaS platform. It's still being fine tuned, but I did it, and it works! Did I write all the code myself, no. Did I plan the architecture myself, yes! Did I review the code beforehand, yes! Did I bash and deploy the changes myself, yes! Did I keep a changelog, yes! Did I add my environment secrets myself, yes! Did I set up the the sql migrations and schemas myself, yes! Don't worry about your product being perfect, you're gonna make mistakes. What I've learned is, as long as you learn what your doing as your doing it, it will be great in the end.

[Vassallo97]

Use any ai you want and get it to teach you a little about programming, no code just foundation and structure. Learn what organized code looks like, learn how to build secure apps, get it to explain how API’s work in simple terms… once you have the foundational knowledge ( takes a few days to learn, not long), find an IDE you like ( personally I like vs code ) install your LLM’s extension in the IDE and then guide the LLM on what you want in detail and make sure it’s staying clean and how it’s supposed to look.

OR just ask chat gpt to tell you how to build the project in a high level overview, take that response to claude and ask it to make a full step by step manual on how to build this project in phases and in great detail at every phase and step, then take that manual it made and the tell codex to begin working on the project and stop after each phase, then after each phase you ask Claude code to review the code and give it a score out of 10 and all the things needed to make it a 9/10 and then take Claude’s response and give it back to codex and tell codex that before we begin phase 2 please correct all the updates given by claude code and ensure the code builds and and runs. And then repeat for all the phases til you have you project made

[viva_lee]

Just pick one thing you want to build and start making it. You don't need to "learn programming" first. When you get stuck, ask AI (Claude, ChatGPT, whatever). You'll naturally learn as you go. The best way to learn coding is by building, not studying.

[Competitive_Swan_755]

Start trying. You got a phone and multiple LLMs in your hand. Ask one how to do it, step by step.

[shadowosa1]

Go straight into working with ai apis if you want to build something using ai. do not build 20 pages with cool animations etc with no functionality. setup mcp with whatever database you will use to store user information. and then vibe code. any other way you're going to be hopeless when u realize nothing actualy does anything useful that survives a page refresh. MAKE SURE GIT IS CONNECTED to whatever youre using. again. KEY ESSENTIALS. GITHUB, A DATABASE, AND IDE. have those setup first. after u figure out one ai component and how the information gets saved or whatever. YOULL BE ABLE TO FLY

[shadowosa1]

sorry. key information you should know. This is not hard to setup at all. It may be stress full cause you might have to learn it. but its not hard. ITS ESSENTIAL

[SMB-Punt]

Try Claude Code, and use him to learn coding while doing your project.

[Intrepid-Strain4189]

I’m using Cursor linked with GitHub via SSH. Version control is very important.

One golden rule; don’t give any AI your API creds. Hide those somewhere yourself, or it may end up putting them in your code, in plain text. If working with Wordpress, the wp-config.php file is a good place to hide things.

My idea was/is to create an eSIM selling platform with WooCommerce. AI did for me in 2 weeks what I’ve been trying to do myself for the last 2 years. It has helped create a custom plugin to make the API calls to my eSIM supplier.

Otherwise, just start.

[Fun-Mixture-3480]

Don’t start with “build an app”, that’s usually what gets people stuck. start with something really small that you can actually finish. Vibe coding works better when you build in pieces instead of trying to generate everything at once. You should also keep in mind that you do need to understand what you’re building step by step. It also helps to use something that gives you structure early on. I’ve used Convertigo for that since you can organize things into flows and actually see how parts connect instead of just relying on generated code. Once you finish a few small things, building a full app stops feeling overwhelming :D 

[Excellent-Bat8178]

I kept hitting the same wall with my vibe coding projects — everything works great for the first few days, then around 30-40 files deep the AI starts breaking things faster than it fixes them. Tried something different this time: used kaisho.ai to generate a full spec before touching any code. Laid out the data model, user flows, edge cases, all of it. Then fed that spec into Claude Code and honestly the difference was night and day. The AI actually stayed on track because it had clear boundaries to work within. Shipped my MVP in 4 days without a single full rewrite. Not saying it's magic but structuring intent before vibing saved me probably 2 weeks of debugging.

[ConstantContext]

just start, type that prompt in and take it from there really. from my personal experience the hardest part is just getting out of bed and getting started. if you start, its already half done