Tag: technology

Categories
AI

The Shape of the Question

Marc Andreessen made two claims recently that don’t quite fit together, and I haven’t been able to stop pulling at the seam.

The first: for almost any topic, the top AI systems now give him better answers than the world-class experts he could call on the phone. And he can call basically anyone. This isn’t a casual observation from someone without access — it’s a meaningful data point about what AI is actually doing to the value of expertise.

The second: the only real skill left in using AI is knowing what to ask. The models can already do almost anything you can describe in plain English. The bottleneck lives in your own head.

Hold those two claims next to each other. If the AI beats the experts, then the quality of your question only has to clear a low bar — good enough to unlock what the system already knows. You don’t need to ask like a cardiologist to get a cardiologist-quality answer. You just need to ask.

Except that’s not how it works in practice. And the gap between the two claims is where something important lives.

The better the question, the better the answer — even from a system that already knows more than any human alive. Expert-level interrogation of a superhuman system produces something qualitatively different from naive interrogation of the same system. The gap between a good question and a bad one doesn’t shrink because the underlying capability grows. It may widen. A sharper instrument in an unskilled hand doesn’t close the distance — it just makes the skilled hand more lethal.

What the AI has done is commoditize answers. What it has not done — cannot do — is commoditize the ability to know which question to ask.

There is a concept from epistemology that keeps surfacing here: the unknown unknown. Donald Rumsfeld made the phrase famous and then spent years living down the mockery, which was unfair, because the underlying idea is genuinely important. There are things you know you don’t know — the gaps you can name, the questions you can form. And there are things you don’t know you don’t know — the territory you can’t even see the edge of. The naive user of AI operates almost entirely in the second category. They ask what they already suspect. They get answers that confirm the shape of what they already believe. The system is brilliant and they are using it as a mirror.

The sophisticated user has learned to ask the AI to challenge their assumptions. To find the holes. To steelman the opposing view. To identify what’s missing from the framing. That second posture requires a kind of intellectual self-awareness — an ability to stand outside your own thinking and interrogate it — that is neither common nor easily taught.

Here is the uncomfortable implication: that self-awareness is not randomly distributed. It correlates with education, with reading, with having thought carefully about hard things for a long time. The people best positioned to ask good questions are, largely, the people who already had access to good answers through the old system. The gate moved. It didn’t disappear.

There’s a democratic story told about AI and I believe parts of it. The kid in rural South Dakota with a good question now gets an answer that rivals what the partner at McKinsey gets.

But access to information was never really the binding constraint. The binding constraint was always the ability to know what information you need — to feel the shape of your own ignorance precisely enough to ask for what fills it. That skill wasn’t distributed by the old system and it won’t be distributed by the new one. It has to be built, slowly, through years of reading and thinking and being wrong and trying again.

What AI may actually be doing is widening the gap between people who ask well and people who don’t — making the former dramatically more capable while leaving the latter approximately where they were, just with a faster way to get answers to questions they already knew to ask.

Somewhere right now, someone is sitting with the most capable thinking tool in human history, asking it to write a cover letter. The tool will do it beautifully. And the gap will quietly widen.

Categories
Bonsai Filoli Living

The Patience of Small Things

There is a tree on a terrace at Filoli that is roughly the size of a lamp. It sits in a shallow black bowl, its trunk leaning with the easy confidence of something that has been leaning for decades, its canopy splayed against the California sky like a fist slowly opening. Behind it, the estate’s formal garden dissolves into soft focus — roses, balustrades, the suggestion of abundance. The bonsai doesn’t compete with any of it. It simply occupies its few cubic feet with a completeness that makes everything else feel approximate.

I’ve been thinking about what that completeness costs.

The tree is probably a juniper — the fibrous, spiraling bark, the dense scale-like foliage, the way the branch structure seems to remember every decision ever made about it. Bonsai practitioners talk about nebari, the visible surface roots, and movement, the quality of dynamism frozen into wood. This one has both. The trunk doesn’t just lean; it goes somewhere, pulled by some invisible argument the grower made with it over years, or decades, or longer. The moss at its base is so even and green it looks curated, because it was.

What strikes me standing in front of it is that this is a technology — not in the semiconductor sense, but in the older one. A technique for shaping time. The grower didn’t make this tree. They made conditions, and maintained them, and made them again, and the tree is what happened. The distinction matters. There’s no shortcut to the trunk diameter. There’s no prompt that produces the movement in that wood.

