The dynamics that dismantle feudalism
In the previous chapters we saw the feudalism the IT revolution built, and the self-destruction of its lord class (Big Tech). This chapter analyzes the dynamics that technically dismantle that feudalism — the structural action of the AI revolution.
Medieval feudalism was dismantled by several overlapping factors — the failure of the Crusades, the great plagues, the arrival of the printing press, the development of banking, the discovery of the New World. The main dynamic dismantling the feudalism of the AI era is the disappearance of translation labor, brought about by AI-native substrates plus LLMs.
Let us look structurally at how this dismantles the hierarchy and brings a new class — the builder — to the fore.
The disappearance of translation labor breaks the hierarchy
As we saw in Part 2, Chapter 6, 70–80% of software development was translation labor. When AI-native substrates plus LLMs erase it, the economic base of feudalism disappears:
AI-native substrate (Markdown, DataFrame, JSON, Parquet) + LLM
→ translation labor disappears (70–80% becomes unnecessary)
→ a 30-person project is done by 1–3 people
→ a large vassal class (engineers) becomes unnecessary
→ hierarchical management (VP, Director, PM) becomes unnecessary
→ the economic rationale for maintaining a large organization disappears
→ Big Tech's "hold a huge retinue of vassals" model collapses
This is structurally the same as the late medieval situation where "the plague slashed the labor force, and the bargaining power of serfs rose." When labor demand changes, hierarchical domination collapses.
In the case of the AI revolution, labor does not "decrease" — it "becomes unnecessary." But the result is the same: when the scarcity of labor changes, the lord–vassal relationship changes.
The vassal class can break free of the lords
When translation labor disappears, engineers (the vassal class) become structurally able to break free of the lords:
| Old structure (IT-revolution feudalism) | New structure (after the AI revolution) |
|---|---|
| 30 people per system → a large organization is needed | 1–3 people per system → an individual completes it |
| translation-labor specialists form a hierarchy | a specialist hierarchy is unnecessary |
| the lord (Big Tech) monopolizes job opportunities | individuals pair with AI to create value directly |
| a vassal cannot move without the lord's permission | a vassal can migrate to a free city |
| advancement = promotion within a larger organization | advancement = becoming independent and building your own domain |
What matters most is that "an individual vassal can now create value directly, without going through the lord's organization." Until now:
- For one engineer to create value, the organization's servers, the organization's data, the organization's team, and the organization's customers were all required.
- Whatever you built alone could not reach scale, was hard to distribute, and was hard to monetize.
But in the AI era:
- One person + AI + Linux + Python + cloud (at an individual level) can hold capabilities equivalent to a company's.
- AI doubles as sales, development, design, operations, documentation, and support.
- Internet distribution can reach customers on a global scale.
- The structure described in Part 2, Chapter 1, "AI and the Individual Business," becomes technically feasible.
Migrating to the free cities — Linux + Python + AI
At the end of the medieval period, merchants, craftsmen, and intellectuals left the manors and gathered in the free cities (the Hanseatic cities, the northern Italian cities, the cities of Flanders). In places beyond the reach of the lords' rule, they built their own economy and culture, and ultimately became the bearers of the Renaissance.
The free city of the AI era is the combination of Linux + Python + AI:
OS → Linux (Debian, Ubuntu in particular) — not owned by Big Tech
Language → Python (run by the PSF, no vendor) — not owned by Big Tech
Substrate → Markdown, JSON, YAML, DataFrame, Parquet, SQLite — open formats
AI → Claude and other LLMs (several companies competing, lock-in avoidable)
Tools → Zed, Neovim, VS Code, Git, uv, ruff, ollama
Distribution → GitHub, PyPI, Flathub, your own domain
None of these are the property of any particular lord (Big Tech). Python belongs to a nonprofit foundation, Linux to a community, Markdown is a spec, AI is contested among several companies. They have the independence that deserves the name "free city."
For an engineer to migrate to this free city means leaving feudalism and building a new economy. This is not "fleeing"; it is "forming a new class."
The builder as a new class
The vassal class that has migrated to the free cities is no longer a vassal class. It is reconstituted as a new class — the builder:
| Software engineer (vassal) | Builder (free citizen) |
|---|---|
| carries translation labor | operates the substrate directly |
| part of a hierarchy | self-contained alone |
| closed inside a specialty | integrates business + technology |
| language: Java / C# | language: Python + AI |
| substrate: primitive types | substrate: Markdown / DataFrame / JSON / Parquet |
| project size: 30 to several hundred people | project size: 1 to a few people |
| subordinate to the lord | parallel to the lord, or independent |
| career: promotion | career: independence / founding / self-employment |
A builder is an individual who, by operating the AI-native substrate directly, can complete the work without going through a translation laborer — this is the structural definition.
On the surface this resembles "freelancer," "sole proprietor," "indie hacker," but structurally it is a different thing. A freelancer is merely one form of the vassal class, working on top of Big Tech's platforms (Upwork, Fiverr, etc.). A builder holds their own domain, independent of the platform — this is the decisive difference.
This rise can already be observed concretely. Boris Cherny, who built Claude Code, calls himself a "builder" and has not written a single line of code by hand since November 2025 — "Coding is solved," he says. The third generation of a family that wrote code by hand, a man who even authored a textbook on a programming language, stopped writing. And moving translation labor (coding) to AI does not make people unnecessary. Anthropic, the company that builds Claude, has AI write much of its code and yet has grown its headcount nearly tenfold in three years, directing much of it to research, safety, and engineering — the frontier where no one has yet written the answer. As the writable work moves to AI, people head for the places not yet written — the rise of the builder is exactly this migration (With AI, You Can Build an App Through Dialogue Alone).
The structural ground of the Second Renaissance
The rise of the free cities at the end of the medieval period became the physical base of the Renaissance (the cultural and intellectual revival of the 14th–17th centuries). Without the free cities, Galileo, Leonardo, and Machiavelli could not have worked — they were all in free cities or comparable environments.
In the same way, the free city of the AI era (Linux + Python + AI) becomes the physical base of the Second Renaissance:
1. A place beyond the rule of lords and church (the free city)
2. A means of accumulating and circulating knowledge (manuscript → printing press)
3. A means of economic independence (commerce, banking)
4. An environment where diverse people gather (exchange among cities)
5. The technology and thought that support all of these
[The AI-era counterparts]
1. → Linux + Python + AI (beyond Big Tech's rule)
2. → AI + Markdown + Web (accumulation and circulation of knowledge)
3. → individual business + AI + the internet (economic independence)
4. → open source, independent media, Substack, etc. (diverse exchange)
5. → AI-native ways of working
Just as the Renaissance did not "completely negate" the medieval period but dismantled the medieval class structure while inheriting its legacy (classical texts, technology, organization), the Second Renaissance also:
- the cloud infrastructure Big Tech built → use it (but are not owned by it)
- the AI Big Tech trained → use it (but do not depend on it)
- the code the IT revolution accumulated → learn it (but rewrite it on the new substrate)
- existing software-engineering knowledge → inherit the necessary parts (but most becomes unnecessary)
Inheriting while dismantling — this is the structure of a Renaissance.
Builders solidarize beyond the individual business
Builders are sole proprietors, but they are not isolated. Just as the citizens of a free city solidarized with one another, builders too solidarize in a new form:
Open-source projects → share code and cooperate
Open standards → share formats and secure interoperability
Independent media → share insight and learn from one another
Individual collaboration contracts → team up per project as needed
Local communities → physical study groups, co-working
This differs from medieval guilds and from modern corporations alike. Equal citizens, subordinate to no lord, solidarize as needed — this is the new organizational form.
What is especially important is that they do not chase scale. Builders do not set "growth" as a goal. They collaborate at the necessary scale for the necessary period, and disband when it is over. They do not pay the maintenance cost of a permanent large organization — this is the builder's economic advantage.
The final position of the lord class
In the course of feudalism's dismantling, the lord class does not vanish entirely. Just as the medieval nobility, even after the Renaissance, kept nominal authority while gradually ceding real power to the merchant class, Big Tech too:
- its existing services keep running (Windows, Office, Google Search, Amazon shopping)
- but new value creation happens on the free-city side (the builders)
- Big Tech remains as "infrastructure provider" and "ad distributor," but is no longer the center of innovation
- its market capitalization gradually shrinks (as the rent income of the medieval nobility was relativized by the Industrial Revolution)
This is not "Big Tech goes bankrupt"; it is the process by which "Big Tech's centrality fades." In the history books a hundred years from now, the protagonists of the AI era are likely to be recorded not as Big Tech CEOs but as the individual builders who worked in the free cities (the Galileo equivalents).
The dismantling is not fast, but it is irreversible
The dismantling of feudalism took centuries. The dismantling of AI-era feudalism, too, will not happen overnight. Big Tech is large and its inertia is strong. Microsoft and Google will persist on a decade scale.
But the direction is irreversible.
| Structural pressure | Effect |
|---|---|
| maturation of the AI-native substrate | translation labor technically disappears |
| improvement in LLM capability | the range of an individual's capability expands |
| accumulation of open source | the foundation of the free city thickens |
| self-destruction of the lord class | Big Tech crumbles from within |
| the collision of resource shocks and AI CAPEX | the legitimacy of the enclosure strategy is lost |
| the becoming-visible of the Second Renaissance | builders gain social recognition |
These pressures act in combination, and the class structure changes over a span of 10 to 30 years — this is the realistic estimate.
The chapter's conclusion — builders rise structurally
The dynamics of the AI revolution technically dismantle the feudalism of the IT revolution. This is not an ideology but a structural fact. Translation labor disappears, the vassal class can break free of the lords, and a new class (the builder) rises by migrating to the free cities.
This is a historical turning identical in structure to the transition from the medieval to the early modern period. Not a metaphor — a structural isomorphism.
When AI-native substrates plus LLMs erase translation labor, the hierarchy of the IT revolution collapses.
The vassal class (engineers) becomes able to break free of the lords (Big Tech).
Linux + Python + AI becomes the free city (a place beyond the lords' rule).
The individuals who migrate there are reconstituted as a new class — the builder.
This is the structural ground of the Second Renaissance.
Not a metaphor — it is proceeding as a structural isomorphism.
The next chapter takes up what individuals should concretely do within this structural change. It lays out the staircase for stepping away from the class, as a combination of concrete tools and choices.