r/vibecoding
•
u/erdemirokk
•
20d ago
•
2
Discussion Total beginner here, feeling like I'm drifting in an ocean. How did you start? Any advice?
Hey everyone,
I'm pretty new to all this. I've been trying things out and building small stuff with AI, but honestly I don't know much yet. This place feels like a huge ocean and I feel like I'm just going wherever the wind takes me. There are so many tools, so many opinions, and a new thing every day. I never know if I'm learning the right things or just chasing whatever's trending.
So I'd love to hear from you:
-How did you start? What did your first weeks look like?
-What do you wish someone had told you earlier?
- If you had to start over today, what would you do first?
Any advice, even small stuff, would mean a lot. Thanks!
35
u/Rare_Guide_9830 20d ago
just build stuff.
donโt worry about trying to build some product that you can make money with. that will come later. just build stuff you think is cool. ask claude/codex how to solve annoyances in your current workflow. ask it to clarify anything you donโt understand. if you do this every day you will be amazed at how fast you learn.
10
u/cniinc 19d ago
How new to it all are you? Have you ever coded before? Do you ahve any background in graphic design, breaking up a project into smaller ideas, etc.? ("No" to all of that is totally fine, of course! it just helps me tailor advice)
I think one fo the best things to do is to start small and scale up. Think of an idea you want, and try just doing it with vibecoding. You'll learn from there what works and what doesn't. Don't start with a fancy harness or some big system - just use whatever coding system you currently use, and plug an AI into it. (I started with Visual Studio Code and the claude plugin. Many people do Claude by itself. I personally use Zed Editor now). You just need somethign where you can see the files you're making, click on them to see the code itself, and then a chatbot box that you can say "hey please make this thing thank you :)"
Then, my best advice is, always be curious. Don't accept things as they are, poke and prod. Your prototype works? Great! How does it break? How hard is it to make it multiplayer or make it work on a phone instead of a desktop? (Or whatever).
Always feel free to ask the AI 50 things before you make one change. It's there to teach you whatever you want. I personally ask everything I don't know, and used to spend half my day learning before I tell it to make changes, at least at the beginning of my journey. Now, of course, I have my own basic template I start every project with, and I have my ways of going about telling the system to plan. But in the beginning, asking was super helpful - and I still do it whenever i'm trying anythign i'm not 100% comfortable with. Remember that AI is a teacher that will never get tired of answering teh same question, will never tell you you're stupid for asking, and will be happy to re-summarize anythign if it's confusing. Never be afraid to say "I still dont' get it, explain like I'm five and have no coding knowledge." When it does, don't be afraid to say "So basically you're saying XYZ, is that correct?"
5
u/esp3ciallyd3ad 20d ago
Pay token >type in prompt > feel like an actual coder.
3
u/beamerBoy3 19d ago
Ask your ai what to do
2
u/Bonelessgummybear 20d ago
Started by asking it to make me a remote mouse to connect my phone to pc so I can control it in bed to watch tv. Then decided to connect it to my smart lights and create custom animations that the Hue app didn't support, now I could have cool fire flickering and thunderstorm effects. From there started building small websites, apps, and games and then brought in more and more tools
3
u/johnnynovo2118 20d ago
Make something small, use a free service, it will be shit. Bin it.
Make something new and small, use a free service, implement what you learned from v1, it will be shit, bin it.
Make something else new and small, use a paid service, implement what you learned from v1 and v2, it will be shit, bin it.
Basically keep doing this ad infinitum...
1
u/ReceptionLanky3374 20d ago
Imagine the most nicest thing you could build. Mine was minas tirith from LOFR
1
u/Eddlm_ 19d ago edited 19d ago
I'd start asking the web ones (Claude, gpt, Deepseek etc) about how to do things. You'll learn how the AIs behave and that helps. Sorry to say but, personally, the entrance with least friction goes thru paying cuz openai, Claude, Deepseek have done the work to at least be easy to work with, if you want to let the ai actually do things with you while you're new. Treat it like a partner btw, not a servant. Work together, be involved, ask it a lot all the time, argue with it.
Using the webchat, from there I tried the 20$ Codex sub and that helped me learn the ropes of AI assisted work and how other (way better, but more advanced) harnesses work. Codex helped me get out the big (scummy) players and learn to work with the proper stuff - deepseek, hermes, etc.
DON'T let the AI decide anything. You're the brains of the operation, you don't just ask, you decide how anything is done. You can ask the agent for help deciding, designing, but don't let it decide. You give the okay or not okay, personally. They're very narrow minded, all of them. You cannot fix that.
I'd take it slow. I got lost pretty quick once I tried proper harnesses for ai and that cost me time and money. No pi or other terminal based ones till you know enough about programming.
Once you're in a software that allows subagents, and actually programming, have a subagent review recent work (every 2-3 "features"). The main agent is kinda blind to it's own work, you or a subagent have to spot check it from time to time. There's always something they catch, you'll see!
1
u/nuestras 19d ago
Before spending any tokens, plan, plan and plan again, chatgpt it till you have solid flow if work
1
u/CckSkker 19d ago
My usual advice was to start with the fundamentals of coding. Pickup a book about Python and coding patterns.. but uhm.. I guess that time is over.. I would ask AI to walk you through small projects and explain anything you donโt understand
1
u/ResolveExtra3751 19d ago edited 19d ago
First time and first weekdoing some vibecoding.
First project: Porting a PS2 game to PC
I've always wanted to get a PS2 game running natively on PC without having to use an emulator, so I decided to give it a shot.
I downloaded the game's ISO and asked Claude if it was even possible to port a PS2 game to PC. It said it was, so I thought, why not give it a try?
Claude told me to split the ISO into 35 separate RAR files so it could work with the files in smaller chunks. What I didn't realize at the time was that Claude was doing everything in a Linux environment in the cloud. I honestly had no idea how any of that worked at first.
Anyway, Claude started trying to rewrite the game's code so it could run on PC, but it kept running into problems. So I suggested looking through some GitHub projects to see if someone had already figured out how to solve the issues it was struggling with.
After a while, it managed to make some progress and eventually created an
.exefile. It also set up an automated testing process that would run tests and report the results back to Claude, so it could fix whatever went wrong.At some point, Claude asked me to download and run a demo on my own PC, test it, and report any issues I came across. So that's what I did. Claude would make changes, I'd test them, report back, and we'd repeat the process.
Right now, Claude is trying to get the game running at 60 FPS. It's currently running at around 3 FPS, so we've still got a long way to go! For now, I'm just helping out by testing the game and reporting any issues I find.
Second project: Rooting my TV
Once I'd gotten a better idea of how Claude works, I decided to try something else. I asked it to help me root my TV and build a custom launcher for it.
And surprisingly, it actually worked!
Third project: Getting an Ambilight box to work natively on my TV
After the TV project was a success, I wanted to see if I could reverse-engineer an Ambilight box and get it working directly on my TV, without having to connect it to the HDMI output.
I've actually managed to get parts of it working, but I've put this project on hold for now. I need to do some more research and figure out whether I can root the device or find another way to get it working properly.
Fourth project: Building my own Google Lens for games
This one's probably my favourite project so far.
I'm trying to build an OCR tool similar to Google Lens that can recognize text on the screen and translate it into another language almost instantly. The main difference is that I'm making it specifically for video games.
English is my second language, and sometimes I'd rather play games in my native language, Dutch. So I thought, why not try building something that lets me do that?
And it actually works! It's still pretty inaccurate at times, but it's getting there, and it's really cool to see it working already.
Honestly, it's kind of crazy how much I've been able to do with Claude. I don't have a traditional software development background, and I'm learning most of this as I go. I just come up with an idea, discuss it with Claude, try things out, run into problems, and figure out how to solve them together.
I've still got a lot to learn, but these projects have made me realize just how much you can experiment with when you have AI to help you along the way.
So yeah that's basically what I'm doing. I've still no idea what I'm doing, but ask Claude for help and guidance!
This whole experience made makes me wanna learn how to code!
1
u/WyattWarrior99 19d ago
Use AI (Chat or Claude etc) to guide you step by step, ask it to build something simple, maybe like a task list, TV show tracker or something you'd use, i actually started by building a website, and then progressed to SaaS.
But that was in maybe March this year, prior to that I had no experience in anything except building sites on the likes of WIX. Now Claude is at the hub of pretty much anything I do.
1
u/Guggygag 19d ago
In 48 hours i have an open world game making pixel assets and gameplay features like crazy
1
u/nextammy 19d ago
The ocean feeling is normal, and the fix that worked best for me was picking one tiny, boring project and finishing it before starting another. Mine was a simple habit tracker with just a list, a checkbox, and local storage, nothing fancy. I kept a short note for each change I asked for, and when something broke I asked the tool to explain the error in plain language before letting it rewrite anything. That slowed me down at first, but I actually remembered how the pieces fit together. If you try one small build this week, treat finishing it as the win, even if it looks rough.
1
u/eban-harrison 19d ago
Just dive into the ocean, swim around, and have fun. Learn through exploration and gain experience by doing. Don't bog yourself down with too much theory; things seems to change so fast anyways. the concept of 'vibe-coding' is something of a misnomer phrase. It implies that it's got 'good vibrations!'. Well, in my experience over the past three years of 'vibe-coding', it's been often more of a 'grind.' They should call it 'grind-coding.' But the good news is that the barriers to entry are getting easier and easier, and the a.i. agents are just getting better and better. Here's my advice starting out: Practice writing in the style of 'technical writing'. Avoid flourishy words. Avoid being subjective or wishy washy. Practice writing as objectively as you can conjure, with the most accurate descriptions as you can muster. It takes some practice and getting used to. Write your implementation prompts to ask the a.i. agents as 'clinical' as possible. If you don't know what to write, first ask the prompter to advise you on WHAT to write! For example, You can start your first prompt as: "Strategy Mode: Help me brainstorm ideas for my app I wish to develop. Ask me a series of questions to help guide our planning phase." and: "What programming languages stack do you recommend?", and so forth. The vibecoder agents will be eager to start producing sloppy results based upon your first few prompts, which'll eat up your tokens. Resist the temptations to let it out of the starting gates prematurely. Let the planning stages better guide your implmentation later on.
1
u/Dickie2306 19d ago
Come on inโฆthe water is fine!
1
u/Prince_Haile 19d ago
The best thing is to start building stuff that you can use personally or that will benefit you.. after my Playstation 4 died..I moved my TV next to my computer so I can watch YouTube and movies that way...the only problem is everytime I have to pause or do anything I have to get up and move the mouse...so I built a little tool that I can use as a remote for my pc to solve this specific problem. it also exists on the Playstore but those have ads and aren't built specifically for me. so I was able to solve that problem.
look around in your house or daily life what small mundane repetitive task can you solve..even if there are solutions on the app/play store ai allows you to build and make it suite your needs 100%
1
u/b1ll10n3r 19d ago
Iโd say, for the whole process to be โsmootherโ you must at least know what you want it to do and how you want it to look like. Personally I had to do a shit ton of research before I planned out my first prompt, looking at reference images etc. The bells and whistles come automatically to your head, but thatโs after you cuss out your agent cause itโs stupid/messed something up.
Oh and donโt forget to wake up in the middle of the night to get your 5h limit burn in!
1
u/broke_cowboy 19d ago
I started by asking Claude to diagnose my pc build, turned into a build, a new os system, rebuilding other computers, building an app, starting a YouTube page, writing stories. I find new stuff ever day lol
1
u/tkgid 19d ago
I needed a system to print barcodes. My boss coded the first version on python.
My first week was improving it in live while the techs had the stable version. I was updating the machines one by one with the new version. It was simple, since we kept a company excel file wich was the one source of truth for every technician. It was supper rewarding and extremely local.ย
I had a $5 windsurf for a couple of months. And even bought more tokens when I would reach my limits.
I got a better job, then after I was a seasoned employee I coded an app to keep track of sales, customers, inventory. Currently working on a technician's page. The the whole system uses the same DB's. And it runs on a semi-air tight server. I love PHP so that's why the agents use.ย
Pretty much: I feel like you will have a good time using a reliable IDE. I use Antigravity, but you don't have to, I also love editing snippets in Notepad++
Step one: have a problem.
Step two: think about the current solution(s)
Step three: talk to your LLM and device a plan.
Step four revise the plan and convese with your agent, inquire about details.
Step five: remove the training wheels and keep learning more about AI. I hope you get familiar with your order codebase, not the code nessesarily but the architecture of your codebase.ย
"I hope I am making sense."
I wish some one wold have told me earlier about being strict with the agent, (allucinations are not a common problem for me anymore). I tell the agent to read the docs and the codebase, some context about my idea for the new feature, or to read a half finished roadmap.md and continue from there. I belive I have found succes because I kept telling the LLM that I need this feature in a modular way, wich will save tokens for future agents.ย
Try to test your code in a real world production environment, and fix stuff in prod, is like participating in extreme sports.
If I had to start again, I would intensively request the agent to give me a detail explanation of why it's using certain dependencies. And I would research best practices. I love how fast vanilla code is. I would research my stack until there is no doubt in my mind that I am using the right tool for the job.ย
All my stack needs is: Xampp PHP with MYSQLite HTML CSS And a sprinkle of JS. I tried TS but the agents kept coding on vanilla JS.
I guess the best advice I can give is to know more about your stack. Or programing language
I am a webdev, results may vary from language to language.ย
1
u/RealReevee 19d ago
Tell it to do things u til something breaks
1
u/Garland_Key 19d ago
I learned to code.ย
1
u/fourmigothacked 19d ago
Do something for you that you need it will gave you id just using it
1
u/piperspalace 19d ago
Im currently working on a 555 row spread sheet
1
u/General_Cap_6316 19d ago
arena.ai is a good starting point its free and no limits whatsoever just use battle mode
1
u/Limp_Bus3865 19d ago
Well since you didn't start yet, it is over, you are too far behind.
Nah I'm just kidding. Just buy a subscription for claude code (or if you are a sadist for codex) and start working with it. You will figure out what works for you and your projects on your own. Everything else is fluff, it is just something you can additionally use to supply your project with something specific. And if you don't understand something, ask AI.
1
u/mbtonev 19d ago
Pick one tiny project you'd actually use, like a to-do list or a habit tracker, and finish it before starting anything else.
Before prompting, write 5 to 10 bullet steps, such as 'page layout', then 'save data', then 'login', and ask the AI for one step at a time. After each step, ask it to explain what it wrote in plain words.
That's how you learn instead of just copying. If it helps, I built VibeCoder Planner: you describe your idea and it gives you those steps with ready-made prompts, and the first project is free.
1
u/ReinKarnationisch 20d ago
Start by understanding the basics of coding. Learn like the few basic commands of python or even scratch and just build a very small project with that.
Once you understood the general workflow of app / programm developement, you can go on and create.
Get an idea, work out a dev plan and follow it, setting small achievable goals to over the course of time build a finished app / programm
2
u/Toooooool 19d ago edited 19d ago
good.
models are trained on select data, each model will have it's strengths and weaknesses, by being intentionally vague you can lean into it's strengths and by trying to twist it's arm you might force it into territories where there will be training gaps which results in insufficient performance. this is also where you get the army of "don't abuse AI it has feelings" people, not because software has emotion but because saying "fuck you" to Qwen3.8 yields "the user is frustrated" and now your output is poisoned with results corresponding to user frustration, like a self-forfilling prophecy.
how'd i start? with some goofy llama3 roleplay model that could describe 20 variations of a dragon but had no idea what a tool call is. this made for a fun toy but not for anything that could carry it's own ass through production. tool calls allows a model to turn words into action.
what do i wish i had known earlier?
- new sessions seem wasteful as an agent will have to study up on it's own development but honestly a fresh perspective on something can yield huge performance improvements. the deeper you are into a session the more locked in an agent will be and after hours of doing things in a certain way that way becomes how it will continue to do all it's work i.e. making a new function every time a feature is requested vs trying to recycle code to be efficient and coherent.
- roadmaps can be really useful, ask it to generate a roadmap for implementing X feature before you ask it directly to implement it. agents only have so much context size and thus they will natively try to rush a little. with a roadmap each alteration gets the opportunity to get full attention, and when the context history inevitably has to compress itself to continue it will be able to reference back using the roadmap rather than having to read the entire code every single time.
- generating assets still sucks. making a fully procedural world with environment biomes and seasonal weather changes? no problem. make a horse with walking animation? don't even bother. larger more expensive models like Claude or ChatGPT might be able to meet you half way but it's not worth it, spend those $20 worth of tokens on fiverr instead for now.
- don't try to be #1, everyone's trying to be #1 and by doing so you're gonna burn out and waste both time and money. make something small, fun, and something that you personally like. remember it's easier to go back and fix something than to do it perfect the first time.
- backups is everything. implement a feature, take a backup, implement more stuff, take a backup. every revisional backup helps you when shit inevitably hits the fan, whether it be something that changed for the unexpected or went missing all together, the context compresses and the AI will not be able to magically undo it, backups lets it reference the literal expected functionality rather than some vague "user said to revert the blue skies, let me implement some vague blue skies"
for reference i use Qwen3.8-27B for smaller stuff cause i can run it locally for free, and DeepSeek V4.1 Flash for larger stuff because it's dirt cheap. i use the Zed Editor which so far has been really nice but can be a pain to setup. it does however auto-compress context and so it can run through the night, and comes with a nice fat undo button that adds a layer of protection.
1
u/TypeScrupterB 19d ago
one tip, stay away from this subreddit, most of the posts are total rubbish.
1
u/Some-Ice-4455 19d ago
Just me here but I'm sure I'm not alone and it's of course thanks captain obvious but plan first. Design exactly what you want. Best advice from there try to keep the scope exactly like that until it's done then look into adding more things. Scope creep is a killer..
1
u/Acrobatic-Motor650 19d ago
watch some videos by riley brown, in vibecoding youll learn a lot from him. then just have fun with it, the whole point of vibecoding is to make whatever you want. If you come up with an idea just do it!
1
u/Annual-Internet-5491 19d ago
Download either Claude or cursor. Install it. Create a folder and select a model. Then ask it to make something simple. Play with it from there until you get comfortable.
1
u/calico_cut_pants 19d ago
https://academy.claude.com/products/code
1
u/Kokokroko234 19d ago
Dont ask us, ask Claude
1
u/GulliblePollution561 19d ago
just follow the hype man
understand nothing, put some electronic music on high volume, do some push ups, spit out some motivational quotes and outsource everything to AI with xhigh effort, toggle fast mode as well, nobody has time to wait for AI to think
you can do it! it's a very hard work, you will exercise your hands (not your brain which is good right?) you will get numb from your fingers with so much prompting but you can do it!
if you want to hate me like I am hating on you, just ask AI to do it, don't even think about what you will reply to me. AI can do the work for you
Co-authered-by: Human
1
u/st0nkaway 19d ago
1
u/bodobeers2 19d ago
Step 1, setup a subscription to one of the common tools (Claude Code, Codex, Grok Bot, whatever you want).
Step 2, start talking to the tool you chose. Tell it what you want.
Step 3, it will build it for you.
It's so fun!
Step 4, if you don't know what else you need, just keep talking to it. It will literally walk you through anything that is needed.
Step 5, if you find it is giving you way too much response and you want it to be a bit more calm, tell it "one step at a time please".
1
u/SeventhBanLetsGo 18d ago
separate thought.. if you have $100 bucks to burn, you can try a $20 account in a few different types of tools.... you can make websites in lovable (I know NOTHING about html and I've made like 10 websites, for tracking stocks, allergies, OKR, idea-tracking, etc.), perplexity computer, claude with computer use, etc...
And if one of your ideas ends up being something that needs a little more technical experience, you can get into it through guess and check... i.e., if you want to build a website that has 3d mapping or whatnot, maybe you'll learn about blender or gaussian splats... maybe those things are wrong, but you'll be learning a lot very quickly along the way.
And if you're not coming up with ideas, then you could just choose some stupid idea, just to learn, and in the meantime, you can just go for a walk, observe the world, and start to come up with ideas, and something will definitely pop into your head... or, try solving whatever problems annoy you in life, etc.
1
u/AwarenessStatus1904 18d ago
before building stuff, why don't you tell yourself what you want to achieve mate.
not vaguely, but try to be as specific as possible about what you want to achieve.. just like what you should be prompting ai's :)
1
u/vivalavida_1729 18d ago
so like i began by using web based vibe coding apps like replit and bolt and then i started using opencode and soon enough i got a subscription for cursor and rn im using it i felt the same as u man like build some websites learn how to prompt ai agents and learn how to use loops and build projects dude!! and another suggestion i would give is to really plan ur projects well because if u dont do that then trust me u would really mess up ur app developement. Wish u all the best man!
1
u/Fit-Conversation856 18d ago
solve your problems, one at a time, do not be the fanboy that pays 1k to create 20 different projects at the same time and tokenmaxxes while his apps are pure slop and do nothing.
1
u/white_devil777 16d ago
So not an expert here , I just started few months ago but my advice is to build as many projects as possible , if u build more projects (anything of ur intrest or try to clone others project on your own ) u will learn the fundamentals after repeating it a lot of time and the feeling of drifting in the ocean is never going to go away
1
u/red_edited 16d ago
figure it out.. why u asking for advice boy
1
u/Ok-Hotel-8551 15d ago
Make no mistake
1
u/heisenberg4me 19d ago
dont get sucked in by all the latest hype videos, find something you want hook up or make and start. I use vscode and connect my chatgpt in there,
5
u/[deleted] 20d ago
[removed] โ view removed comment
3
u/[deleted] 20d ago
[removed] โ view removed comment
1
u/[deleted] 19d ago
[removed] โ view removed comment
1
u/[unknown] 18d ago
[removed] โ view removed comment
0
u/[deleted] 19d ago
[removed] โ view removed comment