Author: Scott Loftesness

Categories
AI

The Quiet Setup: MacSparky’s Robot Assistant and the Unfair Advantage Still Available

A single X post caught my attention this week. It described something quietly happening among a small group of solo professionals. They aren’t working longer hours or grinding harder. Instead, they’ve built a particular kind of setup around AI that carries much of the load.

While most of us still treat powerful models as clever search bars—typing questions and copying answers—these folks have given the AI a rich folder of context, a briefing file that orients it to their world, connections to their tools, and routines that let it produce real work on its own. The result can look like the output of a small team. From the outside it reads as talent or luck. Up close, it’s mostly architecture.0

The post (from @zephyr_hg) emphasized that this advantage remains available because most people haven’t yet made the shift from one-off prompting to building persistent systems. It landed with me because it echoes so closely the practical territory David Sparks (MacSparky) has been mapping for months in his Robot Assistant Field Guide.

MacSparky’s Approach: From Chatbot to Persistent Colleague

David’s work centers on building a true personal assistant using Obsidian (for a local, plain-text knowledge base) and Claude (in its file-aware “Cowork” or project capabilities). The system isn’t a chatbot that forgets everything between conversations. It’s designed to remember your projects, preferences, and people; triage email in your voice; handle morning briefings; track tasks; process documents; and support weekly reviews—freeing you from what David calls the “donkey work.”

The key ingredients will sound familiar to anyone who read that X post:

  • A dedicated context layer (your Obsidian vault or structured folder) holding the details of how you work.
  • Briefing/instruction files that tell the model who you are and what good looks like.
  • Integrations that connect it to email, calendar, files, and other tools.
  • Skills and routines that turn one-time intentions into repeatable, low-friction action.

David has been refreshingly transparent about the journey. He experimented earlier with more fully autonomous agents and even shut one down after learning what felt reliable and aligned. The Robot Assistant Field Guide distills those lessons into videos, workshops, templates, and a starter kit that lets people build without needing to code.

Why This Matters Now

Both perspectives point to the same shift in stance: moving from “How do I prompt better today?” to “What kind of system do I want running alongside me every day?”

For me, at this stage of life, that question carries weight. I’m not chasing maximum output for its own sake. I want arrangements that protect attention and energy for what actually matters—deep reflection, family history work, thoughtful investing, writing that might be useful to others, and simply being present. A well-designed AI setup doesn’t just save minutes; it changes the texture of the day by reducing context-switching and repeated explanations.

It feels like finding a productive seam in the current moment of AI evolution—one of those hidden transitions where leverage quietly compounds if you’re willing to build the architecture.

The Door Remains Open

The encouraging message in both the X post and David’s teaching is that this isn’t locked behind rare talent or expensive infrastructure. The models are accessible. The patterns are becoming clearer. What’s required is the decision to treat AI less like a toy and more like a colleague you’re willing to orient and trust with real work.

I don’t have my own “robot assistant” fully built yet. I’ve been experimenting with custom agents, structured daily scans, and ideas like “The Observatory” for signal synthesis. Reading these sources side-by-side sharpened my sense of the next layer: giving the system a proper home, clear instructions, and meaningful recurring work.

If you’re a solo professional, creator, or lifelong learner feeling the press of too many small tasks, this is worth exploring. Start small. Build a modest context folder. Write a briefing file that captures how you think. Experiment with one routine. Iterate from there.

The setup that outworks the grind isn’t magic. It’s deliberate, learnable, and still wide open.

What setups are you experimenting with these days? I’d love to hear in the comments or on X.

Categories
Books History

The Absence of Cavalry

There is a moment on the second day at Gettysburg, in the trees below a hill nobody had bothered to name until that afternoon, when a colonel from Maine runs out of bullets. He has maybe eighty men left who can still stand. The ammunition wagons are somewhere behind him, or ahead of him, or nowhere at all — nobody has told him, because nobody knows. What he knows is the sound coming up the slope, which is the sound of more men than he has, coming again.

