Tag: decision making

Categories
Aircraft History

The Merlin

There is a sound that men who heard it never forgot. Not the roar exactly, though it roared. Something beneath the roar — a note, almost musical, that settled into the chest and stayed there. Four Rolls-Royce Merlins at full throttle on a Lancaster climbing out of Lincolnshire in the dark, and sixty years later old men would close their eyes trying to describe it and find they couldn’t, not quite, which was itself a kind of description.

The engine was a miracle of the wrong era. Liquid-cooled, sixty degrees of vee, twenty-seven liters of displacement producing over a thousand horsepower from something you could fit in a large kitchen. Rolls-Royce had been making engines since 1906, had learned things about metallurgy and tolerance and the behavior of superheated gases under compression that couldn’t be written down, only accumulated, passed hand to hand through decades of making things that had to work when nothing could be allowed to fail. The Merlin was the distillation of all of it.

And then — this is the part that stops you — they couldn’t build enough of them.

Britain in 1940 was a country running on nerve. The factories were working. The workers were willing. But the math was brutal and the math didn’t care about willingness. So someone made a phone call to Detroit. To Packard. A company that had spent thirty years building luxury automobiles for American industrialists, cars with interiors like drawing rooms on wheels, cars that announced their owners had arrived at exactly the place they had always intended to be. Packard looked at the Merlin blueprints, converted the tolerances from imperial to metric and back again, retooled their entire production line, and started building the engine that would power the Spitfire, the Hurricane, the Lancaster, and the P-51 Mustang.

Think about what that required. Not just the engineering, though the engineering was extraordinary. The belief required. That these tolerances mattered. That this particular arrangement of pistons and supercharger vanes and coolant passages was worth the disruption of an entire industrial operation. Packard’s engineers didn’t question the design. The design had already proven itself.

You built the Merlin because the Merlin worked.

The question — the one that takes longer to arrive — is what you do when the thing the Merlin is for doesn’t.

Arthur Harris believed.

That is the first thing to understand about him, and maybe the last. He believed in the bomber the way certain people believe in a technology so new and so powerful that the believing itself feels like vision. Strategic bombing would break Germany. Not assist in breaking Germany. Not contribute to a larger effort that would break Germany. Would, by itself, through the systematic destruction of German cities and the German will to continue, end the war. Harris had held this view before the war began and he held it after the evidence came in and he held it, unmodified, until he died in 1984.

This is not stupidity. The most costly certainties never are. Harris was shrewd, forceful, organizationally gifted, genuinely courageous in the sense that he was willing to send men to die for what he believed and knew he was sending them. He understood logistics, understood morale, understood the brutal arithmetic of attrition. What he could not do — what the structure of his certainty would not permit — was update.

The evidence arrived slowly enough that you could always explain it away. German war production increased through 1943, then through 1944, even as the bombers came night after night. The factories dispersed. The workers adapted. The morale that was supposed to crack showed instead a remarkable tendency to consolidate under pressure, the way populations sometimes do when the threat comes from the sky and cannot be reasoned with. The theorists had a model of human psychology that turned out to be wrong, and the model’s wrongness kept arriving in the data, and Harris kept flying.

Fifty-five thousand men.

Picture Harris alone. The commander in the early morning after the casualty reports come in, before the day’s work begins again. The loneliness of a certainty that has become structural — no longer a belief you hold but a belief that holds you, because the alternative is not just being wrong but having been wrong, which means all those boys went down over the Ruhr for a theory, which is a weight no living person can carry and continue to function. So you don’t revise. You recommit. You ask for more aircraft, more crews, more nights.

You build more Merlins.

This is the mechanism. Not malice. Not indifference. The certainty becomes self-protective, which means it becomes invisible, which means it becomes the water you swim in rather than a position you hold. Harris stopped being a man with a theory about bombing and became a man for whom bombing was the answer to every question, including the question of whether bombing was working.

The Lancaster crews knew something was wrong before Harris did. You could see it in the casualty rates, which they could calculate as well as anyone — better, actually, because they were doing the calculating with their own lives as the variable. Forty-four percent didn’t survive their tours. They knew this. They flew anyway, because courage doesn’t require certainty about the strategic framework, only about the man beside you and the mission tonight.

The Merlin started and you went.

The Merlin outlasted the theory. It kept flying for decades after the war, in civilian aircraft, in racing planes, in the occasional restored Lancaster that still tours airshows in Britain, where crowds gather on summer afternoons to watch it pass and hear, carried on the wind, that sound. The note beneath the roar. The thing that settles in the chest.

