But there is a question those essays did not answer, and it has started to feel like the only one that matters. If you can build anything, what should you build?

For most of history this question was academic, because you could not build anything. Capability was the constraint. The thing you could imagine was always far ahead of the thing you could make, and so the scarce resource, the thing worth organizing your life around, was the ability to build at all. That is what the three essays were about. Acquiring it. Refusing to wait for permission to have it.

That constraint is dissolving. Not gone, but dissolving faster than most people have adjusted to. When the cost of building collapses, building stops being the bottleneck. And whatever stops being the bottleneck stops being the scarce thing.

The scarce thing is now knowing what is worth building.

I have helped build things that, looking back, were not worth building, and I did not always know it at the time. The building was rarely the problem. The people were good at building. The trouble lived upstream, in the choosing, which is a harder and lonelier act than it gets credit for. A thing gets picked, ratified, funded, handed down, and somewhere in that chain the question of whether it was worth solving never quite gets asked out loud. The building is clean. The choosing is not. And no amount of clean building rescues a problem that was not worth solving.

There is a second failure, quieter than the first. Sometimes the right thing does get chosen, and then no one asks what it is actually for. It gets built, shipped, and its value assumed rather than traced. Choosing what to build and knowing why it matters turn out to be the same act, and it is easy to do only the first half.

The Climb With No Top

There is a question I have learned to keep asking, of others and of myself, and it is not a popular one in a meeting. Someone proposes a thing to build, explains its value, and the honest next question is: so what? You answer. And the question comes again: so what?

It can feel like obstruction. But I have not found a better way to tell whether a thing has value or only appears to, and I include my own proposals in that. Every justification invites the same question of the thing above it, and you keep climbing. We can automate this. So what? So we need fewer people to do it. So what? So it costs less. So what? So we can do other things. So what? And here, usually, the answers get vague, or someone says it is what someone above them asked for, and the climbing stops.

This is the infinite regress problem, and it is old. Every reason rests on another reason. Every “this matters” can be met with “why,” and the answer to the why can be met with another why, forever. The chain does not end on its own. It only ends when someone decides to stop climbing. The whole question of what is worth building comes down to where, and why, that climbing stops.

Say-So, or the World

There are two ways the climb can stop, and the difference between them is everything.

The first way is that someone with authority declares it stops. A leader decides the metric matters. It gets written into a plan. The regress halts because the org chart says it halts, not because anything outside the organization confirmed it. Call this the terminal outcome problem: the stopping point feels final, but its finality is borrowed entirely from the person who declared it. Replace the person and the terminal state can evaporate. The thing that was obviously worth building last year is quietly defunded this year, and nothing in the world changed. Only the internal agreement did.

A great deal of good work gets built this way, mine included. There is nothing dishonest about it. Conviction has to start somewhere, and often a leader’s judgment is the best signal available. But it is fragile in a specific way: its value cannot survive the question so what reaching all the way to the top, because at the top there is only someone’s say-so.

The second way the climb stops is that it reaches something outside the organization that does not answer to anyone inside it. A customer who stays or leaves. A market that prices the thing up or down. A risk that turns out to be real or not. Someone who pays, or does not. These validators do not negotiate. You cannot redefine your way into a customer staying. You cannot ratify a market into agreement. They sit outside the system that produced the work, which is exactly what makes them trustworthy: they have no stake in your story about why the work matters.

When the climb ends here, it ends because the world confirmed it, not because a person did. That is what a real terminal outcome looks like. The regress stops at revealed preference, and it stays stopped even after the leadership changes.

So the first test of anything worth building is simple, though it is uncomfortable to apply to your own ideas. Does the chain of so what end at something external and impartial, or does it end at someone’s say-so? If the latter, you do not have a terminal outcome yet. You have a conviction that will hold exactly as long as the person behind it does.

Too Far to Carry

But passing that test is not enough, and this is the part I missed for the longest time. You can have a real external validator at the end of the chain and still be building something whose value you will never be able to claim. Because the chain can be long.

Watch one stretch out. We reduce cost, so we free up capacity, so we do more work, so quality improves, so more people use the product. The last link, people using the product, is externally validated. Users decide that; the organization does not get a vote. The terminal outcome is real.

