I do not mean that as hype.
I mean it in the most literal sense.
Over the last three months, in the hours after my three children went to bed, I found myself doing things that would have felt wildly disproportionate not very long ago.
- I hosted a large language model on my home PC
- I built an agentic system that handles real day-to-day work
- I built a functional application that I expect to release within the next month
Not in a lab.
Not with a team.
Not with institutional backing.
At home. At night. In the margins of ordinary life.
Somewhere in the middle of this—between iteration and fatigue, between curiosity and momentum—I had a realization I have not been able to shake:
This should not be possible.
But it is.
The Structure Is Changing
For years, the ability to build software at speed was gated by a familiar set of constraints:
- technical specialization
- access to engineering bandwidth
- sufficient capital to buy time
- institutional processes designed—intentionally or not—to slow things down
That structure created companies, defined careers, and shaped entire industries.
What is changing now is not simply that the tools are improving.
It is that the structure those tools depended on is beginning to erode.
The Collapse of Distance
The cost of turning an idea into a working system is collapsing.
The distance between imagination and implementation is shrinking.
And the amount a single determined person can build in a week is beginning to exceed what most organizations are designed to absorb without friction.
This is why much of the current discussion around AI feels slightly misaligned.
The question is no longer whether the models are impressive, or whether adoption is real.
The more consequential question is:
What happens when individuals can design, build, test, and deploy systems faster than the institutions around them were designed to accommodate?
Where the Tension Appears
Inside organizations, this does not present as transformation at first.
It presents as tension.
- workflows begin to feel slower than they should
- approval layers feel more expensive than they are justified in being
- roles built around the management of information begin to lose their logic
- software categories that relied on complexity as a moat begin to look exposed
The bottleneck begins to move.
It is no longer access to capability.
It is the ability of the organization to reorganize itself in response to that capability.
Not a Model Problem
This is why enterprise AI adoption is often framed incorrectly.
It is not primarily a model deployment problem.
It is a workforce design problem.
The real question is not who has access to the best models.
It is:
- who can rethink roles
- who can redefine decision rights
- who can restructure workflows
- who can accelerate operating cadence
fast enough to make use of what those models now enable.
It Is Not Contained
If this were limited to well-funded engineering teams, it would be easier to contextualize.
But it is not.
It is happening:
- in living rooms
- in spare hours
- in the margins of otherwise full lives
It is happening in a way that does not ask for permission before it begins.
That is the part that should give people pause.
Because if one person, working at night, can now build systems that previously required coordination, budget, and institutional approval—
then the distribution of leverage is changing.
Speed and Discipline
I feel this particularly clearly as an American living in Europe.
There are two instincts:
- one favors speed — experimentation, iteration, forward motion
- one favors discipline — governance, structure, second-order awareness
For a long time, they have existed in tension.
Increasingly, it feels as though both are required.
- speed without discipline introduces fragility
- discipline without speed introduces irrelevance
The individuals and institutions that navigate this shift will not choose between them.
They will integrate both.
The Real Scarcity
As access to capability broadens, the scarce resource is no longer the ability to produce code.
It is the ability to decide:
- what should be built
- how it should be built
- why
Imagination becomes more valuable.
Judgment becomes more valuable.
Taste becomes more valuable.
System design—and the willingness to act without waiting for translation or approval—becomes the differentiator.
The divide that is emerging is not simply technical vs non-technical.
It is:
those who can convert intention into systems directly
and those who remain dependent on layers of mediation
That is not a small shift.
It is a structural one.
Closing
I am not writing this as a distant prediction.
I am writing it because I encountered a small version of it firsthand—and it was enough to change how I think about what comes next.
If this trajectory continues—and there is little reason to believe it will not—
then a meaningful portion of how we build software, organize work, and structure companies will be redefined.
Not all at once.
Not evenly.
But with a kind of uneven acceleration that looks gradual—
until it is not.
Most institutions are not ready for that.
Not because they are incapable.
But because they are optimized for a world in which this level of individual leverage did not exist.
That world is beginning to recede.
And whatever replaces it will not ask for permission to arrive.