He gives the only order left. Fix bayonets. Then he does something that has no tactical name because it isn’t tactics, not really — he swings the end of his line forward like a door closing, and his men run downhill into an enemy that outnumbers them, screaming, empty rifles held out in front of them like something between a weapon and a prayer.

It works. It should not have worked. That’s the part that stays with you.

I read Michael Shaara’s The Killer Angels years into a working life that had already taught me the plain, unglamorous truth at the center of that charge — that almost every real decision gets made with less than you need to know. Not none. Less. You wait for the number that would make it easy, and the number doesn’t come, and the hill is still there, and eventually you have to move anyway. Chamberlain at Little Round Top is the version of that truth that Hollywood wanted, the one with a bayonet charge and a hill that becomes a metaphor. It’s a fine scene. It is not the one that has stayed lodged in me the longest.

The one that stays is a man who isn’t even at Gettysburg for most of the book he’s in.

Jeb Stuart was supposed to be Lee’s eyes. That’s the literal job — cavalry rides ahead, cavalry finds out where the enemy is and isn’t, cavalry comes back and tells the general the thing the general cannot see for himself. Stuart instead took his troopers on a long, glittering loop around the entire Union army, capturing wagons, making headlines, having — by every account, including Shaara’s — something close to the time of his life. And Lee, the whole time, was moving a hundred thousand men through Pennsylvania blind. Not blind because he was careless. Blind because the one man whose entire function was to prevent that blindness had gone looking for glory instead of information.

By the time Stuart rides back in, dusty and pleased with himself, the battle has already half-decided itself without him. Lee’s fury at him is quiet in the novel, almost tender, which is somehow worse than if it had been loud. There’s no scene of reckoning. There doesn’t need to be. The absence already did its work. Three days of an army feeling its way forward with its hands out, and somewhere behind all of it, a man who could have told them what was there, riding home late with wagons full of things nobody needed.

What stayed with me wasn’t Stuart’s vanity. It was the shape of the thing — the specific, structural loneliness of deciding while the person whose job was to reduce your uncertainty is off somewhere doing something that felt more important to him at the time. You don’t get to know, later, whether the information would have changed anything. You only get to know you didn’t have it, and you went ahead anyway, and now it’s history, or it’s Tuesday, or it’s both.

There’s a way of reading war novels where the tactics are the point, where watching intelligent people arrange forces on a map has an almost mathematical satisfaction. The Killer Angels gives you that if you want it; Shaara knew where every regiment stood on every ridge. But the book’s better trick is quieter. It keeps putting men in rooms — tents, really, canvas and lantern light — where the map has a hole in it, and asking them to act as though it doesn’t.

Longstreet knows the ground favors defense and says so, and is overruled by a man he loves, and does his duty anyway with the full weight of his own doubt still sitting in his chest. Chamberlain doesn’t know if the flank will hold and commits to it as though he does. Lee doesn’t know where the Union army actually is, for three of the most consequential days in American history, and moves his men forward on faith and old maps and the assumption that his cavalry would come back in time to tell him otherwise.

None of them get the number. They all have to decide before the fog lifts, because the fog was never going to lift on schedule, and the enemy does not wait for your confidence to catch up to your responsibility. That’s not really a Civil War lesson. It just happens to be dressed as one, in wool and brass buttons, on a July afternoon in Pennsylvania in 1863. It’s the same lesson wearing whatever clothes your own decade puts on it.

I don’t remember exactly where I was when I read it. This book doesn’t come back to me that way — it comes back as an idea I keep finding uses for, decades later, in situations that have nothing to do with ridgelines or rifles. Which might be the highest compliment a novel about a three-day battle can earn: that it stopped being about the battle, for me, somewhere around the second reading, and became a way of thinking about every room I’ve since sat in where the map had a hole in it and the clock kept running anyway.

Stuart did come back, eventually. Late, but he came back. I think about the men who never got their Stuart at all — who made the call, and never did find out what the missing piece would have told them, and had to live the rest of their lives inside a decision made permanently, gorgeously incomplete.

