The Non-Coder's
Manifesto
// What happens when anyone can build
lines of code I've written. Across 20+ products. All live. All mine.
This isn't a flex.
It's a provocation.
Code was a tax on ideas
You had an idea. You needed a developer. You joined the queue. Most ideas died waiting in that queue. The problem was never a shortage of good thinking. It was the cost of turning thinking into something real.
The permission problem
The barrier was never skill. Never money. Never time. It was permission. Permission to try. Permission to fail. Permission to ship something ugly and learn from it. The entire industry ran on a single assumption: only technical people get to make things.
years I spent in advertising before I built my first product.
AI didn't replace coders. It promoted everyone else.
I went from being the person who recommends things to the person who makes things. From "imagine if" to "here, try it." AI coding tools didn't take anyone's job. They gave strategists, designers, and editors a bigger one.
"Learn to code" was always the wrong advice
The advice should have been: learn to build. There's a difference. Coding is syntax. Building is decision-making. Which tool for which problem. When to ship versus when to polish. AI handles the syntax. You handle the judgment.
The question was never "can you write JavaScript?" It was "do you know what's worth making?"
We're not cosplaying as developers
Non-coders who build are a new category of maker. Not pretending. Not faking it. Making real things with different tools and different instincts. The strategist who ships a product isn't a bad developer. They're a good builder.
products shipped since September 2025. Without writing a single line of code.
4 hours, 114 pubs, one live URL
Pub Guide London. I noticed London didn't have a proper pub directory that felt considered. Four hours later: 114 pubs with filters, maps, Sunday roast ratings, and 114 custom OG images. From gap to live URL in a single evening.
pubguidelondon.com →Range is the point
A parenting directory. A culture aggregator. An AI poster shop with Stripe checkout. A Japanese restaurant guide. A tube exit planner. Same person. Same tools. Different taste applied to different problems. That's what non-coders bring: range without overhead.
When the tool does the making, all that's left is your judgment. That's both the power and the terror.
The prototype is the pitch
I don't send decks anymore. I send URLs. The conversation changes completely when someone can click it, use it, break it. "Here, try it" beats "imagine if" every single time.
When the kid goes to sleep. When the building starts.
This isn't about replacing developers
Developers are more valuable than ever. This is about who else gets to join the conversation. More builders means more things get built. More experiments. More ideas tested. That's good for everyone.
Taste is the new technical skill
When everyone can build, what you choose to build is what matters. The editing instinct. Knowing what to leave out. Knowing when it's done. Taste isn't a nice-to-have. It's the differentiator.
The best products aren't built by the best coders. They're built by the people closest to the problem.
Version one should embarrass you
If your first version is polished, you waited too long to ship. The point is to get it out, learn from real usage, and improve. Every product I've built started ugly. The discipline is shipping before you're ready, then listening.
Speed changes the conversation
When you can build it tonight, you stop asking for approval. You stop writing briefs. You just make the thing and show people. The competitive advantage isn't budget or headcount anymore. It's clock speed.
The gatekeepers are gone. The only question left is: what will you make?
If you have taste...
If you know what good looks like. If your instinct for quality has been sharpened by years of looking, comparing, and caring. That's how a pub directory gets Sunday roast ratings and hand-picked OG images instead of scraped data and stock photos.
If you have judgment...
If you can look at ten options and know which three matter. If you can kill a feature because it doesn't serve the user, even though it's clever. That's how a culture aggregator becomes a daily briefing instead of an everything-feed.
If you know what people need...
If you've spent your career understanding audiences, reading behaviour, and noticing the gaps that everyone else walks past. That's how a parenting directory gets built because every existing one felt like SEO spam.
You can build it.
Tonight. No permission required.
"Wait, YOU built this?"
That's the reaction. Every time. From developers, from clients, from recruiters.
Yes. I built this. This deck included.