Now count the steps, and notice what lives in each gap. Cost reduction has to actually fund something, not just disappear into the next budget. The freed capacity has to go toward work that matters, not more meetings. More work has to improve quality, but volume is not quality, and it often is not. Better quality has to change whether people adopt, but mature products are held by lock-in, habit, and switching costs that dwarf any marginal improvement. By the time the signal from “reduce cost” reaches “more users,” it has passed through five noisy joints, and there is almost nothing left of it. Any one of a hundred other things could explain the outcome. Your work cannot credibly claim it.

This is the lossy chain problem, and it is in some ways more dangerous than having no validator at all. When there is no external validator, the absence is at least visible; everyone can see the work rests on someone’s say-so. But when there is a real validator at the far end of a long chain, it provides cover. It becomes easy, and tempting, to point at the distant, legitimate outcome and let people assume the work caused it. The claim cannot really be falsified, because the chain is too long to trace. The work feels grounded. It may not be. It can be optimism wearing the shape of an outcome. And I have made exactly that claim about my own work and believed it.

So the bar is two-edged: the chain of so what has to reach something external, and it has to be short enough that the signal survives the trip. Most work will not clear it, and that is fine. Not everything needs to. Some of the most important work, the enabling and infrastructural kind, has no short path to an external signal, and pretending otherwise just produces dishonest metrics.

There is a discipline that follows from this, and it is not “find an external validator.” It is find the nearest one.

Cost reduction was never the real outcome anyway. It is always in service of whatever the savings get spent on. The value lives in the reallocation, not the reduction. Which means the honest thing to measure is what the recovered capacity actually produced, measured right where it produced it, not five steps downstream where the signal is gone. If the savings funded specific work, and that work converts into something external in two or three tight steps, the chain holds and the claim is real. If the only validator available sits at the far end of a long chain, you are not measuring an outcome. You are measuring your optimism about the outcome.

None of this is about how you build. The spec, alignment, and feedback are downstream: you build to discover these things, not the other way around. Whether the thing was worth building is not. That question stays upstream, before the first line.

The discipline is not to reject the work that has no clean signal. It is to know which kind you are doing, and to stop pointing at distant validators as if they were close.

The three essays on building argued that you should build, relentlessly, before you are ready, without waiting for permission. I still believe that. But relentless building has a failure mode the essays did not name: building the wrong thing faster than anyone else. The maniac who picks a problem with no real terminal value, or one buried at the end of a lossy chain, does not get rescued by velocity. They get there sooner, with more conviction, having spent more.

When building was scarce, the scarce skill was the will to build. Now that anyone can build almost anything, the scarce skill is choosing the problem whose value is real before a single line of it exists. The return on what you build is not discovered afterward in a deck. It is decided at the moment you choose what to build, and everything downstream is just collection.

That choice — what is actually worth building — is the last scarce thing.

Pick well. Then build like maniacs.

A Note for the Curious

None of this is original to me, though I arrived at it by argument before I found the names. The endless “so what” is the epistemic regress argument from ancient skepticism. The split between borrowed and real value is the old distinction between instrumental and intrinsic (or terminal) value. And the lossy chain lives in Goodhart’s law (the closer a metric sits to the real goal, the better it holds) and in the statistics of causal mediation, where each noisy step attenuates what you can measure until little survives. I find it reassuring, not deflating, that the same structure turns up in epistemology, ethics, and statistics. It usually means the thing is real.

Every civilization that advanced built its way there. Not planned its way. Not aligned its way. Not waited for the right conditions, the right moment, the right people in the room. Built. Relentlessly, impatiently, often badly, and then better, and then again. The building is what made the conditions right. That has always been the sequence, in every era, in every place that decided it was serious about becoming something.

The same pattern repeats at every scale.

Progress — real progress, the kind that compounds across decades and lifts everything around it — does not come from the best strategies. It comes from the people who could not stop. Build. Learn. Replace. Build again. The act of building is itself the loop. Each version a question asked of reality. Each answer demanding the next build. The spec is in service of the building. The plan is in service of the building. The story, the strategy, the vision — all of it downstream of the thing being made, not upstream of it. This is not how most people think. It is how everything that mattered got built.

The maniacs understand something that everyone around them usually doesn’t. The building itself is the strategy. The loop is the plan.

