Printing Press Software Democratization

Sources#

• Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next

Summary#

Boris Cherny's offered analogy for what AI is doing to software: the invention of the printing press in 1400s Europe. Pre-press literacy was ~10%; literates were employed by mostly-illiterate kings and lords. Within 50 years of Gutenberg, more books were printed than in the previous thousand years combined; book cost dropped ~100×. Over the next few centuries, literacy reached ~70% globally. Boris claims software writing is at the same inflection point — the cost of producing software collapses, the skill becomes general, and the bottleneck moves from coding to domain knowledge.

The analogy in Boris's words#

"Before the printing press, essentially 10% of the European population was literate. They knew how to read and write. They were often employed by like kings and lords that were not literate."

"The printing press was invented, then there were two more presses, and in the 50 years after the first printing press, there was more literature published in Europe than in the thousand years [before]."

"Software will be a thing that is fully democratized, that anyone can do."

"The best person to write accounting software, I think maybe even today, is not an engineer, it's a really good accountant because they know the domain really well and coding is the easy part."

What the analogy claims#

1. Cost of production collapses. Software, like books after the press, becomes cheap to produce.
2. Skill diffuses. Software writing was a specialized skill, like literacy in 1400; it becomes general.
3. Domain knowledge becomes the differentiator. Once literacy is universal, what you write about matters more than the act of writing. Once coding is universal, what you build for whom matters more than coding skill.
4. Faster than 50 years. Boris's caveat: "much faster than 50 years." Diffusion timelines for tech in 2026 are months, not centuries.

Where the analogy bites#

• Education systems took centuries to catch up to mass literacy. Schools built around the assumption "most students can't read at home" had to be rebuilt. There's no obvious analogue ready for "most people can build software." Boot camps, computer-science curricula, and engineering ladders all assume scarcity of coding skill that may not hold.
• Professional writers still exist after universal literacy. "Now we can all read and write… [but] still there are professional writers and that is a thing that you can do." Boris implies professional engineers will still exist post-democratization, just as professional authors do — but the baseline shifts.
• Literacy didn't replace lords. Mass literacy didn't disempower the literate elite — it changed which skills were premium and shifted them upward. Boris's implicit bet: the value migrates from "can write code" to "can decide what to build" — see Engineer PM Convergence.

Where the analogy strains#

• Books are static; software is dynamic. A book once printed sits there. Software needs to be maintained, secured, scaled. "Anyone can write software" doesn't say anyone can run software in production reliably.
• Software has compounding network effects books don't. A single book doesn't depend on other books in the way most software depends on other software. The analogy underweights infrastructure / dependency / interop.
• Reading is one-way; software has stakeholders, users, attackers. Universal authorship of software at scale raises questions (security, accountability, regulation) literacy didn't.
• The "accountant writes accounting software" claim is testable now. Boris implies we're already seeing it. Hard data on how often this works in 2026 isn't in the source — but Cat Wu's parallel point about engineers-with-product-taste suggests the integration of domain + coding is the real lever, not pure non-engineer authorship.

Implications Boris draws#

• Best time to be a startup. Tiny teams compete head-to-head with incumbents because incumbents have to retrain people / change processes / overcome internal resistance — a startup builds AI-native from day one (see Seven Powers Applied to AI).
• 10× more disruption-grade startups in next 10 years. Boris's prediction.
• Boris's predicted next form of value: people with deep domain knowledge who can now also build software. Accountants, doctors, lawyers, teachers — domain experts authoring tooling for their own domains, not waiting for SaaS.

Connections#

• Boris Cherny — author of the framing
• Seven Powers Applied to AI — companion analysis of which moats survive
• Engineer PM Convergence — same direction at smaller timescale (within companies, roles merge)
• Claude Character as Product — once anyone can build, soft attributes (taste, character) differentiate
• Harness Shrinkage as Models Improve — the harness shrink is one slice of the same diffusion: software-of-software gets simpler too

Open questions#

• Is domain-expert-as-builder actually happening at scale in 2026? Anecdotes (shop owners, microcontroller hobbyists) yes; primary-job software building by non-engineers, less clear.
• What's the equivalent of compulsory schooling for universal coding literacy? Or does that not happen and we get a long tail of self-taught builders?
• Boris's "accountant writes accounting software" — does that result in 10K narrow tools that don't interoperate? What's the integration story?

Derived#

• Learning to Co-Work with AI: A Software Engineer's Field Guide — applies the democratization thesis to individual-engineer skill development (domain depth + cross-disciplinary range as the new differentiator)
• Opinions on Using AI Tools & the Future of the Software Engineering Role — uses this analogy as the "bullish insider" stance and as the macro driver behind the future-role section

Sources#

• Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next