The Age of the Creator Is Falling

Knowledge used to be expensive. Not in money — in time and patience.

When I started, learning something meant going to a library. You found a book, and then you read it. Not the paragraph you needed — the book. You sat with it, you were patient, and if you were lucky, somewhere on page two hundred was your answer. If you were unlucky, you finished with a head full of facts that you might use one day, or might never use at all. Either way, the cost was paid up front, in hours.

Then came the internet, and the price dropped. Google, forums, Stack Overflow. Someone had already asked your exact question, and someone else had already answered it. You didn't need the book anymore; you needed the paragraph. You could find not just an explanation but a recipe — the precise steps to build the precise thing you wanted to build.

Now there is AI, and the price has dropped again. You don't even need to find the paragraph. You ask, and the answer is assembled for you, in your own words, at your own level.

Here is what I think this really changes.

The creators get younger — again

This is not a prediction. It is a pattern that has already run twice, and we are watching it run a third time.

In the library era, a creator was an adult. To build something real you first spent years collecting knowledge, usually inside an institution that gave you access to it. The price of knowledge was the price of entry, and children could not pay it.

Then the internet made it cheap, and the age fell. Teenagers started shipping products that people actually used. At first this was news — the teenage founder was a story. Then it stopped being a story, because it stopped being rare. A sixteen-year-old with a laptop had the same recipes available as a company with a research department.

Now AI drops the price again, and the age falls again. The last barrier was not knowledge but the effort of assembling it — knowing where to look, filtering the noise, translating a general answer into your specific case. That work is now done on request, in plain language, adjusted to whatever you already understand. A twelve-year-old can hold a full conversation about a thing they knew nothing about an hour ago, and come out of it with working code.

So the honest question is not whether this happens. It is: what gets built when it does?

The ideas change, not just the speed

People imagine young creators making the same products faster. I think something more interesting happens: the products themselves change, because ideas come from the life the creator is living.

Adults built software for the world adults live in. Offices, invoices, logistics, meetings. When the age dropped to students, we got products shaped by student life — campus networks, chat, sharing music, staying up late together. Not because young people were cleverer, but because those were the problems in front of them.

Drop the age again and you get a different set of problems entirely. School. Games. Boredom. Friendship. Fairness on a playground. Things adults either consider trivial or stopped noticing thirty years ago. Some of it will be nonsense. Some of it will be a category nobody thought to build, because nobody in the room had that problem anymore.

Why that produces better things, not worse

The usual reaction to this is worry: children building things without wisdom, without knowing the risks.

I want to argue the opposite. A young creator builds toward the bright side, because the bright side is all they see. They haven't collected the scars yet — the bad job, the failed product, the user who was hurt. So they build the thing that shouldn't be possible, and sometimes it works.

Experience does teach care. But it also teaches fear, and fear arrives early in the design process, when the product is still small enough to be killed by it. If you begin already knowing every way a thing can go wrong, you build walls before you build the thing. You add the rules, the warnings, the agreements, the protections — and you protect your bright idea so well that the world never gets to see it.

The better order is the natural one: build the bright thing first, let the downsides appear as real problems rather than imagined ones, and by the time they arrive you have grown strong enough to defend the bright side properly. You grow with your product. The naive version comes first, and the wisdom is added by the world.

Cheap knowledge, then, isn't just a convenience. It hands the tools to the people least likely to talk themselves out of using them. And that is a good trade.