Build before ready. Replace before forced to. Move before the plan is complete, and then move again. The maniac is not the person who ignores feedback — the maniac is the person organized entirely around it, who cannot imagine not closing the loop as fast as possible, for whom waiting feels like the actual risk. Most cannot do this. They treat building as the final step — the thing that happens after the requirements are locked, the design approved, the risks mitigated, the stakeholders aligned. The substitution — plan instead of build, discussion instead of doing, alignment instead of thing — is comfortable. It looks like diligence. It produces nothing.

Build. Build like maniacs.

When I moved back to India, I expected to feel the weight of what hadn’t been built yet. Anyone who has spent significant time outside and then returned carries a particular kind of double vision — you see what is there, and layered over it, almost like a transparency, you see what might be there, what you have seen elsewhere, what you keep reading is coming. That double vision can be disorienting. It can also be clarifying.

What I found was more interesting than the gap. Loud and unfinished in the way that places are when they are becoming something. Not the infrastructure — the posture. People who had decided not to wait for the conditions to be right, who had looked at the incomplete, messy, inconvenient present and decided it was sufficient to begin.

I had hoped to find this. It is not everywhere, and certainly not evenly distributed. But there are enough maniacs already building that the hope might just turn out to be justified.

The maniacs are the heroes of this story, even if the world hasn’t caught up to calling them that yet. They are building uphill. Against accurate objections and incomplete systems and a world that is, mostly, still waiting for someone else to go first. The first essay was about who gets permission to climb that hill. The second was about how you start before you are ready. This one is about the people who have been climbing the whole time — who did not need the permission, did not wait for the readiness, who looked at the gap and decided that was a reason to move faster.

Every period of civilizational progress has looked like this from the inside. Not orderly. Not careful. Chaotic, fast, relentless, sometimes wrong, always moving. The industrial revolution. The American century. None of it was planned into existence. It was built into existence — by maniacs who treated the current version as a step and woke up the next morning to build the next one, who did not stop when the objections were accurate, who did not stop when the conditions were wrong, who did not stop. The credit came later. It always comes later. In the moment, what the maniacs mostly received was a clear-eyed account of everything that wasn’t going to work.

They built anyway. They are still building. In half-finished offices, on small teams, in countries trying to close enormous gaps. They are not waiting for alignment or permission or certainty. They understand what the rest of the world eventually learns: the conditions are built, not waited for.

This was always for them. For the maniacs.

Build like maniacs.

There is a sequence most people believe in without having chosen to believe it. You learn, then you do. You prepare, then you act. You qualify, then you begin. For a wide range of tasks this is exactly right — you study medicine before you practice it, you learn to drive before you take the highway. The expertise precedes the application, and the world is better for it.

But at the frontier, where the problem has never been solved before and no established path exists, the sequence inverts. The capability does not precede the action. The action produces it. The expertise is not the input — it is the output. Which means the feeling of not being ready, the feeling almost everyone has at the start of something unprecedented, is not a signal to wait. It is a signal that you have found the edge of the known, and the edge is exactly where everything unbuilt gets built.

Louis Pasteur was a chemist, not a physician. Germ theory came from him applying the methods of chemistry to a domain that was not his — over the objections of doctors who said medicine was not his to practice. The founders of molecular biology were physicists, who brought the instincts of their own field to biology. None of them arrived as experts in the thing they ended up creating. They came with rigor from somewhere else and built the new expertise in the doing. Had they waited for the established path before taking the first step, the path would never have gotten built.

This is not an argument for ignoring what is known. Preparation helps, education helps, mentorship helps. The argument is narrower and more hopeful: the capability you feel you are missing at the frontier is not missing. It is waiting on the other side of building.

There is a period I keep returning to. Early in an attempt at something that had not been built before, before it had produced anything worth pointing to, I spent a lot of time with people who understood the territory far better than I did. What I remember is not what they said but the feeling afterward — of having absorbed a complete account of why the thing would be hard, without having gained any of the capability needed to make it less hard. That came later, through iterations that failed in ways I hadn’t predicted and gaps I hadn’t known existed. The capability arrived through the work because there was no other place it could have come from. I had assumed capability was something I needed before I began. It took me too long to realize it was the thing I was there to acquire.