Beautiful, people say, watching it go.

And it is. It genuinely is.

What they couldn’t know — what none of them could know — was that the engine was the most reliable thing in the entire enterprise.

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
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
AI AI: Transformers Books

The Updating Machine

Tom Chivers puts Bayes’ theorem in plain English and it sounds almost obvious: “the probability of event A, given event B, equals the probability of B given A, times the probability of A on its own, divided by the probability of B on its own.” A formula for revising what you believe when new evidence arrives. You started somewhere. Something changed. Now you believe something slightly different. Repeat.

The obvious part is the mechanics. The hard part is the loop.

Most reasoning errors I catch in myself aren’t failures of logic — they’re failures to update. I hold a view, evidence accumulates against it, and I find reasons the evidence is flawed rather than reasons the view might be.

Psychologists have a name for this: confirmation bias. But I’ve always found that label a bit too clean, like it describes a bug rather than a feature.

The prior isn’t wrong to be sticky. It represents everything you’ve learned up to this point. The problem is when it becomes load-bearing — when the prior stops being a starting position and starts being a conclusion.

“Strong opinions, loosely held” is supposed to solve this. It’s a useful phrase — it captures something true about the right posture toward your own beliefs. But in practice the second half is harder to honor than it sounds. The strong opinion gets stated, new evidence arrives, and changing your mind in public feels like losing. The “loosely held” part quietly becomes decorative.

What Bayes actually demands is something closer to epistemic humility with arithmetic attached. You don’t get to say I don’t know. You have to say I estimate 0.4, and here is what would move me to 0.6. That’s harder. It requires you to specify not just what you believe but how you’d know if you were wrong.

This is why Bayesian thinking keeps surfacing in AI conversations. Modern language models do something structurally adjacent to this — not consciously, but mechanically. Every token generated is a probability distribution revised forward by context. The model doesn’t know the next word; it updates a prior over all possible words, given everything that came before. It’s not reasoning the way humans reason, but it’s updating the way Bayes updates: continuously, contextually, without the luxury of certainty.

Whether that’s comforting or unsettling probably depends on your own prior.

The deeper thing Chivers is pointing at, I think, is that Bayesian reasoning is essentially a description of intellectual honesty as a process rather than a trait. You can’t just decide to be open-minded. You have to build the loop: form a belief, assign it a probability, watch for evidence that should move it, and then actually move it. Most of us do the first three. The fourth step is where it gets expensive.

I’ve been wrong about enough things by now that I’ve started to treat my own confident views with mild suspicion. Not paralysis — you have to act on something — but a background awareness that the prior I’m acting on was formed by a person who had less information than I do now, and less than I’ll have next year.

Strong opinions, loosely held, sounds right. The trick is meaning it.

Categories
AI Business

The Topography of a Face

I found myself staring at the physical geometry of a conversation the other day—not the words, but the topography of the faces delivering them.

Elad Gil recently shared a fascinating experiment during a conversation with Tim Ferriss. He’s been uploading photos of startup founders into AI models and asking the machines to predict if they’d be successful, purely based on their “micro-features.”

“Because if you think about it, we do this all the time when we meet people, right? We quickly try to create an assessment of that person, their personality, and what they’re like. There are all these micro-features—like, do you have crow’s feet by your eyes, which suggests that your smiles are genuine? […] So, I have this whole set of prompts that I’ve been messing around with, just for fun, around: ‘Can you extrapolate a person’s personality based off of a few images?'”

He notes the model breaks down the crow’s feet and the furrowed brows, extrapolating a personality from a static frame. It’s a parlor trick, perhaps. But it works because it holds a mirror to our oldest, most unexamined instinct.

We are all amateur phrenologists of the human face. We sit across a table, measure the crinkle of an eye or the tightness of a jaw, and we build a rapid, invisible architecture of trust or suspicion. Over decades of investing and making career choices, I’ve often leaned heavily on this silent language. I’ve backed founders because their intensity felt genuine, and I’ve passed on others because something in their posture felt misaligned.

But if I am brutally honest, that intuition has sometimes been a mask for my own blind spots. I’ve held on to failing investments for far too long because I trusted a reassuring smile. We like to think our gut instinct is a sophisticated instrument. Often, it is just a pattern-matching engine running on deeply flawed historical data.

Now, we are handing that very human habit over to a machine. We prompt the AI to become a “cold reader,” and it obliges, predicting who will be the quiet observer and who will deliver the dry wit.

The unsettling part isn’t that the machine might get it wrong. The unsettling part is that it might get it exactly right—by mimicking the very same rapid, superficial judgments we make every day, just at a terrifying scale.

