The program
VibeCode: learn to build your own software with AI
Four weeks, six modules, live on Google Meet. You bring an idea and leave having built it yourself.
- Starts
- Monday 12 October 2026
- Length
- 4 weeks
- Sessions
- Wednesdays and Saturdays, 2 hours each
- Where
- Google Meet
The six modules
Every session is applied to the project you walked in with.
- 01
From idea to prototype
What vibe coding is and isn't. How applications actually fit together: frontend, backend, database, auth, APIs, hosting. Enough of it to tell when AI is building the wrong thing. How to cut your idea down to the smallest useful version instead of the version that never ships, describe it to AI, and get something running on your screen. Including how to work without burning money: what a token is, what you are charged for, and the habits that turn a $200 week into a $20 one.
It won't be perfect. That's the point.
- 02
Build the real product
Pages and navigation. Interfaces people can use. Databases, so your product remembers things. Sign-up, login and protected areas. Forms that save what they collect. The rules that make your product yours. Built in a way that transfers: standard tools, sensible structure, code you could hand to a developer later without starting again.
Your prototype becomes a product with users and data.
- 03
Make it actually useful
Payments, AI features, email, SMS, maps, file uploads, notifications, webhooks. Plus the skill that outlasts all of them: reading a service’s documentation with AI, so you can integrate things nobody taught you.
It stops feeling like a demo.
- 04
Debugging with AI
Something will break. Reading errors, using developer tools, checking logs, isolating a problem, keeping AI from rewriting code that already works, and recognising when it is going in circles. Then testing what you built, so the next break is one you find before your users do.
Instead of typing "it’s still not working" for the ninth time.
- 05
Security and production basics
Environment variables, API keys, what is public and what is not, database permissions, user access, handling sensitive information, basic production checks.
And knowing when you should not vibe code something yourself.
- 06
Ship it
Deployment, hosting, a custom domain, analytics, error monitoring, mobile, basic SEO, polish, and collecting feedback once people are using it. Including what running it actually costs and how to keep that near zero until you have users worth paying for.
Then ship. Not someday.
Also in the cohort
A guest session
One session is given by a guest, someone building and shipping in the wild, talking about what that actually takes.
Also in the cohort
How I did it
A session on my own path: what I taught myself, what I built, where it went wrong, and what I would skip if I were starting now.
What you build
By the last session you have all of it.
- A working digital product
- A database
- A usable interface
- Authentication where it is needed
- Real functionality, not a demo
- The integrations your product needs
- A deployed application
- A live URL you can share
Beyond the sessions
What enrolling includes.
Three more weeks of support
The cohort ends before most builds do. For three weeks after the last session you stay in the support channel, where people are on hand to answer questions when you get stuck.
The community, for good
A permanent channel with everyone who has been through this: opportunities, introductions, meetups, and other people building at the same time as you.