Categories
Aircraft Memories

Captain Gil Rud

Recently I wrote about a visit to the USS Constellation that I was very fortunate to make years ago. In that post I mentioned the captain of the ship without citing who he was.

This morning I realized I should do a bit of research and correct that – so I asked Gemini:

Who was the captain of the uss constellation who had previously led the blue angels?

Here’s how I got reacquainted with Captain Gil Rud:

That captain was Captain Gil Rud (USN, Ret.).

He served as the commanding officer and flight leader of the Blue Angels from November 1986 to November 1988, notably leading the team’s transition from the A-4 Skyhawk to the F/A-18 Hornet. Later in his career, he served as the commanding officer of the aircraft carrier USS Constellation (CV-64) from May 1993 to December 1994.

I continued:

When was he assigned to the Constellation? I remember him talking about taking it out of the Philadelphia Navy Yard?

And learned:

Your memory is spot on. Captain Gil Rud took command of the USS Constellation in May 1993, which coincided exactly with the end of her massive Service Life Extension Program (SLEP) overhaul at the Philadelphia Naval Shipyard.

From July 1990 until early 1993, the carrier was essentially torn down and rebuilt in Philadelphia to add an extra 15 years to her operational life. Captain Rud was assigned to the ship just as this grueling three-year yard period was wrapping up.  

He was the captain who literally “took her out” of the Philadelphia Navy Yard, leading the crew through the post-overhaul sea trials and commanding the carrier during its transit from the East Coast, around South America (as she was too large to fit through the Panama Canal), and back to her homeport in San Diego.

I continued this back and forth with Gemini learning about his career after the USS Constellation including his retirement from the Navy and work in private industry. Turns out he also authored a memoir: From the Prairie to the Pacific: A Blue Angel’s Journey.

Afterwards I felt better having done this research and getting reacquainted with Gil Rud.

Categories
Business Creativity Innovation Inspiration

The Idea That Won’t Let Go

“There are three elements to every great idea: 1. It solves for ‘why.’ Long before you figure out what a product will do, you need to understand why people will want it. The ‘why’ drives the ‘what.’ 2. It solves a problem that a lot of people have in their daily lives. 3. It follows you around. Even after you research and learn about it and try it out and realize how hard it’ll be to get it right, you can’t stop thinking about it.”
— Tony Fadell, Build

The third element is the only one that isn’t optional. You can fake the why — retrofit it, hire a consultant to write it on a slide in a font called Montserrat. You can borrow the what; most products are just other products in a better jacket. You cannot fake the third thing, because the whole test of it is that it happens without your permission.

Call it a visitation. It shows up uninvited at the stoplight, in the shower, at 2:40 a.m. when the ceiling becomes a screen for it. You know the unit economics don’t work. You know the regulatory path is nine years long. You know — you know — that fourteen better-funded people already tried this and left with nothing but a Delaware C-corp and a grudge. None of it helps. The idea has already filed its paperwork. It lives here now.

You cannot bullet-point a visitation. There is no OKR for thinking about landing gear hydraulics while your wife is telling you about her sister’s wedding. Everyone who’s built something that mattered will tell you this, late enough at a dinner and honest enough on the wine: not conviction, not passion — that laminated word — but the visitor, still standing in the doorway of every other thought you’re supposed to be having.

It doesn’t check your calendar. It doesn’t care that you’ve moved on to point two, the sensible one, the one venture capitalists nod along to with their flat whites going warm. It was never about the market. The market is the alibi you build afterward, so you don’t have to say the true thing: I didn’t choose it. It moved in while I was asleep, and my life rearranged itself around the shape of it, the way a house rearranges itself around a family it didn’t ask for.

Maybe the third element isn’t a filter for the idea. Maybe it’s a filter for you — a way of finding out, by accident, at 2:40 in the morning, staring at a ceiling that has decided to keep the light on.

Categories
Cars Design Honda

The Shape of Fear