We are teaching silicon to read the human code. The future will belong to those who realize the code was always written in our own biases.

Categories
Living Serendipity Travel

The Conditions of the Unexpected

There is a flight I took in 2001 that I have never fully stopped thinking about. Not the flight itself — a forgettable three-hour hop in a middle seat — but the two-hour delay that preceded it. The gate agent’s apologetic crackling over the intercom. The way I surrendered to the terminal, found a bar stool, ordered something I didn’t need. The man next to me was reading a book I recognized. We talked for two hours. He told me about a job. I didn’t take it — but I spent three months considering it, which is its own kind of detour. I came out the other side different in ways I still can’t fully account for.

I have told this story before as a story about luck. I’m not sure that’s what it is.

Alexander Krauss spent years going through the records of science’s major discoveries — Nobel Prize winners, the landmark non-Nobel findings, more than 750 in all — looking for the mechanism behind what everyone had been calling serendipity. The telescope trained on an unexpected patch of sky. Fleming’s contaminated petri dish. The chance observation that shouldn’t have meant anything but did.

What he found upended the romance of the story. The discoveries that seemed most accidental, most shaped by the caprice of an unlucky sneeze or a mislabeled sample, turned out to follow a pattern. Nearly all of them happened shortly after a researcher gained access to a new tool. The accidental observation of cells under an improved microscope. X-rays discovered through a discharge tube nobody had pointed in that direction before. The first planet beyond our solar system, caught by a spectrograph that hadn’t existed a few years earlier. What looked like lightning striking the same improbable spot again and again was actually the same thing each time: a new instrument creating the conditions under which something unexpected could be seen.

Krauss calls this “engineering serendipity.” The phrase stops me every time I read it, because it sounds like a contradiction and turns out to be the most practical sentence in the philosophy of discovery. You can’t engineer the specific surprise. But you can engineer the conditions that make surprise likely. You can build the lens before you know what it will show you.

This distinction — between engineering an unexpected discovery and engineering the conditions for unexpected discovery — is one I’ve been carrying around like a stone in my pocket. Because I think it applies far outside the laboratory. I think it’s one of the central design problems of a life.

The book trend critics are calling “Digital Nostalgia” is, depending on how you read it, either the most sentimental or the most diagnostic thing happening in literary culture right now. The novels topping lists this spring are full of people losing their recordings, waking up in centuries without algorithms, mourning the weight of analog things. Ben Lerner’s new novel begins with a dropped phone in a hotel sink — the recording gone, the moment unrecoverable. Caro Claire Burke’s Yesteryear sends a social-media influencer back to an 1855 that is nothing like the one she curated for her followers: cold, filthy, unfiltered, and somehow more real.

What readers are reaching for in these books is not the past per se. It’s the texture of a life that wasn’t predicted in advance. The feeling of not knowing what came next because nothing had pre-sorted the possibilities. Nostalgia, in its root meaning, is pain at being far from home. What Digital Nostalgia seems to be mourning is something more specific: the disappearance of accident from everyday life.

I notice this in small ways. My phone knows where I’m going before I’ve decided to leave. The algorithm has predicted, with unsettling accuracy, what I will want to read next. The coffee shop I found by walking down an unfamiliar street now gets recommended to me, which is useful and also somehow diminishes the thing I found. The city I live in has become a more efficient version of itself. Less of it surprises me than used to.

This is not entirely bad. But something is lost in the smoothing. And the books people are buying tell you what.

The urbanist argument for cities has always included, at some level, an argument for density as a serendipity engine. You put people in proximity. You make them share transit and sidewalks and bars and parks. Intersections happen. Ideas cross. The great creative explosions of modern history — Florentine painting, Viennese psychoanalysis, the Bell Labs cafeteria — were products less of individual genius than of designed proximity. People who wouldn’t have met each other kept meeting each other.

What’s interesting about Krauss’s argument is that it generalizes this principle to the history of science in a way that makes it quantifiable. It’s not just that cities were generative because they were dense. It’s that they were generative because they were full of new tools — printing presses, coffeehouses, salons — that created new surfaces where minds could collide and refract in new ways. The tool doesn’t make the discovery. It makes the discovery possible, and likely, and reproducible by others.

Which brings me back to the airport bar.

The two-hour delay created an unstructured interval I hadn’t planned for. I didn’t know what to do with it, so I sat somewhere I wouldn’t normally have sat. The man next to me had a book that served as an opening. We were both temporarily outside our routines, which is another way of saying: we were both in a new instrument, looking at something we hadn’t known to look for.

