Part 2 of 3…
It is eleven-thirty on a Tuesday night and she is arguing with a language model about a spreadsheet.
Not arguing, exactly. That’s not the right word. She is coaxing. She is debugging. She is reading error messages that tell her almost nothing and rewriting prompts that almost work, and she has been doing this for two hours, and the spreadsheet still isn’t right, and she is going to try one more thing before she gives up and does it by hand. She is a data analyst at a mid-sized logistics company in Columbus, Ohio. She is not a researcher. She is not a founder. Nobody is writing about her. She is just a person trying to get a machine to do something useful, and the machine keeps almost doing it, and she keeps learning, in the gap between almost and done, something she couldn’t have learned any other way.
She doesn’t know what she’s learning. That’s the important part.
In 1892, two brothers opened a bicycle repair shop on West Third Street in Dayton, Ohio. The bicycle craze was at its peak — the safety bicycle, with its two equal wheels and chain drive, had just replaced the penny-farthing, that absurd high-wheeler everybody called loose change and the riders, with complete seriousness, called the ordinary. The brothers fixed flats and adjusted brakes and built custom frames and ordered parts from Coventry and kept the books and swept the floor. It was ordinary work. Nobody was writing about them either. What they were doing was accumulating, without knowing they were accumulating, a physical understanding of how machines move through space — the gyroscopic principles, the weight distribution, the thousand small calibrations that kept a rider from falling. They were learning in their hands what no university taught and no book fully contained.
Eleven years later they flew.
We tell the Wright Brothers story as a story about flight. It makes sense — flight is the thing, the miracle, the moment the world changed. But the actual story, the one that explains how Kitty Hawk was possible, is a story about a bicycle shop. It is a story about unglamorous preparatory work, about the education that hides inside the constraint, about what you learn in the gap between the machine that exists and the machine that should exist. Orville and Wilbur didn’t go to Kitty Hawk despite the bicycle shop. They went because of it. The shop was the point. They just didn’t know it yet.
We are in the bicycle shop right now.
The people building with AI today — the prompt engineers, the fine-tuners, the agent builders, the data analysts in Columbus arguing with spreadsheets at midnight — are doing work that looks, from the outside, like mere tinkering. Unglamorous. Iterative. Full of failure. The tools are awkward. The models hallucinate. The context windows run out at the wrong moment. Every solution opens three new problems. It feels like the penny-farthing: powerful enough to be useful, constrained enough to be maddening, requiring a kind of practiced vault just to get started.
But that awkwardness is the education.
Every time a prompt fails, the person writing it learns something about how the model thinks — about what it responds to, what it resists, where it gets confused, where it surprises you. Every agent that breaks in production teaches its builder something about the gap between what a model can do in a demo and what it can do under load, with real data, with users who don’t behave the way you expected. Every context window that runs out forces a decision about what actually matters, what is essential, what can be cut. These are not just technical lessons. They are epistemic ones. They are lessons about the nature of intelligence, about how meaning gets encoded and retrieved, about what it means for a machine to understand something versus to pattern-match on the surface of understanding.
The people learning these lessons right now don’t have a name for what they know. They just know it in their hands.
This is how it always works. James Starley’s craftsmen in Coventry bent and brazed bicycle frames by feel and experience, knowing things in their hands they couldn’t fully explain on paper. That embodied knowledge — the tight tolerances, the interchangeable parts, the discipline of making things that had to work — migrated into every bicycle shop that followed, crossed the Atlantic, and ended up in a shed in Ohio. The Wright Brothers didn’t invent precision manufacturing. They inherited it, absorbed it, and applied it to a problem nobody else had solved because nobody else had brought those particular hands to that particular problem.
The chain drive was the hinge. Before it, the bicycle’s design was locked — bigger wheel for more speed, higher and higher off the ground, until the machine teetered at the edge of what a human could survive. The chain drive broke the constraint. It decoupled the pedals from the wheel, let the gearing do what only size had done before, brought the rider back to earth. What had been a machine for athletes became a machine for everyone. What had been the ordinary became, almost overnight, something new.
We are waiting for the chain drive.
Not waiting passively — it is being built right now, in a hundred places at once, by people who mostly don’t know they’re building it. It might be the interface that finally makes AI genuinely accessible to people who can’t do the running vault. It might be the memory architecture that lets a model carry context the way a human carries context, not in a window but in something more like experience. It might be something nobody has named yet, something that will seem obvious afterward, the way all elegant solutions seem obvious after the fact.
What it will not be is the product of people who stayed away from the bicycle shop.
The analyst in Columbus closes her laptop at midnight. The spreadsheet is still not right. She has learned three things about how the model handles date formatting, two things about how it interprets ambiguous column headers, and one thing about her own assumptions that she didn’t know she was making. Tomorrow she will try again. She will get closer. At some point — not tomorrow, maybe not this year — she will get it right, and the thing she learned in the gap will be available to her for the next problem, and the one after that, and she will carry it forward without knowing she’s carrying it, the way craft always travels, in hands that have done the work.
She doesn’t know what she’s riding toward.
That’s the ordinary part. That’s always been the ordinary part.
You must be logged in to post a comment.