I work in a medium where the gap between intention and output has collapsed to nearly nothing. I describe something and it appears. There’s tremendous utility in that, and I’m not romantic enough to pretend otherwise. But Filoli’s bonsai terrace is a useful corrective — a reminder that some forms of beauty are only legible as records of duration. The lean of that trunk is not a feature. It’s an argument made slowly, over a life, against gravity.

I don’t know who grew it. I don’t know if they’re still alive. The tree, characteristically, offers no information about this. It just stands there in its bowl, complete, patient, not particularly interested in being understood.

Categories
AI Living

The Threshold

There is a specific feeling. You are trying to understand something — a medical term in a lab report, a clause in a contract, how a particular piece of software actually works under the hood — and you hit the edge of what you know. The territory beyond is unfamiliar and the path is unclear, and something in you decides, quietly and almost without announcement: I don’t know how to figure this out.

And then you move on.

Marc Andreessen, talking to Joe Rogan recently, buried something important inside a longer riff about AI prompting tricks. Most of his list was the kind of thing you’d read in a productivity newsletter — ask it to steelman both sides, pretend it’s a panel of experts. Useful, not revelatory. But one observation was different: pay attention to the exact moment you think “I don’t know how to figure this out.” That’s the moment you should open the AI.

He said it almost offhandedly. I haven’t been able to stop thinking about it.

What he’s really describing isn’t a technique. It’s a behavioral pattern that most of us developed so gradually we don’t recognize it as a choice. The feeling of epistemic overreach — of arriving at the edge of one’s competence — became, over decades, a stopping condition. We learned to treat not-knowing as a wall rather than a door because, most of the time, it functionally was one. The library was closed. The expert was unavailable. The research was paywalled. You moved on.

The habit calcified. Now it persists even when the conditions that produced it no longer apply.

I notice it in myself, and I’m someone who is genuinely curious — who likes knowing how things work, who will follow a thread further than most people bother to. That’s not modesty; it’s relevant context. Because even with that disposition, I still hit the wall. I’ll be reading something and encounter a concept I only vaguely follow — some nuance in immunology, some historical episode I’ve only half absorbed — and I feel the familiar slight contraction, the small withdrawal. I read past it. The curiosity was there. The friction was higher.

Curiosity alone was never enough. What determined whether I pushed through wasn’t how much I wanted to understand — it was whether understanding felt retrievable at all. Most of the time, it didn’t. So I moved on, and the curiosity found something else to chase.

There’s a darker version of this worth sitting with. The people who never developed the quit reflex — who hit not-knowing and felt compelled rather than defeated — are, disproportionately, the ones who built things. The intellectual persistence wasn’t incidental to their contributions; it was probably constitutive of them. Curiosity as stubbornness. The refusal to accept the wall as final.

Elon Musk is the limit case. When he decided he wanted to go to Mars and found the rockets prohibitively expensive, he didn’t defer to the aerospace industry’s consensus about what was possible. He started reading propulsion manuals and cold-calling engineers. The quit signal either never fired or got overridden so fast it made no practical difference. The result was reusable orbital rockets, which the industry had largely decided weren’t worth pursuing. The dig reflex, taken to its extreme, rewrote what was considered feasible.

But the trait is undifferentiated. It doesn’t come with a calibration mechanism. The same refusal to accept expert consensus that produced SpaceX also produces a certain amount of confident wrongness — the Twitter decisions, the Covid takes, the occasional foray into geopolitics with the certainty of someone who has read a lot of Wikipedia. The dig reflex, unregulated, has no obvious stopping condition.

AI doesn’t change that underlying trait. What it changes is the access cost for everyone else.

For most of human history, the friction wasn’t random. It selected for people whose drive was strong enough to overcome it regardless of cost — the right connections, the right institution, the time to burn. Now that friction is lower for everyone, nearly to zero, for an enormous range of questions.

What I’m trying to build is the opposite of the quit reflex. Not the Musk version — boundless, uncalibrated, occasionally catastrophic. Something more modest: the habit of checking before giving up. Noticing the moment of not-knowing and treating it as a question rather than a verdict.

It requires noticing the moment. Which is harder than it sounds, because the reflex is fast and the moment is brief.

The contraction happens. You’ve already moved on. Somewhere behind you, the question is still there.

Categories
Haiku Living Reading

The Presence We Keep Deferring

I have so many unread articles saved to Instapaper that I’ve stopped checking the count. Each one felt, in the moment of saving it, like something I needed. A long piece on urban planning, a profile of someone interesting, a reported essay I fully intended to sit with.