What I’ve been slow to admit is that this kind of moment doesn’t just happen. It happens to people who are outside their routines. It happens in places where unlike people are forced into proximity. It happens when you sit down somewhere without your headphones, without a screen to retreat into, in the condition of being briefly unoptimized. The delay was the tool. The discovery followed.

So here is the tension I keep returning to: you can engineer the conditions for serendipity, but you cannot engineer serendipity itself, and the engineering has to be genuinely open-ended or it stops working. If you design a system that produces specific surprises, you haven’t built a serendipity engine. You’ve built a surprise dispenser, which is a different and lesser thing. Amazon’s “you might also like” feature is not serendipity. It is prediction wearing serendipity’s clothes.

The difference is whether the system preserves its capacity to show you something it didn’t know you needed to see. A new microscope could reveal anything. A recommendation algorithm reveals only a constrained neighborhood of the space of things you’ve already wanted. The former is a lens. The latter is a mirror.

I think this is what the Digital Nostalgia readers are grieving, without quite being able to name it: not the analog past itself, but the unoptimized interval. The moment between knowing what you wanted and finding it, when anything might happen. That space has been shrinking for twenty years, and the algorithm’s promise — to eliminate friction, to anticipate, to smooth — has turned out to be partly a promise to eliminate possibility.

The question I’m sitting with is whether it’s recoverable. Not globally — I’m not interested in the manifesto version of this argument, the call to smash the phones or return to the forest. But personally. Whether I can design my own life to include enough genuine aperture — enough unoptimized intervals, enough new tools, enough places where I am briefly outside my routine and available to be surprised — to keep the surprises coming.

I have some guesses about what this looks like. Reading outside my field. Saying yes to the conversation I don’t have time for. Choosing the longer route. Leaving earlier so the delay doesn’t feel like a crisis.

These are small things. They are also, if Krauss is right, approximately how all the important discoveries get made.

The flight eventually boarded. I didn’t take the job. But I thought about it for three months, which means I thought about my actual life for three months — what I wanted from it, what I was settling for, what I hadn’t been willing to name. The man at the bar didn’t change my path. He changed my angle of view, briefly, enough. I’ve been a little suspicious of smooth trips ever since.

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.

Categories
Investing Living

The Lonely Quadrant: Why the Crowd Never Outperforms

There is a profound comfort in the consensus. When we agree with the crowd, we are protected by a shared canopy of logic. If we are wrong, we are wrong together. The sting of failure is diluted by the sheer number of people who made the exact same miscalculation. We can shrug our shoulders, look at our peers, and say, “Who could have known?”

But this comfort comes at a steep price: mediocrity.

Years ago, the legendary investor Howard Marks crystallized a framework that has haunted my thinking ever since. He mapped out the relationship between predictions and outcomes, arriving at a blunt, inescapable truth about generating extraordinary results. To make really good money—or to achieve outsized success in almost any competitive endeavor—you cannot simply be right. You have to be right when everyone else is wrong.

“You can’t do the same things others do and expect to outperform.”

Marks’ logic is beautifully ruthless. If your prediction aligns with the consensus and you are right, the rewards are merely average. The market, or the world, has already anticipated and priced in that outcome. There is no edge in seeing what everyone else sees. If your consensus prediction is wrong, you lose, but you lose alongside the herd.

The danger, and the opportunity, lies in the contrarian view.

If you are non-consensus and wrong, you look like a fool. You bear the entirety of the failure alone, stripped of the insulation of the crowd. This is the quadrant of public mockery, isolated defeat, and bruised egos. It is the fear of this quadrant that keeps most people safely tucked inside the consensus.

But the magic—the life-changing returns, the paradigm-shifting innovations, the profound personal breakthroughs—lives exclusively in the final quadrant: being non-consensus and right.

This isn’t just an investing principle; it’s a philosophy for navigating life. We are biologically wired to seek the safety of the herd. To step outside of it requires not just immense intellectual conviction, but a formidable emotional threshold. You have to be willing to sit with the discomfort of being misunderstood, sometimes for years. You have to endure the sympathetic smiles of peers who think you’ve lost the plot.

Creating truly great art, building a lasting company, or making an exceptional investment demands a willingness to be lonely in your convictions. It requires looking at the exact same data as everyone else and seeing a completely different narrative.

However, a vital caveat remains: being different isn’t enough. There are plenty of contrarians who are simply wrong, confusing blind rebellion with profound insight. The goal isn’t to be a contrarian for the sake of being difficult or edgy. The goal is to perceive a truth the crowd has missed.

