ASTRA DESIGN
OAKWEB.AI AI news & understanding
The First Domino / an interactive essay
OAKWEB FIELD NOTES01 / CREATION & CONSEQUENCE

The First
Domino.

The printing press, AI coding,
and what happens when
more people can create.

When the tools of creation change, what becomes possible?

01 / THENGUTENBERG-ERA EUROPE
WOOD. INK. POSSIBILITY.MAINZ · c. 1450s
One idea, waiting to become many pages.
02 / NOWAI-ASSISTED SOFTWARE
● ● ●the next useful thing↗
YOUR IDEA / a place to begin
✳

Make a tool to track repairs
and schedule a visit.

↵
01 const idea = “something useful”;
02 await build(idea);
03 // a proposal, ready for your judgment
YOUR NEXT IDEA
A starting point. A person takes it further.
One need, waiting to become a useful tool.

Inspired by an analogy from Boris Cherny,
creator of Claude Code at Anthropic.

FOLLOW THE FIRST DOMINO 6 CHAPTERS · TAKE YOUR TIME
02 / BEFORE THE MACHINE

The work
limits the reach.

A skilled hand. A thoughtful builder. When making something takes substantial time and specialized labor, fewer projects can be attempted.

THE SCRIBE’S DESKA page, line by line
ONE COPY. MANY CAREFUL HOURS.
Copying a manuscript takes care and time. Every additional copy asks for that labor again.
THE BUILDER’S DESKA tool, piece by piece
↳Understand the needWho reports a repair? Who schedules it?01
{ }Build the behaviorRequirements → data → interface02
function schedule(request) {
  return { ...request,
    status: "scheduled" };
}
☑Check the resultDates, permissions, edge cases03
Still to make
Software combines decisions, implementation, and checks. Even a small, useful idea can wait in the queue.
I

The first parallel: a production bottleneck becomes less restrictive.

03 / THE MECHANISM CHANGES

A new way
to make.

Reusable type makes another impression possible. A written request gives software a starting point. Watch the page become a tool.

1. Reusable type is arranged.
2. The press produces a sheet.
3. The sheet becomes a software preview.
THE REQUEST

“Make a repair tracker.
Let me schedule a visit.”

01 A proposed implementation
02 A visible preview
03 A human review
● ● ●repairboard.local↗
RepairboardA little less chasing.DEMO
Open requests1Scheduled0
↗
Leaking kitchen tapUnit 04 · Reported by a resident
ReportedNo appointment yet

Try it. Make one everyday task easier.

  1. 01Set the typeArrange a reusable pattern.
  2. 02Make an impressionThe press produces a page.
  3. 03Turn the pageType becomes code, then an interface.
  4. 04Try the toolSchedule the repair above.

Different mechanisms, a shared opening: printing reproduces text; AI generates and modifies software. The software still needs judgment, review, and maintenance.

04 / MORE PEOPLE, MORE POSSIBILITIES

What happens when
more people can build?

The larger story is who gets to participate—and what they do with the opportunity.

In Gutenberg-era Europe and the centuries that followed, printed books circulated into more settings.
A CHANGE THAT TAKES TIME

A machine is
only the beginning.

Printers, booksellers, teachers, readers, and institutions helped turn reproducible pages into access to knowledge. Learning to read and obtaining books still mattered. The benefits were uneven, and the changes were not instant.

For software, access also means skills, affordable tools, and support. The possibility is more people making something useful for their own lives.

THREE PEOPLE. THREE EVERYDAY NEEDS.Small working demos · try the controls
A

A teacherA plan that fits her classroom.

01
Lesson notes
30 MINUTES · CLASSROOM PLAN
  1. 5 min · Look closely at a seed.
  2. 15 min · Draw what a plant needs.
  3. 10 min · Compare ideas together.

More time for the students in front of her.

J

A shop ownerA clearer picture of the shelves.

02
The corner shop
House olive oil500 ml · Pantry
ON THE SHELF4Running low

A delivery is ready to check in.

Know what’s available before a customer asks.

M

A property managerA repair with a next step.

03
Repairboard
UNIT 04

Leaking kitchen tap

The resident needs a visit.

ReportedScheduled

No appointment yet

A resident knows when help is coming.

Illustrative tools, not live services. These demos use fixed sample data and make no AI calls.

II

Lower barriers.
Broader participation.

The two parallels: printing and AI-assisted software
PrintingAI-assisted software
Less labor to reproduce textLess manual work for some implementation tasks
Written material can circulate more widelyMore people can attempt useful software projects
New uses of accessible knowledge emerge over timeNew uses of accessible software creation may emerge
05 / THE HUMAN PART

The tools change.
Judgment matters.

Knowing what to make, checking whether it works, and deciding whom it serves remain human responsibilities.

A READER’S COPY

A useful idea
deserves a
second look.

Every request should be
scheduled immediately.

At a time the
resident can make.
A reader questions the text. An editor corrects the line. Reproduction does not guarantee truth.
HUMAN REVIEW01 COMMENT
P

A requirement we missed“Only schedule a visit when the resident’s availability is confirmed.”

Check failedA visit can be scheduled without confirmation.

One human question makes the tool more useful.

An ink annotation becomes a review comment.
The responsibility stays with people.

06 / THE FIRST DOMINO

What does
this unlock?

The first change is easier to see.
The possibilities beyond it are the interesting part.

THENA simplified chain.
Not a single cause.
  1. Cheaper
    reproduction
  2. Wider
    circulation
  3. New uses
    of knowledge
NOWPossible next steps.
An open horizon.
  1. Easier software
    creation
  2. More people
    experiment?
  3. More needs
    get a tool?
  4. Something we
    can’t yet name?
LOOK A LITTLE FURTHERQuestions, not forecasts.

What everyday problems could people solve with tools they make themselves?

What new ways of working could grow from broader access to software creation?

What uses are we unable to imagine today?

The story is not just what the machine can make.
It is what people can make possible.

Back to AI news & understanding

Notes & sources

Illustrations created with Higgsfield for Astra Design. Interpretive artwork; not archival images.

An editorial analogy, not a claim that two technologies—or their histories—are the same.

  1. Computer History Museum · In Conversation with Boris Cherny

    CHM’s account of its September 23, 2026 conversation with the creator of Claude Code at Anthropic. Cherny’s analogy and expectations are paraphrased here as his perspective; no direct quotation or timestamp is claimed.

  2. Library of Congress · The Gutenberg Bible

    Context for movable metal type and Gutenberg’s work in Mainz in the 1450s. This feature concerns Gutenberg-era Europe, not the beginning of printing worldwide.

  3. Europeana · Europe’s first printed book

    Early printed books, their manuscript traditions, and the spread of the printing process. Access expanded over time; machinery alone did not create universal literacy.