There’s a red-and-silver Honda CRX that shows up in a parking lot near a park I walk regularly. Not always — it’s not a daily thing — but often enough that I’ve started to look for it. When it’s there, I stop. I stare longer than a car deserves. I’ve owned other Hondas. I never owned this model, and by the time I could have, I was a family man, and a two-door coupe with a back seat that barely qualifies as a suggestion wasn’t a thing you brought home. That’s still true. I still love it anyway.

For a long time I thought the pull was nostalgia — an artifact from a specific decade doing what artifacts from specific decades do, standing in for the whole era around them. But nostalgia doesn’t usually make you stop walking.

Something more specific was going on, and I only located it recently, looking at a rendering of Tesla’s Cybercab: the same silhouette. Not the same car, not the same era, not the same anything except the one thing that matters most in a side profile — the roofline. Low nose, a peak over the front seats, one continuous downward sweep to a short, cropped tail. No break at the B-pillar to speak of. Glass that continues the line of the roof instead of interrupting it.

Two cars, forty years apart, arriving at the identical answer to a formal problem. That’s the kind of coincidence that isn’t really a coincidence — it’s a shape that keeps getting rediscovered whenever the constraints line back up.

The Cybercab gets there because there’s no driver’s compartment to package around, no B-pillar structure fighting for space, nothing back there to make room for. The roofline can just fall away because there’s nothing left to interrupt it.

The CRX got there from the opposite direction — not by subtraction of function but by subtraction of everything else. Weight. Drag. Ornament.

What I didn’t expect, going looking, was how much fear was baked into that shape.

The CRX wasn’t dreamed up in some skunkworks with time to spare. It came out of what Honda’s own people described, at the time, as something close to an image crisis — the third-generation Civic was about to launch into a market with sharper competitors than the last one, and the man responsible for small-car development at Honda R&D was worried the company’s whole small-car identity was aging out from under it. The response was billed internally as a kind of renaissance, and the CRX was its opening statement — not a side project, but the leading edge of an “all-out attack.”

The person who actually shaped it, Hiroshi Kizawa, had already put his career on the line once, on the original Civic — a car he believed Honda’s future as a real manufacturer depended on. He came back and did it again, smaller and stranger this time: a two-seat coupe, under 900 kilograms, wrapped in plastic body panels molded in-house, chosen partly because they could someday be recycled — Honda thinking, in 1981, about what happened to the car after its life was over, which is its own small strangeness worth sitting with.

The reception at home was lukewarm in a way I find almost endearing now. One Japanese trade magazine at the time called it a dehydrated Camaro with some boy-racer posturing, allowing that it might not be beautiful but was at least likeable. That’s a strange epitaph for a car I’d call one of the most purely resolved shapes of its decade. But maybe that’s how it goes with real design — the people closest to it, watching it get made under pressure, can’t yet see what it will look like from forty years out, parked in a lot, still stopping people who weren’t even born when it launched.

Less than six months after the CRX reached showrooms, Honda started work on what would eventually become the NSX. The unglamorous little economy coupe, born from institutional anxiety and injection-molded plastic, turned out to be the warm-up act for the most serious sports car the company would ever build. Fear, it turns out, is not a bad place to start, if the people afraid of it are good enough to turn it into something worth being afraid for.

Which makes me think of Ferrari’s own version of this moment, playing out right now. Their first electric car, the Luce, is exactly the kind of institutional fear the CRX was born from — a company that has to prove it still belongs to the future, using a technology it didn’t choose. And where Honda answered that fear with a shape, a single unbroken line that turned scarcity into style, Ferrari answered it with a four-door liftback, roomy and glassy and, by most early accounts, nobody’s idea of a Ferrari silhouette. I wish they’d gone the other way. I wish somebody at Maranello had looked at what a wedge does when you strip a car down to its constraints — no engine bay to hide, no B-pillar to interrupt, nothing left but the line from nose to tail — and had the nerve to make the Luce look like it was afraid of something, the way the CRX clearly was.