It is a quiet, solitary bet against the world’s prevailing wisdom. And when the world finally catches up to where you have been standing all along, the reward is entirely yours.

Categories
Probabilities

The Fiction of Certainty

There is a profound discomfort in the space between zero and one.

In her book Spies, Lies, and Algorithms, Amy B. Zegart notes a fundamental flaw in our cognitive architecture:

“Humans are atrocious at understanding probabilities.”

It is a sharp, unsparing observation, but it is not an insult. It is an evolutionary receipt. We are atrocious at probabilities because we were designed for causality, not calculus. On the savanna, if you heard a rustle in the tall grass, you didn’t perform a Bayesian analysis to determine the statistical likelihood of a lion versus the wind. You ran. The cost of a false positive was a wasted sprint; the cost of a false negative was death.

We are the descendants of the paranoid pattern-seekers. We survived because we treated possibilities as certainties.

The Binary Trap

Today, this ancient wiring misfires. We live in a world governed by complex systems, subtle variables, and sliding scales of risk. Yet, our brains still crave the binary. We want “Safe” or “Dangerous.” We want “Guilty” or “Innocent.” We want “It will rain” or “It will be sunny.”

When a meteorologist says there is a 30% chance of rain, and it rains, we scream that they were wrong. We feel betrayed. We forget that 30% is a very real number; it means that in three out of ten parallel universes, you got wet. We just happened to occupy one of the three.

Zegart operates in the world of intelligence—a misty domain of “moderate confidence” and “low likelihood assessments.” In that world, failing to grasp probability leads to catastrophic policy failures. But in our personal lives, it leads to a different kind of failure: the inability to find peace in uncertainty.

Stories > Statistics

We tell ourselves stories to bridge the gap. We prefer a terrifying narrative with a clear cause to a benign reality based on random chance. Stories have arcs; statistics have variance. Stories have heroes and villains; probabilities only have outcomes.

To accept that we are bad at probability is an act of intellectual humility. It forces us to pause when we feel that rush of certainty. It asks us to look at the rustling grass and admit, “I don’t know what that is,” and be okay with sitting in that discomfort.

We may never be good at understanding probabilities—our biology fights against it—but we can get better at forgiving the universe for being random.

Categories
Business

The Geometry of Focus: Finding the Limiting Factor

In the modern landscape of high-stakes management, there is a recurring temptation to solve everything at once. We are taught to optimize across the board—to improve efficiency by 2% here, 5% there—until the entire machine hums. But in a recent conversation with John Collison and Dwarkesh Patel, Elon Musk repeatedly returned to a single, almost obsessive mantra: the “limiting factor.”

It is a deceptively simple phrase. It suggests that at any given moment, there is one specific bottleneck that dictates the speed of the entire enterprise. If you aren’t working on that, you aren’t really moving the needle. You are merely polishing stuff.

“I think people are going to have real trouble turning on like the chip output will exceed the ability to turn chips on… the current limiting factor that I see… in the one-year time frame it’s energy power production.”

Musk’s management technique is not about broad oversight; it is about a radical, almost violent prioritization. He looks at the timeline—one year, three years, ten years—and asks: What is the wall we are about to hit? Right now, it might be the availability of GPUs. In twelve months, it might be the physical gigawatts of electricity required to plug them in. In thirty-six months, it might be the thermal constraints of Earth’s atmosphere, necessitating a move to space.

This approach requires a high “pain threshold.” To solve a limiting factor, you often have to lean into acute, short-term struggle to avoid the chronic, slow death of stagnation. John Collison noted this during the interview:

“Most people are willing to endure any amount of chronic pain to avoid acute pain… it feels like a lot of the cases we’re talking about are just leaning into the acute pain… to actually solve the bottleneck.”

For many leaders, the “limiting factor” is often something they aren’t even looking at because it lies outside their perceived domain. A software CEO might think their limit is talent, when it’s actually the speed of their internal decision-making. A manufacturer might think it’s raw materials, when it’s actually the morale of the factory floor.

To manage by the limiting factor is to admit that 90% of what you could be doing is a distraction. It is a philosophy of subtraction and focus. It demands that we stop asking “What can we improve?” and start asking “What is stopping us from being ten times larger?” Once you identify that wall, you throw every resource you have at it until it crumbles. And then—and this is the part that requires true stamina—you immediately go looking for the next wall.

By focusing on the one thing that matters, we stop being busy and start being effective. We stop managing the status quo and start engineering what may feel like the impossible.