Categories
AI Apple Bicycles History

The Best Lathe in the Shop

Part 3 of 3…

There is a version of this story where Apple is the Wright Brothers.

It is not an unreasonable version. Apple has done the safety bicycle move more times than almost any company in history — taken a technology the engineers built for engineers and brought it down to earth, made it a machine for everyone. The Mac. The iPod. The iPhone. Each one was a wheel coming down. Each one arrived after a period of apparent slowness, of critics saying Apple had lost its edge, of the industry having already moved on to the next thing. Each one was, in retrospect, obvious. Apple had been in the bicycle shop the whole time. You just couldn’t see what they were building.

So when Apple showed its hand at WWDC this week — a rebuilt Siri operating at the OS level, accessing your messages and mail and photos in real time, understanding context across apps, doing things the old Siri could only approximate — it is tempting to read it as Kitty Hawk. The long preparation made visible. The brothers finally leaving the shop.

It might be. It also might not be. That is the only honest thing to say.

What Apple showed was real. The new Siri, built on Apple’s own Foundation Models with help from Google’s Gemini, is not the Siri that became a punchline. It holds context. It moves across apps without being asked. It knows what you were doing five minutes ago and connects it to what you are doing now. It can surface a photo without opening Photos, build a navigation route from an image, draft a message in the tone of the conversation it is joining. These are not features. They are the beginning of an operating system that understands you, which is a different thing from an operating system that executes your commands.

The structure of the keynote said more than the words did. Apple led with fixes before features. iOS 27 is a Snow Leopard update — performance, reliability, the underlying machinery — and Siri AI was presented as one item on a long list rather than the main event. This is Apple’s tell. When they are doing something foundational they tend to understate it, the way a craftsman doesn’t announce the quality of his work but simply does it and lets you find it. The penny-farthing riders called their machine the ordinary. They didn’t think they needed to explain.

But here is the thing about the bicycle shop analogy that the optimistic version leaves out. The Wright Brothers knew what they were trying to build. They had been thinking about flight for years before Kitty Hawk. The bicycle shop gave them the craft knowledge, the physical intuition, the hands-on education in how machines move through space. What it did not give them was the destination. They brought the destination themselves.

The question Apple has not answered for me — the question this week’s keynote raised rather than resolved — is whether they know where they are going. Or whether this has only been a partial reveal and there’s much more behind the curtain?

The OS-level integration is the chain drive. Decoupling AI from the app, letting it run through the substrate the way a chain runs through a drivetrain, is exactly the kind of architectural insight that changes what a machine can do. It is not a feature you add. It is a rethinking of what the machine is for. Every previous AI assistant lived above the operating system, looking down at your data from a remove. Apple’s new architecture lives inside it, which is a different relationship entirely — the difference between a mechanic who reads about your car and one who has driven it for a year.

That is the Coventry precision. The tight tolerances. The discipline of making things that have to work at the level where failure is not an option.

What nobody knows, including Apple, is what you build with it.

There is also this: Tim Cook will not be driving this evolution. He announced that John Ternus takes over in September, which means this WWDC — this particular showing of the hand — is the last one Cook owns. Ternus is a hardware engineer, the man who built the Apple Silicon transition, the person most responsible for the Neural Engine that makes on-device inference possible. He is, in the bicycle shop metaphor, the craftsman who built the lathe. Whether he knows how to use it to make something that flies is the question the next several years will answer.

History is patient about these things. It lets the work speak.

In 1892, two brothers opened a shop on West Third Street in Dayton and started fixing bicycles. They were not trying to change the world. They were trying to make a living, to learn a machine, to understand in their hands what the books couldn’t teach them. The flying came later, and it came because of the shop, not despite it. The shop was the point. They just didn’t know it yet.

Apple has the best lathe in the bicycle shop. They have the chain drive architecture, the on-device precision, the installed base of two billion devices that will carry whatever they build into more hands than any other platform on earth. They have a new set of hands on the wheel starting in September, hands that know the metal intimately, that built the engine the whole thing runs on.

What they do not have yet — or if they have it, they are not showing it — is the image of what they are flying toward.

Maybe that’s the ordinary part. Maybe that’s always been the ordinary part. You don’t know what you’re building until you’ve built it, and by then the world has already changed, and everyone says it was obvious, and they are right, and they are also completely wrong about when the decision was made.

The shop is open. The lathe is running. Work is underway.

What happens when someone finally knows what to make?

Categories
Apple Business

The Architecture of Subtraction

Hold an iPhone in your hand, or run your fingers along the cold, machined edge of a MacBook. What you are feeling isn’t just glass and aluminum; you are feeling the physical manifestation of a thousand invisible rejections.

We are conditioned to think of creation as an additive process. But true institutional excellence operates in reverse. It is an act of relentless, unsentimental subtraction.

A few years ago, Tim Cook articulated what became known as the “Cook Doctrine.” It is meant to answer the existential question of what makes Apple, Apple. Reading through it, what strikes me isn’t the corporate ambition, but the brutal, uncompromising geometry of its choices.

We believe that we’re on the face of the Earth to make great products, and that’s not changing. We’re constantly focusing on innovating. We believe in the simple, not the complex. We believe that we need to own and control the primary technologies behind the products we make, and participate only in markets where we can make a significant contribution.

We believe in saying no to thousands of projects so that we can really focus on the few that are truly important and meaningful to us. We believe in deep collaboration and cross-pollination of our groups, which allow us to innovate in a way that others cannot. And frankly, we don’t settle for anything less than excellence in every group in the company, and we have the self-honesty to admit when we’re wrong and the courage to change.

The gravity of that doctrine doesn’t live in the pursuit of “great products.” Everyone claims to want that. The gravity lives in the tension between wanting to do everything and having the discipline to do almost nothing.

“Saying no to thousands of projects” is easy to write on a slide. It is agonizing to practice in reality. It means looking at a perfectly good idea—perhaps even a highly profitable idea—and killing it because it dilutes the core mission. It is the architectural equivalent of leaving vast amounts of empty space in a room so that the few pieces of furniture inside it can actually breathe.

I think about the times in my own career when I lacked that specific kind of courage. I have held onto projects that had long since lost their spark, simply because of the sunk costs. I have said yes to interesting distractions that slowly eroded my focus on the essential work. We dilute our attention not because we intend to fail, but because the alternative—staring at a promising path and refusing to walk down it—feels entirely unnatural.

That is where Cook’s point about “self-honesty” becomes the linchpin. You cannot admit you are wrong unless you have created a culture where the truth outranks the ego. The deep collaboration Cook speaks of isn’t just about sharing resources; it’s about sharing the burden of that honesty. It is a collective agreement to not settle, to look at a nearly finished product and have the courage to say, this isn’t right yet.

Ultimately, the Cook Doctrine isn’t a strategy for building computers. It is an observation about human nature. The future is only guaranteed for those who can afford to survive the present—and survival demands knowing exactly what you are not.

The chaos isn’t an obstacle to the mission; it is the environment in which the mission earns its meaning.

Excellence is not just about what you build. It is also about what you are willing to destroy.