The app is beautifully designed for exactly this — the frictionless capture, the clean reading interface waiting patiently on the other side.

What it can’t do is manufacture the attention I didn’t have when I saved it and still don’t have now. The articles aren’t the problem. The premise is: that presence is something you can bank.

There’s a haiku I keep returning to, from Natalie Goldberg’s Three Simple Lines. It’s by a poet named Fumiko Harada:

Morning chill
I savor this moment —
one meeting one lifetime

Eleven words. No verb in the third line, which makes it feel less like a thought and more like a verdict.

The Japanese concept underneath it is ichi-go ichi-e — loosely, “one time, one meeting.” It’s a Zen idea with origins in the tea ceremony, the understanding that each gathering is singular and therefore irreversible. You cannot archive it. You cannot search for it later. When it ends, it doesn’t go anywhere you can retrieve.

This is what the Instapaper queue is, at scale: an archive of moments I decided to experience later. The article about urban planning was written by someone who spent months reporting it, on a day when some editor thought it was ready, and landed in my feed on a morning when something about the headline caught me. That constellation doesn’t reassemble. Later is a different article.

The tools I use every day are getting astonishing. There are systems that can summarize, translate, recall, explain, anticipate. I use them. I find them genuinely useful.

But there’s a habit of mind they reward — a kind of perpetual deferral of full attention — that I haven’t fully reckoned with. The promise, always, is that you can engage more completely later, once the summary is ready, once the transcript exists, once the notes have been taken. Presence becomes a productivity tax you pay while waiting for a deliverable.

Harada’s haiku doesn’t moralize. The speaker isn’t lecturing herself into awareness. She’s just cold, and awake, and choosing to notice. I savor this moment. The word “savor” does a lot of work. It implies effort. You savor things that could be missed.

The pivot in the third line is what stays with me. One meeting one lifetime. Not “this meeting will last a lifetime” — that would be sentiment. It’s more like a mathematical statement: the cardinality of this encounter is one. There is exactly one of them. This morning, this particular chill, whatever conversation or solitude is happening inside it — that set has one element. By tomorrow it has zero. No amount of documentation changes that arithmetic.

I’m working on believing that.

Categories
Architecture Infrastructure

The Architecture of the Indestructible

We are conditioned to look for the center of things. When we try to understand an organization, we ask for an organizational chart. When we look at a nation, we look to its capital. Traditional architecture—whether of a building, a company, or an army—relies on a classic playbook: a strong hub, radiating outward. You find the center, you secure it, and the system holds.

But what happens when you try to decapitate an enemy, or a technology, that has no head?

In 1964, a brilliant engineer named Paul Baran sat at his desk at the RAND Corporation, trying to solve a Cold War nightmare: How do you maintain a communications network after a catastrophic nuclear strike? Baran realized that traditional networks were centralized—like a wheel with spokes. If you destroy the hub in the center, every single spoke becomes useless.

His solution was the distributed network, the foundational blueprint for what would eventually become the Internet.

“Under the proposed system, each station would need to be connected to only a few of its nearest neighbors… The system would be highly reliable, even if a large fraction of the stations were destroyed.”

Baran mathematically proved that if you remove the center, the edges don’t die. They simply reroute. A few decades later, telecom engineers used a remarkably similar logic to build cellular telephone networks. Instead of one massive, high-power radio tower serving an entire city, they broke the terrain into a grid of small, low-power cells. If one tower goes offline, the network degrades gracefully rather than collapsing. It bends, but it refuses to break.

There is a profound, poetic irony buried here. The United States government originally funded Baran’s research to create a distributed network so that its centralized monolith could survive. Decades later, asymmetric adversaries across the globe adopted that exact architectural philosophy for their physical defense doctrines—creating “Mosaic Defense” systems designed specifically so that when you destroy the center, the edges keep fighting.

They copied our homework to survive our strength.

I find myself thinking about this tension far beyond the realms of military strategy or software engineering. It is a metaphor for how we construct our lives. We often build centralized lives—anchored entirely to a single identity, a single career, or a single institution. We project a monolith of strength to the world. But monoliths are brittle. When the center is struck, the whole architecture crumbles.

The lesson of our modern architecture is becoming increasingly clear, whether you are managing a network, building an organization, or navigating the quiet complexities of a human life. The fragile monolith is an illusion of safety.

The future belongs to the web that knows how to reroute.

Categories
AI History

The Arrival