I think about that shape differently now — not as a wedge from the eighties, and not as a preview of some robotaxi’s rendering either, but as a shape that seems to arrive whenever a design team is left with almost nothing to hide behind. No engine bay to speak of. No back seat to protect. No driver at all, in one case. What’s left, both times, is the same honest line — nose to tail, unbroken — and I wonder what it says that the shape survives every reason for making it, outlasting the fear and the plastic and the market anxieties that produced it, showing up again decades later for reasons nobody involved the first time could have guessed.

Categories
AI Podcasts

A Remarkable Conversation…

Highly recommend this conversation between Harry Stebbings and Clay Bavor. Among many topics, I especially enjoyed the discussion about not investing in frontier models, the important values, the particular importance of craftsmanship, intensity, and family. And the special conversation about parenting and kids near the end. Just a delightful conversation to be able to enjoy!

Key Highlights:

• Founding Sierra: Bavor explains why he and Taylor chose to start Sierra, focusing on the transformative potential of language model-based agents (1:37 – 5:53).
• The AI Tech Stack: Sierra focuses on building enterprise-grade agent architectures and fine-tuning models on top of open-weights models rather than pre-training foundation models from scratch, prioritizing capital efficiency (5:53 – 7:15).
• Unbounded Demand for Intelligence: Bavor argues that there is massive, unmet demand for “frontier-level” intelligence in fields like coding, science, and legal work (7:15 – 11:41).
• Internal AI Operations: He details the use of Pinecone, an internal AI agent Sierra developed to navigate company data, streamline engineering, and assist in recruitment (18:36 – 22:00).
• Enterprise Strategy: Sierra employs a “forward-deployed” engineering model, embedding staff within client companies to ensure rapid, effective integration of AI, leading to quick deployment timelines (30:12 – 33:22).
• Board Governance: To keep pace with the speed of AI development, Sierra operates on a six-week board meeting cadence, utilizing comprehensive memos instead of traditional slide decks (39:07 – 41:13).
• Corporate Culture: Bavor emphasizes values like craftsmanship, intensity, and family. He also highlights the importance of working in-person to foster apprenticeship, mentorship, and a cohesive team culture (43:02 – 55:41).

Categories
AI AI: Large Language Models Apple

The Slipstream Strategy

Apple had a problem no amount of money could solve. An iPhone can’t draw the power or shed the heat of a data center, so ten different tasks can’t mean ten different models fighting for the same sliver of RAM. Apple’s answer was to freeze one small, efficient base model into the device and then swap tiny adapters in and out of it in milliseconds — a summarization adapter for your texts, a Siri adapter for on-screen actions, and a handoff to Private Cloud Compute for anything heavier. The phone behaves like it’s running many models. It’s running one model wearing many hats.

That architecture — a frozen base plus swappable adapters — is quietly becoming the default way serious AI companies build, and it’s worth understanding why, because it inverts the assumption most people still carry into this industry.

The assumption is that winning means owning a frontier model. Sierra co-founder Clay Bavor pushed back on that on a recent 20VC episode: pouring capital into your own pre-training, he argued, tends to leave you holding a highly perishable bag of floating-point numbers. Open-weight models improve fast enough that yesterday’s frontier is next quarter’s commodity. The companies playing this well aren’t racing to out-spend the labs. They’re slipstreaming behind them — taking the free, state-of-the-art engine and putting all their effort into what sits on top of it.

What sits on top is LoRA — low-rank adaptation. The old failure mode was catastrophic forgetting: fine-tune a model hard enough on your own data and it forgets how to reason generally. LoRA sidesteps this by leaving the base model untouched and training a small set of additional parameters alongside it — a thin layer of expertise bolted onto a frozen foundation. You get real domain depth without touching the thing that makes the model work at all.

The business logic that follows from this is the actual point, and it’s simpler than it looks:

