Vibe Coding to the Max š
I didnāt start vibe coding because I had a genius idea. I started because I was procrastinating. Scrolling! Watching people ship websites, Apps, Micro tools and more. Seeing those Lovable ads pop up every five minutes. And then I had this moment:
āWhat is actually stopping me from doing this?ā
āWhy canāt I just join the crowd?ā
So I did. Because the only thing worse than failingā¦ is wondering what wouldāve happened if you tried.
The Spark š„
It started small. I worked with my cousin on my friendās business website ā PureOrigins.uk. He was more advanced with AI tooling at the time. He kicked it off. I picked it up midway and finished it.
That was it! The spark that started this journey!
If I could do thatā¦ I could do more.
Then I watched another friend engineer his site forefinder.golf purely through vibe coding. Watching him iterate fast, ship quickly, break things, fix things ā it was addictive.
And when I say addictive, I mean addictive.
There were nights I shouldāve been asleep but instead I was pushing another increment live. The only real battle now? Managing my ADHD and not juggling 12 projects at once š
Look To Start Small š¤
My friends have asked me:
āWhy donāt you just build one big āseriousā thing?ā
Simple. I wanted to feel what building with AI was actually like. I studied Software Engineering. I worked in DevOps. But over time I drifted more into delivery and programme leadership. Vibe coding has been my way back into building ā seeing code again, understanding structure again and once more breaking problems down. Itās been like reconnecting with a muscle I hadnāt flexed properly in years.
So for now I am working primarily on:
- Personal tools
- Experiments
- Friendsā projects
- Potential business ideas
- Things that started as shower thoughts šæ
I find one of the biggest, most rewarding surprises, has been building my own website. I had been putting it off for years. I couldāve used WordPress or a template, but building it increment by increment just hit differently. More control! More ownership!! More reward!!!
The Biggest Lesson: AI Is Not a One-Shot Machine š§
Early on, I thought if I wrote a comprehensive enough requirements document, AI would build the whole thing in one go. Right?
Wrong!
Even with detailed instructions, thoguh personal experimentation, I find it falls short if you try to do too much at once. Thatās when something clicked. This isnāt magic. Itās Agile.
Build small. Ship fast. Iterate.
The moment Codex started losing sight of the narrative, ignoring design intent and drifting from the vision, I realised dumping everything into one mega prompt wasnāt the way. You have to guide it, just like you would guide a team.
Shipping Small But Fast ā”
For me, this looks like:
- Build the skeleton.
- Break functionality into parts.
- Deliver one working slice at a time.
- Test behaviour and styling.
- Merge only when it behaves properly.
I even built myself a lightweight starter repo template, something I can copy into any project to standardise how AI behaves as a small delivery team. It frames AI like a Product Owner, Scrum Master and Dev Team; But all controlled by one person.
That structure alone improved the quality of what I was building.
AI Isnāt Just a Tool. Itās an Extension š¤
At some point I stopped treating AI like autocomplete. It became an extension of me.
Does having a dev background help? Absolutely. Is it required? No. But thinking like a Product Owner helps massively. If you can break work down, clarify outcomes, guide direction and refine incrementally, youāll get far better results.
AI builds. You steer.
Thatās the game!
Futher pitfallsā¦ Agents: Theyāre Powerfulā¦ But Can Often Over-Engineer š§©
Agents are incredibly useful when youāre stuck on a big hurdle, need structured reasoning, or want gaps identified in your thinking. Theyāre great at decomposing complexity.
But they can over-engineer small problems. Sometimes the solution is simple. Not every task needs a swarm of agents.
What Frustrates Me š
Letās be honest. Depending on what model you are using, what prompting you have provided, AI does not one-shot beautiful UI. It doesnāt naturally nail UX without direction. At least that has what I have observed. Evidently it is an area which developments are being made. Especially if we were to look at what is coming out of China with Kimi-K2.
If you want something polished, youāll spend time refining prompts, adjusting structure, fixing layout quirks and re-aligning to your design intent. That iteration loop can be exhausting.
But thatās also where the craft comes in. A new muscle you develop along this journey. The AI prompting muscle. Something I feel will strongly be our future. Learn how to correctly prompt with AI now, will pay dividends for all in the future.
What I Learned (Accidentally)
Just download the tools.
VSCode. Codex. Copilot. Claude.
Stop overthinking it and start small.
Also join a Discord community or start with your friends. Some of my best learning came from conversations about whatās actually achievable, better strategies for building apps and even discovering local LLM setups like Ollama for projects where buying tokens didnāt make sense. Things which only came up in conversations with my friends. Things which helped grow my knowledge and shape the way I attack projects
You donāt need the most expensive stack. You need the right stack for the job.
Has This Changed Me?
Yes.
I find it has made me more rounded. Itās brought back the builder in me. Itās reminded me how to start small and structure an SDLC that fits the scale of the project, not some enterprise theatre version of it.
Iām learning more. And Iām learning faster.
If Youāre Thinking About Starting š
Start small!
Understand what AI can do. Understand what it cannot do. Yes, you can build a full product. But there will be hurdles: UI refinement, architecture clarity, scope drift and your own discipline.
Treat it like a team member. Not a vending machine.
And if you get stuckā¦ Well Iād say Google it but maybe, form now on, Iāll start saying GPT it š¤£ Jokes aside, there are massive communities out there which can help you explore and navigate this new world. YouTube videos which really help to break things down nicely. And like I said before, levarage your friends. If they havenāt started already, started this journey together. Joint learning is a very powerful tool in and of itself.
The Truth
I believe vibe coding isnāt about AI replacing developers. Itās about building better solutions. Itās about bringing shower thoughts to life!
For the first time, the gap between āI have an ideaā and āit existsā is tiny. And once you realise that, you stop waiting. You stop over-planning. You stop saying āone day.ā You just build!
Messy. Incremental. Imperfect. But live.
AI hasnāt made me a developer again. Itās made me a builder again. And thereās a difference. ām shipping more. Learning faster. Thinking bigger.
And honestly? Iām only just getting started š