There is a retrospective illusion that hides this, and once you see it you cannot unsee it. When we look at people who are genuinely capable, we see the capability. We do not see the period during which they were becoming capable — it produces nothing worth pointing to yet, and the story always gets told from the endpoint backward, which makes the capability look like a precondition rather than a result. The illusion makes people wait for a readiness that only beginning can produce. Seeing through it is freeing. You are not behind. You are standing where everyone who ever built something new once stood.

This is also the answer to a quieter question — not how we build, but why. We build because building is how the thing that does not yet exist comes into existence, and because it is how we become the people capable of creating it. The future has to be built before it can be fully imagined. The work changes the world a little, and the builder more than a little. For many of the things worth doing, that transformation is not a side effect. It is the point.

So do it anyway — not out of defiance, and not in spite of the difficulty, but because the doing is where everything you are reaching for actually lives: the thing you are building, and the person capable of building it. And this is true at every scale — not only of individuals, but of teams, of companies, of entire countries standing at the edge of what they might become.

And when someone tells you that you cannot build what you do not yet understand.

It is not a warning. It is an invitation.

The future is built before it is understood.

For the last few years, I have been trying to build things with AI in domains that are not mine. Every time the work has gotten close to something that actually matters, someone considerably smarter than me has reminded me that I am not an expert.

They are usually right.

The problem is too contextual. The domain knowledge is too specialized. The edge cases are too numerous. The system is too large. The workflow depends too heavily on human judgment. The stakes are too high. The existing process evolved for a reason.

What makes these objections difficult to dismiss is that many of them are technically true. The problems are contextual. The domain knowledge is specialized. The edge cases are real. The systems are large. Human judgment matters. The stakes are high.

Modern society is built on specialization. We trust surgeons to perform surgery, pilots to fly airplanes, economists to think about economics, and security researchers to think about security. This arrangement works extraordinarily well because the world has become too complex for any one person to understand more than a tiny fraction of it. Specialization is not a flaw in how we organize knowledge. It is the only way we have found to make progress at scale.

But there is a paradox hidden inside it.

If expertise becomes the primary source of legitimacy, then nobody is qualified to create anything genuinely new. The expert in today's system is, almost by definition, an expert in the current system. They understand why things are the way they are. They understand the constraints, the history, the failed attempts, the political realities, the technical debt, and the countless edge cases that outsiders cannot see. This is not a criticism. It is a description of what expertise actually is — a deep, earned familiarity with the way something currently works.

This makes experts invaluable for operating the present. It does not necessarily make them the best people to imagine the future.

That distinction feels important, and it is more uncomfortable than it first appears. Because the implication is not that experts are wrong. The objections are often accurate. And yet, if those objections were always sufficient to stop the work, very little that is genuinely new would ever get built.

The builder is making a different bet — that the current system will eventually be replaced regardless, and that the question is not whether to wait for someone with full credentials to arrive, but whether to start now with incomplete knowledge and improve from there. These are not compatible priors. That is why the conversation tends to end the same way: the builder is reminded they are not an expert, and the expert is confident the reminder is sufficient.

I remember the first time someone walked me through everything that was wrong with what I was building. They were thorough. They understood the domain in ways I did not. Some of what they described, I had already encountered. Most of it, I hadn't. What struck me afterward was not how much they knew — it was how complete the picture felt when they described why the thing wouldn't work. The system they were defending was coherent, well-understood, and clearly the product of hard-won experience.

What they couldn't describe — because they had no reason to — was what the system looked like from the outside. From a position of not-yet-knowing. That is not a lesser vantage point. The expert sees the system so completely that its edges become walls. The outsider sees the same edges and wonders, with genuine curiosity, what is on the other side. That wondering is not ignorance. It is the only place certain questions ever get asked. And asking them — even badly, even without the vocabulary the domain has built up over years — is where new things begin.

I have never found "you are not an expert" to be a satisfying conclusion. It is useful information. It raises real questions worth sitting with. But there is a difference between the fact and the implication, and for a long time I did not have language for that difference.

For years, I walked into rooms where the default assumption was that someone else was more qualified to shape the future than I was. Sometimes that is true. Sometimes they have been in the domain longer. Sometimes they have credentials you don't. Sometimes they have organizational authority. Sometimes they have simply been there first.

And yet, almost everything meaningful gets built by people who ignored the implication of that fact. Not the fact itself. The implication.

The fact is: someone knows more than you do.