You stop being hostage to any one model provider — if a better open-weight model ships next month, you port your adapter, not your whole product. You can serve hundreds of differently-customized clients off one base model on one piece of hardware, instead of running a separate giant model per customer. You can ship a fix in an afternoon, because an adapter is a few hundred megabytes, not a training run. And in regulated industries, your proprietary data can train an adapter that never leaves your own infrastructure.

None of this is really a story about model architecture. It’s a story about where the moat moved. For a while the moat was raw capability — whoever had the best model won. Apple and Sierra are betting the moat is now somewhere else entirely: in how tightly you can weave a commodity intelligence into a specific workflow, a specific dataset, a specific customer relationship. The engine is free. The adapter is the business.

Categories
AI Apple Google

The Floor

I compared the frontier to a three-star chef making grilled cheese in “Context Rot” — the smartest models on earth spending most of their time on work beneath them, the way a chef trained at Le Bernardin might still melt cheese between two slices of bread on a Tuesday night and call it dinner. The comfort was the point: if the sharpest tool is saved for hard problems and something merely-very-good handles the rest, nobody’s losing anything. The floor was never the interesting part.

I’ve kept turning the joke over, and I think I had the wrong worry.

Watch what companies do with their AI spend, not what they say. Coinbase moved engineers off frontier models onto open weights and cut its AI spend nearly in half while usage kept climbing. Nvidia runs a closed model as orchestrator and routes the actual volume — the daily uncelebrated bulk of it — to open weights it controls. The frontier is becoming a dispatcher, deciding where the request goes and rarely doing the work itself. The instinct is to worry about whose open weights end up running that volume, and right now the most capable ones at scale are Chinese — GLM, Kimi — which makes it tempting to read this as a contest America is quietly losing: the floor of the AI economy built somewhere else, at a price export controls can’t touch. You cannot embargo a file already downloaded. You cannot price-match free.

But that framing has a hole. Google’s own Gemma family is open-weight and good enough to handle that daily volume without anyone reaching for GLM or Kimi. “Open weights are a Chinese story” only holds if you don’t count the open models the company running Android and half the internet’s search traffic has already shipped.

And once I saw that hole, a bigger one opened behind it. I’ve been trying Apple’s new Siri — arriving with iOS 27 this fall, genuinely surprisingly good in beta — and it made me realize open weights, of any nationality, were never going to cook most of the world’s dinners. Apple and Google are.

Consider what actually determines where the world’s routine inference runs. Not which model benchmarks best, not which weights are downloadable — what’s already installed. Apple ships to well over a billion active devices before routing a single query through Siri’s new architecture. Nobody has to be persuaded to try it, or hear about it on a podcast; it’s the thing that answers when you press the button you’ve pressed for a decade. Google owns the search bar and the Android default the same way. Between them, that’s most of the world’s phones — and phones are where most of the world’s questions get asked.

The open-weight framing assumes the floor is up for grabs, that whoever ships the best free model wins the daily grind by merit. But the floor was never a bazaar. It’s a set of defaults, owned by whoever already has the device in your hand, not whoever holds the most generous license. Apple didn’t need to win the model war to win this. Its heaviest reasoning tier is built with Google, running on Nvidia chips in Google’s cloud, under a deal reported at roughly a billion dollars a year — Apple doesn’t fully own the engine doing the thinking. It doesn’t need to. It owns the button.

That’s a quieter concentration than an export-controls fight, and a harder one to dislodge. An open model can be forked, distilled, undercut, or out-competed by the next release. A billion phones with an assistant built into the lock screen cannot be routed around. Whoever’s weights hum underneath barely matters, the way it barely matters to a diner which supplier delivered the flour. What matters is whose kitchen the meal came from, and whose name is on the door.

The grilled-cheese chef was never the risk. Two chefs are about to own nearly every kitchen on earth, and most of us will never notice — because a kitchen you’ve been eating out of for a decade doesn’t feel like something that was won. It just feels like home.

Owning the kitchen and getting paid for what’s cooked in it, though, turn out to be two different questions. That one’s for another post.

Categories
AI China Youth

The Arithmetic of Youth

