AI Tore Down the 'I Can't' Wall — the One Left Is in Your Head

I spent a long time these past few days staring at two sets of numbers. Three years ago, both would have sat squarely in the “impossible” column.

The first set: DeepSeek, a team of a few hundred people that grew out of a quant fund, built a model that goes toe-to-toe with OpenAI. Its founder, Liang Wenfeng, is worth $36 billion this year — more than the co-founders of OpenAI and Anthropic. A few hundred people, out-building a company of 100,000+.

The second set: the 2026 World AI Conference (WAIC) opened, for the first time, a dedicated zone for one-person companies — 180 solo projects on display. One person can also be a company.

Three years ago, if you’d said either of these things to anyone in the industry, the answer would almost certainly have been the same word: impossible.

Now they’re just sitting there, plain for anyone to see.

The “I can’t” wall is being flattened

Let me be concrete. The “impossible” that used to block an ordinary person was, in the vast majority of cases, not “this thing can’t be done” — it was “I don’t know how to do this.”

I can’t write code, so I can’t build an app. I don’t understand design, so I can’t produce a decent interface. I can’t edit video, so I can’t start an account. I can’t set up a server, so I can’t launch anything. Every “I can’t” is a wall, holding an idea inside your head, unable to get out.

These past two years, AI has flattened these “I can’ts” one by one.

You can’t write code — say what you want to Claude Code, and it writes it. You can’t design — describe the look you want, and it produces it. You can’t configure an environment, connect a database, or write a regex — things that used to take months of dedicated study are now a single sentence away.

How concrete does this get? Someone who has never written a single line of code, as long as they can clearly describe the product in their head, can have — in an afternoon — a clickable, usable prototype running in a browser. That same thing, three years ago, was a small team plus several months of work.

The core of the doaipm way of building, stripped down, is one sentence: you say it, and AI builds it. This isn’t a metaphor. What you say becomes something that actually runs and that other people can use. The wall of technical skill really has fallen.

Building software three years ago vs. building software today

Let me make “the technical barrier has fallen” concrete, so you actually believe it.

Three years ago, an outsider who wanted to build even the simplest little tool faced this path: either spend months learning a programming language until you could write something usable, or scrape together some money to hire a contractor or a programmer friend, translate your needs into words they understood, go back and forth on revisions, and wait weeks or even months — all while a single “that’s technically hard to do” could talk you out of it at any moment. The vast majority of people fell apart at step one: “Me, an outsider, go learn to program? Forget it.”

Today’s path: open an AI coding tool, describe in plain language what you want, and it writes it out and runs it right there. Not happy with it? Say in plain language “change this part to that,” and it changes it. In an afternoon, you’re holding something clickable and usable. You wrote not a single line of code the whole way — you may not even understand the code it wrote — and none of that stops you from getting the product built.

This isn’t the future tense. DeepSeek, Qwen, Claude — these models are sitting right there, free or very cheap, for anyone to use. The real barrier has moved from “do you have this craft” to “can you clearly say what you want.” And the latter is a capability that everyone who understands their own needs already has.

On the other side of the wall, there’s actually quite a pile

Don’t think “one person building a product with AI” is still some rarity, something that only happens in the news. It’s becoming everyday.

Open any developer community and shares like these are more and more common: a person with no technical background built an automation script with AI and killed off a two-hour daily chore; a designer built a complete SaaS single-handedly, launched it themselves, and charges for it themselves; a content creator built a tool site serving only their own niche little need. Three years ago, each of these would have required an engineer, a budget, and a long stretch of waiting.

Those 180 one-person companies at WAIC are mostly the same kind of thing: one person fixated on one specific itch, using AI to fill in the “craft” part, turning it into something launchable that people actually use. Individually they’re small, but together they prove one thing — the line “one person can’t build a complete product” is now void.

Barely any of these people are geniuses. What sets them apart from most people usually isn’t knowing more — it’s that at the “I can’t” moment, they turned and opened the chat box and typed the first sentence.

But there’s one wall AI can’t knock down

Once one wall falls, you quickly discover that the wall actually stopping most people has just moved to a new spot.

Here’s a concrete case: the same idea, put in front of two people.

The first person thinks, “This must require knowing how to code, right? I can’t, so forget it.” And so this idea, to this day, is still in his head.

The second person opens AI and types, “Help me build a little tool that automatically organizes my bookmarks.” Today, that thing is running online, and he uses it himself every day.

These two people both can’t write code. The only difference is one thing: whether they typed that sentence into the chat box — whether they dared to first make something ugly.

Once the technical barrier drops away, what’s exposed is another wall, and this wall is in your head: I’m not good enough, this is too hard, I’m not ready yet, what if what I make is terrible and people laugh. AI can write the code for you. It can’t press “start” for you.

Many “impossibles” are just an assumption no one dared to touch

Look at DeepSeek again. The wall it stepped over had an assumption pressed underneath it: “To build a top-tier large model, you have to do it like the big companies — stack the most chips, burn the most money.” Almost everyone took this assumption as a given, and so “a small team can’t build a good model” naturally became “impossible.”