The implication is: therefore you should not try.

I have never found a good reason to accept the second.

In the early months, momentum was electric. Learning Linux, navigating endless CUDA debugging sessions, and successfully fine-tuning models on sophisticated datasets felt genuinely exhilarating. I'll never forget when the model went rogue, generating pages of nonsensical text—a surreal reminder of how delicate and powerful AI can be. Or when I ventured into building my first prototype website using GitHub Copilot, marveling at how much could be accomplished with the right tools.

But eventually, complexity overtook progress. Datasets grew heavy, results unpredictable, and priorities shifted beneath me. The runway that once seemed generous began to shrink, and questions changed from "how" to "why."

Deciding to close down was gradual and quietly challenging—like gently fading out a favorite song. Archiving my experiments felt bittersweet, a quiet acknowledgment of effort and acceptance.

Initially, it felt like failure. But with some distance, I see it differently.

Though the original target went unmet, the experience was transformative. It reshaped my relationship with uncertainty, taught humility, and instilled respect for the hidden complexities beneath ambition. Big bets don't always yield immediate success—but their lessons endure.

I close this chapter grateful for the excitement, the challenges, and every unexpected detour. Perhaps the true value wasn't the finish line, but everything the journey revealed along the way.

Addendum to "Scaling Life"

We often imagine growth as linear and predictable, but real life—my life—is much messier. Projects that excite and define us can quietly end in ambiguity, teaching vital lessons about resilience and humility.

One late night, staring at my laptop and a dataset refusing to cooperate, frustration gave way to acceptance and insight. Scaling life isn't about uninterrupted wins; it’s about navigating uncertainty and finding meaning even when outcomes differ from expectations. This quiet ending holds deep lessons—reminding me that genuine growth comes not from constant success, but from learning how to move forward after setbacks.

This is a chapter from an unfolding book about designing a life that expands. I’m writing it as I live it—without pretending to have it all figured out.

There’s a moment that comes after ambition. After the plans. After the discussions. After the first surge of wanting more. It’s the moment when outlines on whiteboards meet the quiet of real life.

That’s Effort. It’s the slow, steady work that follows the spark of ambition. At first, effort feels honest. It feels like proof you meant it when you said you wanted more. You show up every day. You build routines—brick by brick, action by action. The hours add up, and momentum grows.

But over time, effort changes. The bold leaps you pictured become smaller, incremental steps. The clarity you began with fades, and the initial spark grows harder to see. Effort shapes itself into structured work—routines, systems, late nights—yet underneath, it remains the same: a choice to keep moving forward.

For me, putting in the effort feels like a uniquely reliable ‘algorithm’ that steadily compounds into meaningful progress. It’s something uniquely within our grasp—it outpaces talent when talent stops trying, and it outlasts luck when luck doesn’t show up. Even when the odds are against us — it can change the equation.

Like ambition, effort sometimes gets a bad rap. It’s often mistaken for hustle culture, but it’s not about burning out or doing more for the sake of doing. It’s about steady, intentional, and consistent action—reliability over drama. Working hard is often criticized for throwing off work-life balance. But maybe balance isn’t always about equal parts. Maybe it’s about knowing where your effort needs to go—and letting that be enough.

Practicing the Algorithm

I remember clearly the first time I truly faced the Learning Curve—it wasn’t pretty. It started with that familiar rush of confidence—what I've since heard called "Mt. Stupid." Everything seemed obvious, easy, inevitable. Then came what’s called the Valley of Depression. Progress stalled. Every step forward felt exhausting, even meaningless.

My first big project came with high stakes and a lot of unknowns. Initially, fixing each setback felt exhilarating, affirming that I was on the right path. But soon enough, those setbacks piled up—unexpected roadblocks, failed experiments, and late nights spent doubting every decision I'd made. It didn't feel good. It felt tiring and discouraging. I wasn't even sure it was worth continuing.

But here's the thing: I kept going, not because I was driven by certainty, but precisely because certainty was nowhere to be found. Effort became the one reliable thing I had. Each morning, despite how I felt the night before, I got up, adjusted my approach slightly, and moved forward. It wasn't heroic; it was practical. Effort became my lifeline, the steady rhythm beneath the noise.

Roosevelt captured it perfectly: “It is not the critic who counts; not the man who points out how the strong man stumbles... The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...”. Effort was simply about staying in that arena.