The first meeting was at one of the banks on a high floor somewhere in Shanghai, the kind of view that turns a city into an abstraction. It was 2005, and I was there the way American investors were there that year — curious, a little jet-lagged, trying to read a country that was rewriting itself faster than anyone could print the new edition. Across the table sat a management team, and what struck me wasn’t anything they said. It was how young they were. Not junior-young. Running-the-company young.

Afterward — in the hallway or the car, early in the trip, when I still had the confidence of someone who thought he could just ask — I put the question to one of our local colleagues. Casually, expecting a casual answer. Something about a young country, a young economy, energy meeting opportunity.

The answer I got instead was the Cultural Revolution.

There was a generation, she explained, that simply wasn’t there. Sent to the countryside, pulled out of universities, handed shovels instead of textbooks. By the time China opened back up, that cohort had a hole in it — a rung missing from the ladder. So the young people I’d just watched run that meeting weren’t there because anyone had bet on youth. They were there because there was no one older left to put in the chair. Youth, in that boardroom, wasn’t a strategy. It was a vacancy dressed up as one.

I have thought about that answer, off and on, for twenty years, without knowing what to do with it. Then a few weeks ago I read a summary of a conversation with Nathan Lambert — an AI researcher who’d just spent time visiting the frontier labs in Beijing and Hangzhou — and I found myself back in that room, except everything about the youth in it had flipped.

He describes teams at places like Moonshot AI as almost absurdly young, tight-knit, close to giddy about the work — “the best vibes,” he calls it. Zhipu AI, he says, has built something close to an AGI showroom, a physical space engineered to perform confidence for whoever walks through the door. These aren’t companies with a hole where the experienced people should be. These are companies that went looking for twenty-five-year-olds because twenty-five-year-olds move at the speed frontier AI research demands, and installed them at the center of the room. The showroom isn’t hiding a vacancy. It’s staging a choice. That’s panel two.

Same demographic. Same first city — Beijing both times — with a high-speed rail line now running to Hangzhou instead of whatever second city I’d have named twenty years ago. Opposite cause. In 2005, youth in the room meant a generation had been taken from the labor force involuntarily. In 2026, youth in the room means a generation has been selected for it, deliberately, competitively, because being young is now the qualification rather than the disqualifier. The Cultural Revolution left a gap that youth filled by default. The AI boom left a door that youth is filling by design.

I would have stopped there, satisfied with the irony, except for a number I couldn’t get out of my head once I went looking for it: 15.6 percent. That’s China’s urban youth unemployment rate — ages sixteen to twenty-four, university students excluded — as of May 2026, and it counts as good news, down from 16.3 percent in April. A year earlier it had spiked to nearly nineteen percent in a single August, the month twelve million university graduates walked out of commencement and into a labor market that had no idea what to do with them. Some will sit for civil service exams, chasing what people there still call the iron rice bowl — the illusion of permanence a state job used to guarantee, back when your grandparents didn’t choose their careers so much as get assigned them. Others will enroll in another degree, not because they want one, but because a classroom is a more dignified place to wait than an unemployment line.

So there is a third panel now, and it doesn’t fit neatly next to the other two. It isn’t a vacancy, and it isn’t a showroom. It’s just a very large number of young Chinese people who did everything they were told to do — studied hard, got the degree — and are standing outside a door that isn’t opening. And somewhere behind that door, in a much smaller room with much better lighting, another group of young Chinese people, maybe the same graduating class, are building the technology that a Silicon Valley researcher travels overseas to admire for its vibes.

I don’t think those two rooms are as separate as they look. I think the showroom is real, and I think the twelve million are real, and I think the mistake — my mistake, sitting here in Menlo Park two decades removed from that conference table — is letting either one stand in for “Chinese youth” as if it were a single sentence instead of a population. The Moonshot AI team is not a representative sample. It’s the visible sliver of a generation, selected with a precision that turns the unemployment numbers into part of the same mechanism — one sorting process, not two unrelated stories. The best vibes in that lab and the worst numbers in that economy might just be describing the two ends of the same funnel.