Yoshua Bengio spent forty years building the foundation of modern artificial intelligence. He won the Turing Award for it. And he didn’t think he’d live to see it work.

That’s the quiet fact buried inside Stephen Witt’s New Yorker profile of him. Bengio — one of the three researchers whose decades-long bet on neural networks eventually became the architecture underlying every large language model running today — had made peace with the idea that the thing he was building was a multi-generational project. Something for his successors to finish. Then Witt writes: “one day in late 2022, the technology had simply arrived. He compared it to meeting an extraterrestrial.”

Hemingway once described bankruptcy happening two ways: gradually, then suddenly. He meant ruin. Bengio experienced something harder to name — not ruin but arrival, which carries its own vertigo. The gradually was four decades of work that most of his peers considered quixotic. The suddenly was a Tuesday in November when a chat interface went live and the world quietly changed.

What unsettles me about the extraterrestrial comparison isn’t the strangeness it implies. It’s the distance. You meet an alien; you don’t meet something you made. The metaphor suggests that even its creator couldn’t fully recognize it — that the thing, once arrived, belonged to a category that exceeded its own origins.

We don’t have good language for this. Breakthrough, inflection point, paradigm shift — these are words people reach for after the fact, when they’re building timelines. What Bengio seems to be describing is the experience of standing in front of a threshold you spent your life approaching, and finding it already behind you.

The technology didn’t ask permission. It didn’t announce itself.

It arrived.

Categories
AI Technology

The Bathwater Problem

Gary Kamiya was writing about the Tenderloin when he said it, but the line has been following me around: “The problem is that by saving the baby, you also save the bathwater.”

The pattern is remarkably consistent across every major information technology. Each one arrives promising to liberate the deserving — the faithful, the learned, the civic-minded — and each one immediately, inevitably, arms everyone else too. Gutenberg’s press was understood by its champions as a device for spreading the true Word; within decades it was the primary infrastructure for Protestant schism, Catholic counter-propaganda, astrological almanacs, and pornography. The reformers got their Bible. They also got their pamphlet wars.

The telegraph was greeted as a force for peace — shared information would make war irrational, commerce would bind nations. It also became the nervous system of commodity speculation, financial manipulation, and the first truly industrial-scale news hoaxes. The telephone: connection and the crank call, the crisis line and the threatening voice in the dark. Radio: FDR’s fireside chats and Father Coughlin. Television: Murrow taking down McCarthy, and also fifty years of manufactured consent. The internet: the largest library ever assembled and the largest sewer.

The pattern isn’t coincidental. It’s structural. Each technology expands what’s possible for human expression and coordination — and human expression and coordination contain both the noblest and the worst of us in roughly fixed proportion. The tool doesn’t change the ratio. It scales both sides of it.

What’s interesting historically is how each generation believes their technology will be different — that this time the architecture can be designed to select for the good. The internet era produced the most elaborate version of this belief: algorithmic curation would surface truth, network effects would reward quality, the wisdom of crowds would outcompete misinformation. Instead it turned out that engagement was the attractor, and outrage was the highest-engagement content. The bath got hotter.

The AI moment is the same belief system, restated with more technical sophistication. But the Kamiya line stands. You are saving a baby, and you are saving bathwater, and no one has yet designed a tub that can tell the difference.

The question isn’t whether the bathwater comes with the baby. It always does. The question is whether you turn on the tap.

Categories
AI AI: Large Language Models Anthropic

Breakout

Jack Clark doesn’t panic easily. He spent years at OpenAI watching capabilities inch upward, then left to co-found Anthropic, and has been writing his Import AI newsletter long enough to have developed — and been wrong about — many priors. So when he publishes an essay saying he has reluctantly arrived at a 60% probability that fully automated AI R&D happens by the end of 2028, the word “reluctantly” deserves some weight.

His essay, published last week and titled “Automating AI Research,” isn’t a press release or a fundraising pitch. It reads more like a man thinking out loud at the edge of something large. “I don’t know how to wrap my head around it,” he writes, which is a notable thing to say publicly when you are one of the architects of the thing you can’t wrap your head around.

The argument is built from benchmarks — not any single one, but a mosaic of them assembled to reveal a trend. SWE-Bench, the test that measures an AI’s ability to solve real GitHub issues, was at roughly 2% when it launched in late 2023. A recent Anthropic model sits at 93.9%, effectively saturating it. METR’s time-horizon plot tracks how long an AI can work independently before needing human recalibration: 30 seconds in 2022, 4 minutes in 2023, 40 minutes in 2024, 6 hours in 2025, 12 hours today. The trajectory, if it holds, suggests 100-hour autonomous work sessions by the end of this year.