Maybe scaling life isn’t about certainty or clean arcs of progress. Maybe it’s just about continuing—especially on the days when things feel unclear, unremarkable, or unresolved. Staying in the arena when there’s no fanfare. Trusting that quiet motion still counts.

If ambition is the spark, then effort is what keeps showing up—even when it’s inconvenient, even when it’s not glamorous. So maybe it’s not about mastering effort. Maybe it’s just about respecting it enough to keep going. Because that’s what effort does—it keeps going. Quietly. Repeatedly. Even when the results haven’t arrived yet.

Effort—steady, deliberate work—is the only algorithm I know that always runs. Timing can shift. Talent can stall. Luck can disappear. But effort is different. It’s the part you can control. The part you can return to. The part that quietly adds up.

There’s a moment that comes before anything begins. Before the plan, before the pivot, before the actual change. It’s the moment you decide you want more. Not more stuff. Just more from your time, your work, your days. More out of the people you spend time with. More clarity in how you show up. A bigger canvas.

That’s ambition. And it’s usually quiet. It doesn’t arrive like a lightning bolt. It just starts tapping on your shoulder until you either pay attention or convince yourself to ignore it. For me, that’s where things began. Not with a project or a job switch or a big leap. Just with a feeling I couldn’t shake — that staying still would slowly turn into going backwards. That there was a version of me out there I hadn’t become yet.

Ambition gets a bad reputation sometimes. People treat it like it’s about ego, or greed, or proving something. But I think real ambition is just awareness. It’s looking around at what you’ve built so far and quietly deciding that there’s more left in you — and that it’s worth trying.

That decision — to want more — changes everything. It turns restlessness into curiosity. It turns boredom into a search. It’s what makes the unknown feel like an invitation instead of a threat. Every big change I’ve made started with that small internal shift. Not because I had a five-step plan. Just because I was done waiting for something to change on its own.

Ambition isn’t about knowing all the steps. It’s about deciding to move, even when you don’t. The decision itself is the act of ambition — the moment you say, “I’m going to do this,” with the quiet confidence that you’ll figure the rest out as you go. Until you decide, thinking is just a loop. You’re not really going anywhere. But once you decide, your mind starts working differently. It stops circling and starts building.

And maybe that’s the simplest way to measure ambition — by the scale of the things you’re willing to decide on. The bigger the decision you feel comfortable making without all the answers, the bigger your ambition really is.

And like anything else, ambition can be scaled. The more you act on it, the more natural it becomes to take on bigger and bigger things. It stops being about whether you’ll succeed or fail — and becomes more about what you're capable of holding. Ambition builds capacity.

Practicing the Muscle

I remember taking New Year's resolutions very seriously — not in a dramatic way, but in a personal, deliberate one. I wasn’t trying to overhaul my life. Just making small commitments that felt meaningful. One year it was to take one trip each month. Another year it was to run a few 5Ks. Once, it was as simple as avoiding certain foods or trying new ones. They were small, quiet resolutions, easy enough to forget — but I didn’t.

I kept doing them. And something strange happened: I started to believe myself. Each time I followed through on one of those promises, something shifted. The next year, the goals were a little bigger. The risks felt a little less intimidating. The voice saying "maybe you could do this" started to show up more often. What started as a few casual goals slowly became a mindset I couldn’t shake — one where staying still felt more dangerous than moving forward.

Eventually, I stopped waiting for a clean starting point or perfect conditions. I began to make decisions that felt much larger. Not because I had all the answers, but because I’d practiced trusting myself to figure things out along the way. That’s what ambition had become for me — not an impulse, but a muscle.

It wasn’t some grand plan. But looking back, that’s when I started taking ambition seriously. Not just as a vague sense of wanting more, but as a practice. A habit of deciding. And one day, without needing a special reason, I decided to do something I might’ve once thought was too far out of reach.

You can’t scale anything — not a career, not a relationship, not your sense of self — without first deciding that you want it to grow. That’s what ambition really is. It’s the start of momentum. It’s the beginning of a better story. That’s why this chapter comes first. Because everything else in this book — every decision, every bet, every risk — only matters if you’ve decided on that one simple thing first: You’re ready for more.

Ambition — wanting more — is truly the start of everything.