I keep coming back to that hallway in 2005, and to how confident I was in the question I asked — as if a generation’s youth could only ever be telling one story. It couldn’t then, and it can’t now. I got a true answer that day and thought I understood something. I understood one panel of a triptych I hadn’t seen the rest of yet — and I’m still not sure I’ve seen all of it.

Categories
Business History

The Architecture of Unseen Influence

We build our monuments over the wrong graves. It’s a bad habit of ours, this craving for the lone genius—the larger-than-life figure who supposedly commands the tides of progress by sheer force of will. But look beneath the surface of how things actually get built. The reality is messier. And a hell of a lot more interesting.

Take Thomas Edison. Secular saint of American ingenuity. The wizard who single-handedly lit up the dark. Except he didn’t. Edison wasn’t a solitary creator; he was a brilliant, ruthless aggregator of other people’s breakthroughs and a master of public relations. He invented the bulb, sure, but his real masterpiece was the myth of himself. In the process, he eclipsed the collective sweat of his own labs and the far more elegant alternating-current systems of his rivals. He’s our most overrated figure—not because he lacked talent, but because his shadow blinded us to how progress actually happens.

Morgan Housel nailed this structural blind spot by tracing the tangled ancestry of major turning points:

“Every current event – big or small – has parents, grandparents, great grandparents, siblings, and cousins. Ignoring that family tree can muddy your understanding of events, giving a false impression of why things happened… Viewing events in isolation, without an appreciation for their long roots, helps explain everything from why forecasting is hard to why politics is nasty.”

Look past the blinding light of the celebrity inventors and you find the long roots that actually remade our world. Take FCC Part 15. It’s an event almost no history textbook bothers to mention. In the early 1980s, a lone staff engineer named Dr. Michael Marcus looked at three chunks of the radio spectrum—stuff discarded as “garbage bands” reserved for industrial microwave ovens—and saw an opening. The entire telecom establishment thought he was chasing a recipe for chaotic interference.

Marcus didn’t blink. He spent years pushing through a dry, technical ruling in 1985 to open those garbage bands for unlicensed public use. A total footnote. Yet that single, unheralded bureaucratic open door laid the invisible foundation for Wi-Fi, Bluetooth, and the entire wireless ecosystem running your life today. Marcus didn’t get a ticker-tape parade; he got political friction and a quiet transfer to a back-office enforcement role. No hero on horseback. Just a guy in a cubicle who rewired the world.

We do the same thing with politics. We rank presidents by the volume of their rhetoric or the body count of their wars. Meanwhile, men like Chester A. Arthur get left in the dusty margins of trivia. Arthur was the ultimate product of the spoils system—a New York machine politician who climbed to power on institutional corruption. Then James A. Garfield was assassinated, and Arthur was thrust into the big chair. Something clicked. Instead of feeding the machine that birthed him, he turned inward, defied his old patrons, and signed the Pendleton Civil Service Act. He dismantled the very patronage system he’d mastered. It was a stunning act of quiet integrity that killed his political future but saved the republic’s administrative soul.

Or take Frances Perkins. Ask the average student who gave them the weekend, the forty-hour work week, unemployment insurance, and the abolition of child labor, and you’ll get a blank stare. Perkins was FDR’s Secretary of Labor. She wasn’t a regular on the campaign posters. She just stood in the back of the room, turning abstract economic suffering into concrete human safety nets.

I’ve been sitting with this for a few days, thinking about my own career—and the times I mistook the loudest person in the room for the smartest. I chased the visionary founders with the spellbinding pitches. I ignored the quiet engineers and the mundane infrastructure choices that actually determine whether an idea scales or snaps. It takes a few painful, expensive missteps to realize that the real compounding interest of progress is almost always generated in the dark.

History isn’t a solo act. It’s an intricate, mostly anonymous collaboration between accidental reformers, stubborn bureaucrats, and regulatory footnotes. If you want to understand where we’re going, stop staring at the stage lights.

Start looking at the wiring.