What DeepSeek did was refuse to accept that assumption. It went and grinded on engineering efficiency, using fewer chips and less money to build a model on par with the top tier. Once it actually did it, that “impossible” wall, looked at in hindsight, wasn’t a capability problem at all — it was that no one was willing to touch that default premise.

Many of the “impossibles” in your head have this same structure. Take one apart and, pressed underneath, there’s often an assumption you’ve never questioned: “you must have A before you can build this,” “someone like me can’t do B.” Pull that assumption out on its own and ask, “Really?” — and the wall often loosens on its own. Stepping over a wall, much of the time, isn’t about how hard you push; it’s about whether you dare to question, “Says who this is impossible?”

What the wall in your head looks like, taken apart

This wall isn’t one you get over with a “be brave.” It’s made of a few very specific bricks. Let me lay them out one by one, and you decide for yourself which one is blocking you.

Brick one: “I don’t understand tech, so this isn’t for me.”

Three years ago this held up; now it doesn’t. Tech is no longer the barrier. What’s actually scarce is whether you understand users and can see the real problem clearly. A person who understands the problem but not the tech, paired with AI, runs far faster than a person who understands the tech but not the problem. Not knowing how to code is, today, even an advantage — you won’t get tied down by “how do I implement this,” and you can keep your eyes fixed on “what does the user actually want.”

Brick two: “I’ll do it once I’m ready.”

You’ll never be ready. In the AI era, the cost of building a prototype approaches zero, and the cost of revising a version approaches zero too. Under this cost structure, building an ugly thing that runs first will always beat thinking about it in your head for three months. In the three months you spend thinking, someone else has revised to version ten and gotten real feedback.

Brick three: “This is so simple, surely someone’s already built it.”

Built doesn’t equal built well, and it certainly doesn’t equal built the exact way you want it. And plenty of things are exactly right when you build them for your own specific little scenario that others look down on. Whether the market is big is an investor’s problem; your own itch is worth an afternoon.

Brick four: “What if what I make turns out terrible?”

The first version should be terrible. The point of building a prototype that runs is to get it moving first and receive real reactions — not to nail perfection in one go. The “terrible” you’re worried about is really you comparing it against the perfect finished product in your head. But the one in your head will never turn real on its own. In the real world, a usable sixty out of a hundred beats an imagined perfect hundred: the sixty can get feedback and grow version by version; the hundred can only sit in place and shine, useful to no one.

Why it had to be now

The “I can’t” wall has actually always been there — it’s been there for decades. Why did it fall these past two years, of all times?

Because AI is the first tool where “you speak plain human language, and it goes to work.” Before it, the things that claimed to help you clear the technical barrier — search, tutorials, low-code platforms — none of them actually got around the “you have to understand a bit of tech first” gate. You find the answer via search, but you still have to understand it; you use low-code, but you still have to grasp its logic. AI is different. It catches your plain language and spits out something that runs. That whole stretch of “you have to learn it first” — it swallowed the entire thing.

What this brings isn’t the barrier being lowered a bit; it’s the nature of the barrier changing: from “learn a craft” to “clearly state a thing.” A dislocation like this comes around maybe once in decades.

And the biggest dividend of a dislocation period has always gone to the ones who dare to act first. Once everyone has caught on and is using it, the dividend flattens out. The people acting now are standing at the starting point of this dislocation. They aren’t smarter — they just swallowed that “I can’t” a little earlier and swapped in “let me try.”

What the people who stepped over it actually did

I’m not going to give you a pep talk. Let me just tell you the common threads I’ve observed in the people who actually “stepped over” — check yourself against them.

One, translate “impossible” into a concrete sentence. “I want to build a tool that automatically organizes my WeChat bookmarks” — as long as you can say it clearly, AI can start working. If you can’t say it clearly, it means you haven’t thought it through yet. That’s “haven’t figured it out,” not “impossible.” Don’t confuse the two.

Two, ask for the ugliest running version first, not the complete solution. A half-finished thing you can click and see results from today beats a perfect plan on paper. The first thing you want has only one standard: it has to run.

Three, change one thing at a time, let AI go step by step. Don’t have it build the whole thing in one shot — that way, when something breaks, you won’t know where the error is. One small change at a time, take a look, then the next step.

These points sound plain. The barrier to actually doing them is just this: open the chat box and type the first sentence.

Back to those two sets of numbers from the start

DeepSeek didn’t win because it had the most compute. It’s that a small handful of people were convinced “we can build a cheaper, smarter model,” and then actually went and did it. Behind each of those 180 one-person companies at WAIC is a thought — “one person… could actually work?” — that someone pressed start on.

What stands between you and these things is no longer whether AI can do it — AI already can, and can do far more than you think. What stands in the way is whether, the moment you say “I can’t, I’m not good enough,” a single action follows right behind it: saying it to AI.

That wall has always been in your head. AI knocked down the one next to it and cleared away “I can’t”; but the one that reads “I’m not good enough,” it can’t knock down — only you can step over that one. And the first step over is so small it barely looks like a step: open that chat box, and tell it, exactly as it is, the “impossible” you’ve been holding in. The rest, it takes from there.