You've had ideas for years. Now you can build them.
Software used to require developers. Now it requires intent. A field guide for the new builders.
No coding experience required. Type an idea. Watch it become real.
people tried to learn to code and quit. This page is for them.
AI didn't replace developers. It created new ones.
There's a principle called Jevons Paradox: when something gets cheaper, people don't use less of it. They use more.
When lighting got cheaper, cities lit up. When travel got cheaper, people went everywhere. When communication got cheaper, social media was born. The pattern holds: lower the cost of creation, and you don't get less. You get an explosion.
The software being built is about to explode — not because companies need more enterprise apps, but because people want to build things.
The kid making an app for his friend group. The jogging club. The sci-fi movie club for three people. The taco truck that finally takes orders online, the contractor who killed the clipboard. None of that exists today because creation costs too much. Lower the cost and you don't get less — you get more.
"There's a lot of people who never would have coded before who are going to get pulled into it because it's all of a sudden so easy."
— J. Chris Anderson, Founder of Vibes DIYChris calls this expanding authorship. AI isn't replacing authors. It's creating new ones.
What new builders are making
The most frivolous apps prove the platform works. If it took real effort, no one would bother building something this small. The fact that they do is the point. And the same tool that builds a movie-night app for three friends builds the order form that runs a food truck, or retires the spreadsheet a small shop has been fighting for years.
How to build
AI is a paintbrush. An extraordinary one. But you still have to know what you're painting.
Floor, Not Ceiling
AI gives you the average as a starting point. Your job is to push past it. Use AI to reach 80% — then spend your energy on the 20% that matters: the decisions, the taste, the thing that makes it yours.
The 3 Rules of Vibe Coding
- Start with the vibe, not the spec. Describe the feeling and purpose. The code follows.
- Iterate in conversation. Talk to the AI like a collaborator: "Make it warmer." "Too cluttered."
- Ship ugly, then polish. A working thing you can share beats a perfect thing in your head.
Reduction Over Accumulation
The lightest version is the best version. Every layer you strip away is one that can't break.
"Projects, not pets" — build things that don't wake you up at night.
The reading list
This isn't just a technical shift. It's a cultural one. Essays, interviews, and demos — updated as new work publishes.
Join the builders
Building alone is fine. Building with others is better.
💬 Discord
Where builders help each other. Weekly challenges, live builds, show-and-tell.
Join Discord →▶ YouTube
Demos, tutorials, and conversations with the builders.
Subscribe →✉ Substack
What we built, what we learned, what's next.
Sign up →⌨ GitHub
Our SDK is open source — view it, fork it, make it yours. The system prompts behind the generator are published in our docs.
Explore →The tool doesn't matter as much as the decision to start
But if you want the easiest path:
Vibes DIY
Describe what you want. Get a working app. No terminal required.
Vibes CLI
For people who live in the terminal. Claude Code for people who don't code.
"We're making the electric guitar. Let's see what happens after that."
— J. Chris Anderson