For years, the excuse was practical. I don't know how to code. I can't afford a developer. I'd need to raise money first. These were real constraints, and they kept a lot of ideas safely theoretical.

AI removed them almost overnight. You can build a working prototype in an afternoon. You can ship something functional in a week without writing a line of code yourself. The barrier that kept most people from building is gone.

And yet most people who can now build anything are building nothing. Or - more accurately - finishing nothing. Which raises an uncomfortable question: if the barrier was never really technical, what was it?

The interesting thing about removing a constraint is that it shows you which constraints were real and which were alibis. "I can't build it" was, for a lot of people, a comfortable reason not to confront a harder question: do I care enough about this to see it through?

It's easy to have ideas when you can't act on them. The impossibility is what makes them safe. You get to imagine the product, the users, the outcome - without ever testing whether you'd actually do the tedious, unglamorous work of making it real. AI called that bluff. It solved the how. And it revealed that the how was never really the problem.

The most common first instinct when people realise what AI can build is: I'll replace the tool I'm paying for. My own CRM. My own task manager. My own invoicing system.

But nobody obsesses about invoicing. These are solutions to mild annoyances, not responses to problems that keep you awake. You'll get a prototype running in an evening, feel clever about it for a day, and never touch it again. Not because you failed - because the problem wasn't important enough to sustain your attention past the novelty of building it.

The prototype works. You just don't care enough to make it good.

The people who will build things that matter are the same kind of people who always did - the ones who feel so strongly about a problem that they can't leave it alone. The kind of person who uses every existing solution, finds all of them inadequate, and can't stop thinking about what the right one would look like. That hasn't changed. Obsession isn't a skill you acquire. It's something that finds you.

What changed is who those people can be. You no longer need capital, a technical co-founder, or a computer science degree. The barriers to entrepreneurship collapsed. But the barrier to persistence - genuine, slightly irrational care about a specific problem - is exactly where it always was. The filter didn't disappear. It moved.

The filter didn't disappear. It moved.

The obvious downside is that this cuts both ways. When starting is nearly free, you start everything. The graveyard of abandoned projects isn't a personal failing - it's the predictable result of a world where every new idea is one prompt away from feeling real.

But the same dynamic that creates the graveyard might also shorten the search. You probably can't tell upfront whether a problem is yours to obsess about. The historical advice has always been to try things quickly and see what sticks. If AI makes trying nearly free - if you can go from idea to working prototype in an afternoon - maybe people cycle through the false starts faster and arrive at their real obsession sooner.

The doom is more abandoned projects. The boon is a shorter path to the one that won't let go of you. And you'll know the difference, because the project you care about is the one where the prototype isn't enough. It's the one where you look at what you built and think: this needs to be better. And then you actually make it better. And then you do it again the next day.

The story being told right now is that AI democratised building. Everyone can create software. Everyone is a founder. That's technically true and practically misleading. Everyone can start. That was already mostly true before, and starting was never the hard part.

The real unlock is quieter. Somewhere, right now, someone who has been bothered by a specific problem for years - who always knew what the solution should look like but couldn't build it - can finally act. Not because AI gave them an idea. Because it removed the last obstacle between them and the thing they were already obsessed with.

That's who AI is really for. Not the person looking for something to build. The person who already knows.

For years, the excuse was practical. I don't know how to code. I can't afford a developer. I'd need to raise money first. These were real constraints, and they kept a lot of ideas safely theoretical.

AI removed them almost overnight. You can build a working prototype in an afternoon. You can ship something functional in a week without writing a line of code yourself. The barrier that kept most people from building is gone.

And yet most people who can now build anything are building nothing. Or - more accurately - finishing nothing. Which raises an uncomfortable question: if the barrier was never really technical, what was it?

The interesting thing about removing a constraint is that it shows you which constraints were real and which were alibis. "I can't build it" was, for a lot of people, a comfortable reason not to confront a harder question: do I care enough about this to see it through?

It's easy to have ideas when you can't act on them. The impossibility is what makes them safe. You get to imagine the product, the users, the outcome - without ever testing whether you'd actually do the tedious, unglamorous work of making it real. AI called that bluff. It solved the how. And it revealed that the how was never really the problem.

The most common first instinct when people realise what AI can build is: I'll replace the tool I'm paying for. My own CRM. My own task manager. My own invoicing system.

But nobody obsesses about invoicing. These are solutions to mild annoyances, not responses to problems that keep you awake. You'll get a prototype running in an evening, feel clever about it for a day, and never touch it again. Not because you failed - because the problem wasn't important enough to sustain your attention past the novelty of building it.

The prototype works. You just don't care enough to make it good.

The people who will build things that matter are the same kind of people who always did - the ones who feel so strongly about a problem that they can't leave it alone. The kind of person who uses every existing solution, finds all of them inadequate, and can't stop thinking about what the right one would look like. That hasn't changed. Obsession isn't a skill you acquire. It's something that finds you.

What changed is who those people can be. You no longer need capital, a technical co-founder, or a computer science degree. The barriers to entrepreneurship collapsed. But the barrier to persistence - genuine, slightly irrational care about a specific problem - is exactly where it always was. The filter didn't disappear. It moved.

The filter didn't disappear. It moved.

The obvious downside is that this cuts both ways. When starting is nearly free, you start everything. The graveyard of abandoned projects isn't a personal failing - it's the predictable result of a world where every new idea is one prompt away from feeling real.

But the same dynamic that creates the graveyard might also shorten the search. You probably can't tell upfront whether a problem is yours to obsess about. The historical advice has always been to try things quickly and see what sticks. If AI makes trying nearly free - if you can go from idea to working prototype in an afternoon - maybe people cycle through the false starts faster and arrive at their real obsession sooner.

The doom is more abandoned projects. The boon is a shorter path to the one that won't let go of you. And you'll know the difference, because the project you care about is the one where the prototype isn't enough. It's the one where you look at what you built and think: this needs to be better. And then you actually make it better. And then you do it again the next day.

The story being told right now is that AI democratised building. Everyone can create software. Everyone is a founder. That's technically true and practically misleading. Everyone can start. That was already mostly true before, and starting was never the hard part.

The real unlock is quieter. Somewhere, right now, someone who has been bothered by a specific problem for years - who always knew what the solution should look like but couldn't build it - can finally act. Not because AI gave them an idea. Because it removed the last obstacle between them and the thing they were already obsessed with.

That's who AI is really for. Not the person looking for something to build. The person who already knows.