Clark marshals similar progressions across AI fine-tuning, kernel design, scientific paper replication, and even alignment research itself. His throughline is the same in each: AI is now genuinely competent at the unglamorous scaffolding of AI development — the debugging, the experiment runs, the parameter sweeps, the code reviews. And crucially, it can now do these things not just faster than humans, but for longer, with less supervision.

There’s a Thomas Edison quote at the center of the essay: “Genius is 1% inspiration and 99% perspiration.” Clark’s claim is that AI has become very good at the perspiration. The question of whether it can supply the inspiration — the paradigm-shifting insight, the Move 37 — remains open. But he argues it may not need to. Most of what has moved the AI field forward has been sustained, methodical work, not lone flashes of genius. If you can automate the 99%, you have something that compounds.

There’s a data point that makes Clark’s argument feel less like forecast and more like dispatch. Last month Boris Cherny, who runs Anthropic’s Claude Code, disclosed that he hasn’t written a line of code by hand in more than two months. Every pull request — 22 one day, 27 the next — written entirely by Claude. Company-wide, roughly 70–90% of Anthropic’s code is now AI-generated. Anthropic’s stated position: “We build Claude with Claude.” The loop Clark is describing as a probability by 2028 is already running, at least partially, today.

The word Clark uses for the threshold he’s describing is not “singularity” or “AGI.” It’s quieter than that. He calls it “automated AI R&D” — the point at which a frontier model can autonomously train its own successor. It’s a specific, falsifiable thing. And he puts a number on it: 60% by end of 2028, 30% by end of 2027.

I’ve been writing about the dark software factory and the 3D printer that prints better printers, finding metaphors for what seems like an inexorable process. Clark’s essay is a different kind of writing about the same thing — the primary source document, the engineer’s log, the inventory of evidence. Reading it is a little like watching someone carefully pack boxes before a move. Each individual item seems manageable. But there are a lot of boxes.

What he’s describing — if the trend holds — is not a feature or a product launch. It’s a breakout. The moment the loop closes and the system starts building itself. He’s not certain it happens. He just thinks it’s more likely than not, and he thought you should know.

Categories
AI Business Work

The Tipping Point Was Last November

Matthew Prince, Cloudflare’s CEO, said something on today’s earnings call that I keep turning over. He didn’t bury it or soften it. He named a date.

“Internally, the tipping point was last November.”

That’s a specific thing to say. Not “we’ve been on a journey” or “AI has been transforming our industry.” A month. A moment. The thing changed, and he knows when.

What changed, by his account, is that Cloudflare’s teams began seeing productivity gains so dramatic they were hard to describe — people who were two times more productive, ten times, in some cases a hundred times. “It was like going from a manual to an electric screwdriver.” Usage of AI tools internally is up more than 600% in just the last three months. Every line of production code is now reviewed by an autonomous AI agent.

And then he said goodbye to 1,100 people — about 20% of the company.

Today wasn’t just Cloudflare. Earnings season has become something like a drumbeat. Meta is cutting 8,000 employees this month. Amazon cut 16,000 in Q1. Oracle eliminated roughly 30,000 to fund AI infrastructure. Block cut almost half its workforce. PayPal is reportedly planning to cut 20% of its staff over the next few years. Coinbase cut 14%. Snap cut 16%. As of this week, more than 92,000 tech workers have been laid off in 2026 alone.

The scale is striking. But what strikes me more is the framing — the specific language being used to describe what’s happening. These aren’t being announced as cost-cutting moves or post-pandemic corrections, the way they might have been in 2022. They’re being announced as architectural decisions. Structural adaptations. Evolution.

Prince was careful to be explicit: “This isn’t a cost-cutting exercise or an assessment of individuals’ performance. It’s about defining how a world-class, high-growth company operates and creates value in the agentic AI era.” That’s not empty corporate language, or at least not only empty corporate language. The distinction he’s drawing — between trimming fat and reimagining how a company is built — maps to something real about what AI agents can now actually do.

There’s a legitimate version of this argument and a convenient one, and they’re being delivered in the same sentence by the same people, which makes them hard to separate. Some analysts suspect companies are using AI as cover for cuts they wanted to make for other reasons — rightsizing from pandemic-era overhiring, funding massive infrastructure buildouts, chasing margin. Oxford Economics flagged this: maybe some firms are “dressing up layoffs as a good news story.” The cynicism is warranted.

