Everyone Is a Builder Now

This morning at 9am, I watched my screen. I didn't touch anything. The newsletter I built - the one I've been sending manually for weeks - sent itself. I just watched it happen. A year ago, I couldn't write a line of code.

Here's what changed: Building used to require knowing how to build. You needed to code, or you needed someone who could. That wall is seemingly going away. If you can say what you want in words, and you can recognise whether what comes back is what you meant, chances are you're closer to making it real than you think. Everyone is a builder now. Most people just don't know it yet.

Before ChatGPT, I wanted to build a tech business. But I couldn't code. So my options were: find a technical co-founder, hire developers, or learn to code myself. I tried pieces of all three. None of them worked. I'd sketch ideas in notebooks that went nowhere. I was someone with vision but no hands.

Then ChatGPT arrived. At first I used it like everyone else - answering questions, drafting emails. But I noticed something. These models don't understand what you want. They understand what you say. The skill isn't coding anymore. It's two things: Can you put what you want into words? And can you look at what comes back and know if it's right? That's it. That became my new training.

I failed a lot at first. I'd design an entire workflow - ten steps connected - then build it all at once. Something would break. I couldn't find the bug. Everything collapsed. Start over. Same result. Then I learned: don't build a machine. Build small pieces that each do one thing. Connect them with a system that hands off tasks like a relay race. Primitive. Boring. But when something breaks, I know exactly where. And the rest keeps running.

What you build has a life. You're not just writing code - you're teaching something to exist. Can it wake up on its own? Can it rest when there's nothing to do? Can it feed itself the data it needs? Can it recover when something goes wrong? I build small gadgets. Each one has a job, knows when to act, knows how to finish. And they talk to each other. One finishes, tells the next one to start. I'm not running the system anymore. I set it up. Now it runs itself.

Here's what I want you to understand: this isn't my story. This is everyone's story now. The tools are just one click away in your browser. The difference between someone who builds and someone who doesn't isn't technical skill anymore. It's whether you decide to start. Your problem is different from mine. Your solution will look nothing like mine. Good. That's the point. There's no right way. There's your way - shaped by how you see problems, what you care about, what you refuse to accept.

I'm going to keep sharing what I build. The failures too - maybe especially those. Because that's how I learned: watching others figure it out in public. Now I want to know what you're building. What problem made you angry enough to solve? What broke three times before it worked? We're all going through this at the same time. That's never happened before. A year ago, I watched my ideas go nowhere. This morning, I watched my system run without me. What will you build?