But then there’s the Cloudflare number: 600% increase in AI usage in three months. That’s not a narrative. That’s a measurement.

What’s different about this moment — what makes Prince’s “tipping point” language feel accurate rather than convenient — is that the people making these decisions are themselves users of the tools. They’ve seen the productivity numbers internally before anyone else has. They’re not theorizing about what AI might do to their workforce; they’re describing what it already did.

That’s the thing that changed. For years, AI’s labor impact was a future tense conversation. Economists studied it, think pieces warned about it, conferences debated the timeline. Then, somewhere around last November apparently, a cohort of technology companies crossed from hypothetical to empirical. The future tense became past.

Whether you read that as tragedy, as transformation, or as both depends on where you’re standing. 1,100 people at Cloudflare today are standing somewhere very specific. Prince acknowledged this with what felt like genuine difficulty: “A number of friends will no longer be colleagues.” Whether that difficulty changes anything material for the people leaving is a fair question.

But the acceleration itself — the thing he named — is real. The tipping point was last November. And if it was last November for Cloudflare, it was some nearby month for Amazon, for Meta, for Block, for all of them. Whatever these companies learned that changed everything, they all seem to have learned it around the same time.

That’s what I find myself sitting with today: not just the scale of the disruption, but the synchrony of it. The realization arrived, and then the decisions followed. Quietly at first, then all at once.

Categories
Business Creativity Space SpaceX

Test like you fly!

There’s a phrase in the SpaceX documentary that keeps coming back to me: “Test like you fly.” It sounds like a slogan. The kind of thing that gets painted on a factory wall and eventually stops meaning anything. But the more I sit with it, the more I think it’s actually a philosophy that reaches well beyond rocket engineering.

The video — a 25-minute documentary SpaceX released last week — is ostensibly about Starship Version 3. New ship, new booster, new engines, new pad, new test site. Everything rebuilt. And they’re not shy about framing it as a reset, not an upgrade. One description I read called it “a quiet violence in progress.” That phrase stopped me cold, because it’s exactly right. Progress that looks violent from the outside — all that fire and metal — but is somehow quiet in its inevitability.

What moved me watching it wasn’t the engines. It was the engineers. SpaceX put the people on camera: the ones running cryogenic pressure tests at 80 Kelvin, stress-testing tank structures at 70% proof, explaining their failures and their data with the flat affect of people who have made peace with how long hard things take. There’s something almost monastic about it. You choose a problem that will not yield easily. You accept that the work will outlast any individual sprint of enthusiasm. You go back to it anyway.

I keep thinking about that in the context of what we’re doing with AI — the other enormous, fast-moving project that I spend so much of my mental energy on. The development arc is different: iterative releases, weeks not years between jumps, demos that blur into deployment. But the same principle is buried in there somewhere. The best AI teams I read about aren’t the ones shipping the most polished demos. They’re the ones building infrastructure for failure — evals, red-teaming, structured feedback loops. Test like you fly.

The Raptor 3 engines now produce 280 metric tons of thrust each. Thirty-three of them on a Super Heavy booster means over 17 million pounds of liftoff force. I have no intuitive frame for that number. What I do have a frame for is what those numbers represent: three years of iteration on top of five years before that, on top of a theoretical foundation laid by people who didn’t live to see any of this. There’s a compounding in that which I find genuinely moving. Nobody built the Raptor 3 in isolation. It came from everything that broke before it.

The hardest part of the documentary isn’t the engineering. It’s the implicit acknowledgment of how much remains undone. No Starship has yet achieved full orbital velocity with both stages intact. In-space refueling is still untested. The thermal protection systems need more work. And yet — SpaceX talks about unmanned cargo missions to Mars before the end of this year like it’s on the roadmap, not the wish list. That sentence used to sound like marketing. Watching the footage, it doesn’t anymore.

I’m not sure what to do with that feeling exactly. It’s something between awe and vertigo. We’re living in a moment when the audacious has started to have quarterly milestones. When the impossible keeps showing up on timelines and then — bewilderingly, uncomfortably — meeting them.

Test like you fly. Fail with rigor. Build the thing you actually need, not the thing you could more easily explain.

I keep turning that over. There’s a post in there somewhere about writing, too — about the drafts nobody sees, the structural tests that fail, the versions that taught you the one that worked. But that’s for another day.

For now I’m just sitting with the footage of those 33 engines lighting up, and the quiet weight of how much went wrong before they could do that.