PJFP.com

Pursuit of Joy, Fulfillment, and Purpose

Tag: AI productivity gains

  • Dario Amodei on Policy for the AI Exponential: Anthropic’s Plan for AI Regulation, Job Displacement, Civil Liberties, and Democratic Leadership

    In June 2026, Anthropic CEO Dario Amodei published “Policy on the AI Exponential”, a wide-ranging essay arguing that the gap between how fast AI is advancing and how slowly policy moves has become dangerous, and that the window to close it is open right now. He opens with a memorable image from The Lord of the Rings: the Hobbits trying to rouse Treebeard, the ancient tree who takes a full day just to say hello, to defend his forest before it is cut down. That mismatch in speed, he writes, is exactly the relationship between AI and our political institutions. This post breaks the essay down in full and adds analysis of where the argument lands.

    TLDR

    Amodei argues that AI’s scaling laws point toward “powerful AI,” a country of geniuses in a datacenter, within a few years, while legislation still moves on a timescale of years. For most of the last few years, safety advocates including Anthropic pushed only for optionality-preserving moves like transparency rules, chip export controls, and labor data collection, because the risks were not yet concrete. He says that has changed: events like Claude Mythos Preview proved frontier models are now tools of national strategic consequence, and the time for binding regulation has arrived. The essay covers five policy areas. First, regulation and public safety, where he proposes an FAA-style regime of mandatory third-party testing of frontier models above a compute threshold across four risks (cybersecurity, biological weapons, loss of control, and automated R&D), with government power to block unsafe deployments. Second, macroeconomics and tax policy, where AI could deliver hypergrowth and severe, enduring job displacement at the same time, demanding measurement, pro-employment incentives, and possibly UBI or universal capital accounts. Third, accelerating AI’s positive impact, where the danger is regulators like the FDA being too slow rather than too lax, and biomedical approval needs reform. Fourth, the state and civil liberties, where AI could become the ultimate tool of autocracy through autonomous weapons and mass surveillance, requiring new accountability rules, a domestic ban on autonomous weapons, closing the data broker loophole, and public rights to AI advice. Fifth, securing leadership by democracies through a values-based global coalition that controls the AI supply chain, coordinates on risk, shares benefits, and rejects AI-powered repression. He closes by rejecting the idea that public concern about AI is a PR problem to be marketed away, calling it democratic accountability working as it should.

    Thoughts

    The most important move in this essay is structural, not technical. Amodei is explicitly retiring the “preserve optionality” posture that defined Anthropic’s policy work through 2025 and replacing it with a call for binding rules. For years the argument from safety-minded labs was that the risks were too speculative to legislate against without doing more harm than good, an idea he grounds in the Collingridge dilemma and the Hayekian point that regulators lack the information to make good calls. That was a defensible hedge. What is striking here is the claim that the hedge has expired. He is saying the evidence is now concrete enough that continued caution about regulating has flipped from prudent to negligent. Whether you trust the underlying capability claims or not, that is a genuine change in position from one of the field’s most influential voices, and it deserves to be read as such.

    The FAA analogy is doing enormous work, and it is worth poking at. Airplanes and drugs are mature technologies with stable physics and decades of incident data; the certification regime works because the failure modes are well understood. Frontier models are the opposite: the whole premise of the essay is that capabilities are changing faster than anyone can characterize them. Amodei half-acknowledges this when he warns that a fixed list of safety requirements tends to consume 95 percent of compliance effort on things that turn out not to matter while missing the real risks, a lesson he says Anthropic learned from its own Responsible Scaling Policy. So the proposal is really for an agency nimble enough to rewrite its own standards continuously, which is a much taller order than the FAA. The honest read is that he is proposing a regulator we do not yet know how to build, and betting that building it is still better than the alternative.

    The economics section is where Amodei is most careful, and it is the part most likely to be misread. He goes out of his way to say enduring job displacement is undesirable and that warning about it is not the same as wanting it, a distinction critics of AI leaders often collapse. His real claim is subtle: that AI might jam the economic policy dial on a “hypergrowth, hyper-inequality” setting that is hard to unstick, because AI substitutes for human cognition broadly and faster than past technologies, potentially overwhelming the usual escape hatches like comparative advantage and Jevons paradox. If he is right, the political fight of the next decade is not about growth, which AI supplies, but about distribution, which it does not. His mention of UBI, universal capital accounts, and higher capital gains taxes is notable coming from a frontier CEO, even hedged as it is.

    The civil liberties section is the one that should travel furthest beyond the AI-policy bubble, because it does not depend on accepting his most aggressive timelines. The data broker loophole, the idea that the government can simply buy the bulk data Americans hand to private companies and run mass analysis on it, is a problem that exists today; AI just raises the stakes by making that data vastly more revealing. Same with the proposal that anyone facing adverse government action should have access to AI at least as capable as what the government uses against them. These are concrete, near-term, and bipartisan in a way the abstract autonomy debates are not. The most candid line in the whole piece is his admission that AI cannot be safely entrusted to either governments or companies, an unusually direct acknowledgment that his own industry needs external checks, with Anthropic’s Long-Term Benefit Trust offered as one imperfect example rather than a solution.

    The geopolitics section is the most contested terrain. Framing AI as a nuclear-scale reset of the game board, with a virtual country of 100 million geniuses divisible across military strategy and weapons R&D, leads naturally to a democratic coalition that hoards chips and denies them to adversaries. That logic is internally consistent, but it sits in tension with the benefit-sharing and “eventually the whole world joins” language elsewhere in the same section. Export controls that lock down the supply chain are, by design, a tool of exclusion, and reconciling that with broad diffusion of AI’s benefits to developing countries is the circle the coalition idea has to square. Amodei is clearly aware of the tension and bets that making membership attractive resolves it. The closing image is the one to remember: Treebeard waking up, with the warning that the goal is to channel real public concern into constructive policy rather than let it curdle into formless anger.

    Key Takeaways

    • The core tension of the essay is a mismatch in speed: AI advances exponentially while legislation moves on a multi-year timescale, dramatized by the Treebeard and Hobbits image from The Lord of the Rings.
    • In only four years, AI models went from barely writing a coherent line of code to writing most of the code at major AI companies, with similar gains across biology, physics, math, finance, law, and translation.
    • Scaling laws now have over a decade of empirical support, and if they continue another year or two they likely produce “powerful AI,” a country of geniuses in a datacenter.
    • For the last few years, safety advocates including Anthropic focused on optionality-preserving policies: transparency legislation, chip export controls, and data collection on AI’s labor effects.
    • Amodei argues that posture is no longer enough. Claude Mythos Preview revealed that frontier models pose real cybersecurity risks to the financial sector, critical infrastructure, and national security, and proved AI is now a tool of strategic consequence.
    • He expects biological risks to follow cyber risks, with serious AI autonomy risks potentially not far behind.
    • The essay covers five policy areas: regulation and public safety, macroeconomics and tax policy, accelerating AI’s positive impact, the state and civil liberties, and securing leadership by democracies.
    • Alongside the essay, Anthropic released a legislative proposal on frontier model testing and a policy framework for job displacement, both with promised financial backing.
    • On regulation, Amodei invokes the Collingridge dilemma and Hayek’s information problem to explain why pre-writing AI law in 2023 to 2024 was risky, then argues the situation has now changed.
    • Anthropic’s 2025 answer was transparency, helping pass SB 53 in California, RAISE in New York, and SB 315 in Illinois, plus advocating a federal transparency standard.
    • He now calls for binding regulation modeled on the FAA, where frontier models must pass technical testing and can have release blocked or reversed if they fail high safety standards.
    • Models above a compute threshold should face mandatory third-party testing in four areas: cybersecurity, biological weapons, loss of control of AI systems, and automated R&D that accelerates the other three.
    • Government should be able to block or deter deployment of models judged to present unacceptable risk, scoped to those four risks with protections against political favoritism.
    • Evaluation could come from a government agency or from authorized and inspected private organizations under a “regulatory markets” approach.
    • AI companies should have strong security to protect model weights, conduct regular red teaming and penetration testing, report safety incidents promptly, and work with government against major threat actors.
    • He warns a time may come when the most powerful systems resemble weaponizable nuclear materials rather than airplanes, requiring more aggressive measures, but cautions against getting ahead of present dangers.
    • On economics, AI could deliver extremely rapid growth via accelerated science and operational efficiency, supercharged by AI building better AI.
    • The same properties make AI a broad substitute for human cognition that changes the economy faster than past technologies, risking large and potentially enduring labor market disruption.
    • The feared outcome is a “hypergrowth, hyper-inequality” setting that is hard to unstick, where the challenge shifts from incentivizing growth to sharing its benefits.
    • Amodei is emphatic that enduring job displacement is undesirable and dangerous, and that he warns about it to help society adapt, not as a prophet of doom.
    • Anthropic says it works with customers to find new revenue and use cases rather than only cost cutting, and explores interaction paradigms that keep humans active alongside AI.
    • He predicts AI will enable single individuals to build billion-dollar companies, noting teams of a few people already reach hundreds of millions in revenue, while admitting significant enduring job loss may be intrinsic to the technology.
    • Any response must address both economic provision and the human need for meaning, purpose, and agency, with the latter ultimately more important and beyond what policy can directly deliver.
    • Suggested economic interventions: better measurement and tracking (governments expanding statistics beyond Anthropic’s Economic Index), pro-employment incentives, and long-term macroeconomic support.
    • Pro-employment ideas include wage insurance, retention tax incentives, workforce training grants, and employer-employee matching infrastructure.
    • If displacement is large and permanent, mechanisms like universal basic income or universal capital accounts, financed through company taxes or higher capital gains taxes, may be necessary.
    • He frames datacenter and energy-price backlash as largely a symbol of broader economic anxiety, and says AI companies should pay to absorb rate increases, a pledge Anthropic has already made.
    • For technologies accelerated by AI, the bigger risk is regulators like the FDA being too slow, not too lax, because AI may make downstream tech safer in ways that violate skeptical regulatory assumptions.
    • Biomedicine is the illustrative case: AI could flood the drug pipeline, raise effect sizes, treat previously untreatable diseases, and create whole new therapy categories, while the current FDA and EMA pipeline takes 7 to 8 years.
    • Agencies should pre-approve standards for AI methods like PD/PK modeling, toxicology prediction, dose selection, biomarker validation, synthetic control arms, and surrogate endpoints, plus more flexible accelerated-approval mechanisms.
    • On civil liberties, powerful AI in the wrong hands could be the ultimate tool of autocracy, and existing constitutional protections are not fully equipped to counter a surprise seizure of power.
    • Threats named include fully automated drone armies that obey unlawful orders and surveillance AI that infers the innermost details of every citizen’s life from widely available data.
    • Civil liberties proposals: accountability rules and an “off switch” for autonomous weapons, a domestic ban on fully autonomous weapons including in law enforcement, closing the data broker loophole, and public rights to AI advice during adverse government action.
    • Amodei warns companies as well as governments can seize quasi-state power, citing the Gilded Age and the East India Company, and says AI cannot be safely entrusted to either alone.
    • He offers Anthropic’s Long-Term Benefit Trust as one separation-of-power structure and urges the industry to explore mechanisms that go further.
    • On geopolitics, he argues AI resets the geopolitical game board like nuclear weapons, becoming the dominant source of military and economic power for any nation that holds it.
    • A nation with powerful AI versus one without it, or even one three years behind, could resemble WWII Marines facing medieval swordsmen.
    • He calls for a democratic coalition that shares chips and semiconductor manufacturing equipment internally while denying them to adversaries, citing MATCH and OVERWATCH as good first steps.
    • The coalition should coordinate risk policy, share benefits including harmonized medical approvals, provide mutual AI defense, reject AI-powered repression, and cooperate on macroeconomic stabilization.
    • He rejects the idea that AI’s image is a PR problem, arguing public concern reflects real risks and is democratic accountability working as it should, with the task being to channel it into constructive solutions.

    Detailed Summary

    The speed mismatch between AI and policy

    Amodei frames the entire essay around a single problem: AI advances at a lightning pace while policy, especially legislation, moves very slowly, often for good reasons since governments wield grave powers that should not be used hastily. He illustrates this with Treebeard, the sentient tree from The Lord of the Rings who takes a full day to say hello, as a stand-in for political institutions trying to respond to a technology that can go from amusing toy to a country of geniuses in the time it takes Congress to act. He recounts the dilemma responsible actors have faced: they could see where the exponential was headed, but to observers looking only at present capabilities, AI looked as mundane as the latest consumer app or cryptocurrency, making a laissez-faire attitude hard to argue against. The absence of AI’s radical effects, and uncertainty about their shape, made it genuinely difficult to design good policy even where the will existed.

    That uncertainty, he says, is why safety advocates limited themselves to optionality-preserving measures like transparency rules, export controls, and labor data collection. But over the last few months the evidence of AI’s power and risk has become undeniable, with Claude Mythos Preview as the emblematic example: it scrambled the global cybersecurity landscape and proved AI models are now tools of global and national strategic consequence. He expects biological and autonomy risks to follow, and argues the world must now activate its slow, rickety policy apparatus to handle risks that will compound quickly. He worries current early actions are at least a year out of step with AI’s progress, and presents the essay as an attempt to close that gap across five policy areas, focused on US policy but relevant worldwide.

    Regulation and public safety: an FAA for frontier models

    Amodei opens by acknowledging the real costs of regulation: it can reduce a product’s benefits, disincentivize innovation, and suffer from the Hayekian problem that regulators lack the information for good tradeoffs, plus the Collingridge dilemma that a technology’s impacts are hard to anticipate until it is too late to manage them. In 2023 to 2024 these dynamics argued against pre-writing AI law, since the exact form of biological or autonomy risk, how to test for it, and how it would play out were all unclear, creating a high risk of low-value compliance requirements that miss the real dangers. Anthropic’s answer was transparency: requiring developers to disclose safety procedures, tests, and critical incidents, which is why it supported SB 53 in California, RAISE in New York, and SB 315 in Illinois in early 2026.

    Now, he argues, the risks are clearly here and it is time for binding regulation. His analogy is to cars, airplanes, and drugs: powerful technologies essential to the economy but capable of killing many people if designed or operated poorly. He models AI regulation on the FAA, with frontier models required to pass testing and auditing and with release blocked or reversed if they fail high safety standards. His concrete proposal: mandatory third-party testing for models above a compute threshold across cybersecurity, biological weapons, loss of control, and accelerating automated R&D; government power to block deployment of unacceptably risky models, scoped narrowly with anti-favoritism protections; evaluation by either a government agency or authorized private organizations in a regulatory-markets model; strong weight security, red teaming, and penetration testing at AI companies; and prompt reporting of safety incidents. He notes a future may arrive when systems resemble weaponizable nuclear materials and demand harsher measures, but warns against designing for dangers that have not yet emerged.

    Macroeconomics and tax policy: growth and displacement together

    Here Amodei challenges the standard premise that growth is fragile and must be traded off against the drag of taxes or deficits to reduce inequality. Powerful AI, he suggests, may scramble that assumption by producing extremely rapid growth through accelerated science and efficiency, supercharged by AI building better AI, while simultaneously acting as a broad substitute for human cognition that reshapes the economy faster than any prior technology. The result could be a world stuck on a hypergrowth, hyper-inequality setting that is hard to unstick, where the central challenge is no longer incentivizing growth but sharing its benefits. He is careful to make two points clearly: first, enduring job displacement is undesirable and dangerous and should be minimized, and his warnings are meant to help society adapt, not to play prophet of doom; second, any response must address both economic provision and the deeper human need for meaning, purpose, and agency, which matters more and which policy cannot directly supply.

    His policy menu starts with measurement and tracking, arguing good policy is impossible without accurate data, and that governments could expand economic statistics well beyond Anthropic’s Economic Index. Next come pro-employment incentives such as wage insurance, retention tax incentives, workforce training grants, and employer-employee matching, costs he says society should readily accept since they are likely offset by AI productivity gains. If displacement proves large and permanent, he says long-term income support like universal basic income or universal capital accounts may be needed, financed through taxes on relevant companies or higher capital gains taxes. He closes the section by reframing datacenter and energy-price backlash as mostly a symbol of broader economic anxiety, while saying AI companies should absorb rate increases, as Anthropic has pledged.

    Accelerating AI’s positive impact: the slow-regulator problem

    For technologies accelerated by AI, rather than AI itself, Amodei flips his concern: the bigger danger is regulatory systems designed for a slower pace failing to handle the deluge of new products, and AI making downstream technologies safer in ways that violate the skeptical assumptions baked into agencies like the FDA. He focuses on biomedicine as the area likely to produce AI’s biggest humanitarian benefits and where regulation is especially complex. AI could greatly increase the rate of new drug candidates, improve their effect sizes and safety profiles, treat previously untreatable diseases, and create entirely new therapy categories the way antibodies, peptides, and cell therapies did.

    The current pipeline at the FDA and EMA takes 7 to 8 years, built on the pessimistic assumption that drug candidates usually fail and often carry safety problems even when they work. Without reform, AI will jam or overload that system. Amodei proposes that agencies develop standards now for accepting AI simulation and analysis, so they can be adopted quickly once proven rather than after years of unnecessary testing. Specific candidates include AI-based PD/PK modeling, toxicology prediction to reduce animal testing, more accurate dose selection, biomarker validation from large datasets, synthetic control arms, and surrogate endpoints (especially for aging and neurodegeneration). He urges more flexible accelerated-approval mechanisms generally, and notes biomedical acceleration may also reduce AI’s risks by aiding biodefense and improving mental health.

    The state and civil liberties: guarding against AI-driven tyranny

    Amodei frames the perennial balance between state power and individual liberty, enforced through machinery like the First, Fourth, and Fifth Amendments, the Posse Comitatus Act, and FISA, and argues AI threatens to upset that balance while raising its stakes. Powerful AI in the wrong hands could be the ultimate tool of autocracy, because the enormous returns to intelligence combined with AI’s pace create a perfect storm for a surprise seizure of power. The danger could take many forms but shares one feature: AI conferring sudden power while routing around democratic oversight. He cites a fully automated drone army that could obey unlawful orders, where trained humans might object, and a surveillance AI that analyzes widely available information at massive scale to infer the innermost details of every citizen’s life, an ability current civil liberties law never contemplated.

    His proposals: create accountability rules for autonomous weapons so they respond to court orders, legislation, and human overseers rather than blindly following orders, possibly with a judicial finger on an off switch; ban domestic use of fully autonomous weapons, including in law enforcement, while allowing them against foreign adversaries; close the bulk-collection and data-broker loophole that lets the government buy and analyze data Americans share with private companies; and guarantee public rights to AI advice at least as capable as what the government uses during adverse action, as an extension of the Administrative Procedure Act, due process, or the Sixth Amendment. He closes by warning that companies, not just governments, can capture the state, citing the Gilded Age and East India Company, and argues AI cannot be safely entrusted to either alone. Anthropic’s Long-Term Benefit Trust is offered as one accountability structure, with a call for the industry to go further.

    Securing leadership by democracies: a values-based coalition

    Amodei rejects treating AI as a mere instrument of trade policy to diffuse a tech stack worldwide. He believes AI resets the entire geopolitical game board like nuclear weapons, potentially even more so, becoming the dominant source of military and economic power for whoever holds it. In a virtual country of 100 million geniuses, millions could be assigned to military strategy, drone manufacture, weapons R&D, intelligence, and scientific advancement at once, so a nation with powerful AI facing one without it, or even three years behind, could be like WWII Marines against medieval swordsmen. Because powerful AI also enables deeper autocratic repression, it matters enormously that the world’s strongest nations are democracies.

    His answer is a global coalition built on shared democratic values that draws in the rest of the world by making membership increasingly attractive and exclusion increasingly costly. Operating principles include managing the AI supply chain by sharing chips and semiconductor manufacturing equipment within the coalition while denying them to adversaries, expanding and tightening export controls (he cites MATCH and OVERWATCH as good first steps); coordinating on biological, cyber, and autonomy risk to make compliance compatible and effective; sharing AI’s benefits including harmonized medical approvals; mutual defense through collective AI cyberdefense, drones, manufacturing, compute, and intelligence; rejection of AI-powered repression; and macroeconomic cooperation against contagious employment crises. The coalition would respect each nation’s sovereignty, start with aligned democracies, and grow iteratively, ideally toward the whole world, but at minimum positioning democracies to contain and outcompete repressive regimes.

    A window of opportunity

    Amodei closes on cautious optimism. The same exponential that strains policymaking has created a unique opening: clear evidence of AI’s risks, an early taste of its value and disruption, and public backlash against unregulated approaches have left policymakers unusually open to forward-looking action. Treebeard and his forest are waking up. He firmly rejects the industry-circle view that this is a PR problem solved by better marketing, arguing people are worried because the risks are real, and that public concern in response to transparency is democratic accountability working as it should. The key challenge is focusing that concern into constructive solutions rather than letting it descend into formless anger and violence. He is optimistic because issues from job displacement to model testing to export controls have common-sense appeal across the political spectrum, and a broad nonpartisan coalition could adopt sane, forward-looking policy faster than usual.

    Notable Quotes

    “in only four years, AI models have gone from barely being able to write a coherent line of code to writing most of the code at major AI companies.”

    Dario Amodei, on the pace of the AI exponential

    “in the several years that it can take Congress to act, AI can go from an amusing toy to the full country of geniuses.”

    Dario Amodei, on the mismatch between AI’s speed and the speed of legislation

    “However, now the risks are clearly here. It is time to go beyond transparency to more serious and binding regulation of AI.”

    Dario Amodei, marking the shift from transparency to binding rules

    “enduring job displacement is undesirable and dangerous, and we should do everything we can to minimize or prevent it, not to bring it about.”

    Dario Amodei, clarifying his stance on AI and jobs

    “The key challenge in such a world won’t be incentivizing growth, but finding a way for everyone to share in the benefits.”

    Dario Amodei, on a hypergrowth, hyper-inequality economy

    “Powerful AI in the wrong hands could be the ultimate tool of autocracy, and our existing legal and constitutional protections are not fully equipped to counter this threat.”

    Dario Amodei, on AI and civil liberties

    “A nation that possesses powerful AI facing one without it … could be the equivalent of an army of World War II Marines facing an army of medieval swordsmen.”

    Dario Amodei, on AI as the dominant source of geopolitical power

    “People are worried about AI because they correctly perceive that its risks are real, not because AI CEOs have been insufficiently Panglossian.”

    Dario Amodei, rejecting the idea that AI has a PR problem

    “Treebeard and his forest are waking up.”

    Dario Amodei, on policymakers’ new openness to acting on AI

    “Policy on the AI Exponential” is a dense, structured argument from one of the most consequential figures in the field, and it rewards a full read in the original. The summary and analysis above are a guide, not a substitute. You can read the full essay here.

    Related Reading

  • Waste Tokens to Save Time: Naval, Guillermo Rauch, Blake Scholl, and Max Hodak on AI Software Factories, 1000x Engineers, and Whether Pure Software Is Dead

    Naval Ravikant gathers three frontier founders, Guillermo Rauch of Vercel, Blake Scholl of Boom Supersonic, and Max Hodak of Science, for a freewheeling conversation about how AI coding tools are reshaping what an engineer is, what software is worth, and where the moat goes when models speak English. The headline idea comes from Naval himself: waste tokens, save time. Stop measuring AI by tokens consumed or lines of code generated and start measuring it by the final output and the time you got back. The full conversation is on the Naval Podcast YouTube channel. This is part one of the discussion. Part two, on vibe coding hardware, follows the same group into jet engines, semiconductors, and biotech. You can also watch and read the full episode here.

    TLDW

    The job of an engineer is shifting from shipping output to building the factory that ships the output, which means 10x engineers were never really 10x, they were always 100x or 1000x in idea domains, and AI leverage is making that obvious. Models now reflect back the judgment of the user, so a senior architect extracts dramatically more value than a junior, although the junior also writes code they could never have written alone. The frontier models have quietly graduated from junior coders to principal engineers, returning with intuitive plans and real tradeoffs (sometimes with hilariously bad time estimates) rather than just running away with the prompt. Naval has stopped learning prompt tricks, scaffolding tools, and Claude plan-mode rituals entirely. Instead he throws Codex, Claude, and Gemini at the same problem in parallel and brute forces his way through, because tokens are still cheaper than a human and the models keep getting better faster than tricks can. That leads to the bigger question on the table: is pure software still investable, or is it now just a free byproduct of hardware, models, and taste? The group lands on the block economy thesis (a tip of the hat to Mitchell Hashimoto): agents do not want to reinvent Postgres or BMQ on the fly, they want to grab the right reusable building block, so infrastructure software actually gets more valuable, not less. Max Hodak closes the loop with a personal data point: he has not written a line of code in years and has built more software since December than ever before, all through agents, because just understanding APIs, data flow, and performance is what actually moves the work forward.

    Thoughts

    The “waste tokens, save time” line is the most important rhetorical move in this conversation, and it deserves to be unpacked beyond the soundbite. Naval is implicitly arguing that the entire token-economics debate (input cost, output cost, leaderboards, model arbitrage) is a category error in the same way that lines-of-code was a category error in the nineties. The thing being purchased is not tokens. It is a finished result delivered with less of your finite attention spent. If three parallel runs of Codex, Claude, and Gemini cost you a few dollars and one of them lands the answer in twenty minutes instead of you sweating the problem for two hours, the unit economics are not even close. The only people who care about the token bill are people who have not internalized that human time is the actually scarce resource. Once you do internalize it, the question is no longer “how do I prompt this more efficiently,” it is “how do I get out of my own way.”

    The 100x and 1000x engineer point is the one most likely to enrage commenters, and it is also the one most worth taking seriously. Naval is right that the egalitarian flinch in software circles always sat awkwardly next to the empirical fact that one Carmack, one Brendan Eich, or one Satoshi creates more durable value than every mid-tier engineer on earth combined. What AI does is collapse the bottom of that distribution. The marginal junior engineer at a typical company is now competing with a model that costs a few dollars an hour and never sleeps. The remaining premium for human engineers is taste, judgment, and the rare ability to pick the right thing to build at all, which Naval correctly flags as the multiplier that dwarfs raw coding speed. “Just one who had a better judgment on what to work on in the first place” is the most underrated line in the whole episode.

    Guillermo Rauch’s observation that the models have graduated from running away with your prompt to returning with three routes and a tradeoff matrix is the technical update most people have not actually felt yet. There was a real, qualitative shift when the model started saying “we don’t put high-cardinality telemetry into Postgres, you probably want ClickHouse or Athena.” That is not autocomplete. That is a peer. And the funny corollary, that the same model will then confidently tell you the work will take three weeks when it will take three hours, is not a knock on the model. It is a reminder that calibration is a separate skill from competence, and humans get this wrong constantly too. The right posture is to treat the model the way a good engineering manager treats a strong but cocky senior: take the architecture suggestions seriously, throw out the estimates.

    The block-economy thread, riffing on Mitchell Hashimoto, is where this conversation quietly answers Naval’s “is pure software dead” question. Agents are insatiable consumers of reusable building blocks because reinventing infrastructure on every run is wasteful, brittle, and incompatible with the rest of the world. If your service is the canonical primitive an agent reaches for (the queue, the database, the auth layer, the deploy target), you are not commoditized by AI, you are amplified by it. Pure software is not dead. Pure software with no distribution, no defensibility, and no integration into the agent toolchain is dead. That is a much less catchy headline, but it is the real one. The takeaway for founders is not to abandon software, it is to ask whether your software is something an agent will reach for ten thousand times a day or something a human had to be talked into using once.

    Max Hodak’s confession (no code written in years, more shipped software in the last six months than ever before) is the empirical proof that this is not just theory. The skill that ports forward is not syntax. It is the engineering leader’s instinct for what an API is, how data flows, where performance matters, and what level of expectation to set. Guillermo’s framing of “vibe coding through people on Slack” as the original form of vibe coding is genuinely insightful. A good engineering manager has always been transmitting intent to other minds and letting them run. Doing it with agents is the same skill, just with a faster, cheaper, more literal counterparty. The engineers who will struggle in this transition are the ones whose identity was tied to writing the code themselves. The ones who will thrive are the ones who already thought of themselves as taste, judgment, and intent, with code as an implementation detail.

    Key Takeaways

    • The engineer’s job has shifted from shipping output B to building the factory that produces outputs B through Z. You are now judged on the multiplicative system you create, not the single artifact you deliver.
    • 10x engineers were always a misnomer. In idea-domains and digital domains, the real distribution has always been 100x or 1000x. AI just made that obvious enough that arguing about it is no longer fashionable.
    • Token consumption leaderboards are the new lines-of-code metric: a vanity number that measures activity, not value. Tokens are an input, your time is the constraint.
    • Naval’s core rule: waste tokens, save time. Tokens are still vastly cheaper than human hours, no matter how the pricing scares you.
    • Models tend to be about as good as you are in a given domain. The feedback you give them, the corrections, the redirections, sporadically but powerfully shapes the quality of the output.
    • The quality of your reprompting matters enormously today, but will probably matter less over time as models get smarter and need less hand-holding.
    • Naval has refused to learn prompt scaffolding, plan-mode tricks, or named prompt frameworks. His bet is that the models will figure out how to use him faster than he can figure out how to use them.
    • His preferred technique: throw Codex, Claude, and Gemini at the same problem in parallel and brute force the answer. Time is the cost center, not API spend.
    • Lower quality first-draft code is not a blocker. When it is time to ship, throw more tokens at it for a hardening pass. Quality compounds across model generations.
    • Verifiable domains (problems with a clear right answer) are the ones the models will fully solve. Cutting-edge creativity work, the Terence Tao tier, still needs careful human collaboration.
    • Models have qualitatively shifted from “next-token autocomplete that runs away with your prompt” to “intuitive planning mode” where they return with multiple routes and explicit tradeoffs.
    • This is why people on social media say models are now PhD-level. It is not the raw output, it is the back-and-forth posture.
    • Models will confidently make terrible time estimates (“this is a three week project”). Treat them like a strong but miscalibrated senior engineer: trust the architecture, ignore the schedule.
    • Architect-level engineers are extracting much more value per session than junior engineers, but juniors are still leveling up because they can now write code far above their unaided ability.
    • The next career step for a junior engineer is moving from implementing features to picking technologies. Postgres vs ClickHouse, ZMQ vs other queues. The model can suggest, but a human still has to decide.
    • Taste and judgment remain the residual human advantage. Models will give you good tradeoffs if you ask, but knowing which tradeoff to take is still on you.
    • Concrete example: a recent model pushed back when asked to store high-cardinality telemetry in Postgres and recommended ClickHouse or Athena instead. Unprompted architectural judgment.
    • Humans are still completing the model for tasks like fetching API keys, moving capital, or performing real-world actions. That gap is temporary.
    • Every SaaS and hosting company will soon expose a CLI or API surface that agents can drive directly. Anything Unix-shaped and text-based, agents can already hack into a usable API themselves.
    • The missing piece for full autonomy is payments. Crypto, Bitcoin, or any programmable money lets the agent buy what it needs without a human in the loop.
    • The open question Naval poses: is pure software dead? We used to learn code to talk to machines. Now machines speak fuzzy, sloppy English back to us.
    • For hardware founders, AI is a massive boon. Software, which was always hard to hire artists for (per Patrick Collison’s “software is art” framing), is suddenly fast and cheap to produce alongside the hardware.
    • Model training, post-training, and fine-tuning may be the new “real software engineering” for those who want to work at the model layer.
    • Mitchell Hashimoto’s “block economy” thesis: agents need powerful, reusable, well-known building blocks. They should not reinvent message queues or databases every run.
    • Reinventing primitives is bad civic engineering. The value of “we both depend on Postgres 13.2” is interoperability with the rest of society and toolchain.
    • Infrastructure software and reusable libraries are getting more valuable, not less, in the agentic era. Vercel’s bet is on being the layer agents reach for.
    • Useful metaphor: building blocks are like a token cache. Why churn through a trillion tokens to reproduce code that already exists when you can fork from a known starting point?
    • Max Hodak has not written a line of code in years but has shipped a huge volume of personal software since December, all through agents. Projects he had fantasized about for years are now actually running.
    • What still matters from a real software background: understanding what an API is, how data flows, performance expectations, and how to set the right level of demand on an operation.
    • A proficient engineering leader has always been “vibe coding through people” on Slack and in one-on-ones, transmitting intent and letting others execute. Doing it with agents is the same skill, faster and cheaper.
    • Naval personally went from twenty years of not coding to coding constantly through agents, leaning on first-principles software engineering and algorithms knowledge.
    • The friction that historically killed personal coding projects (latest framework, infra plumbing, deploy setup) is now mostly handled by the agent. Vercel makes it easier, agents make it trivial.
    • The single biggest change Max highlights: you do not get stuck anymore. The indefinite debugging spiral on some narrow obscure bug is largely gone.
    • The old mantra that learning to program means accepting intrinsic frustration (“nope, that’s part of the deal”) is no longer true. The frustration was incidental, not essential.
    • The frontier founder pattern on display in this episode: all three guests build their own factories (Vercel’s AI cloud, Boom’s supersonic jets and engines, Science’s biohybrid brain interface) rather than composing from off-the-shelf parts.

    Detailed Summary

    The Software Factory and the Hundredfold Engineer

    Guillermo Rauch opens the substantive portion of the conversation with the framing he has been pushing publicly: the role of the engineer is moving from “ship output B” to “build the factory that ships outputs B through Z.” That reframes engineering judgment. You are no longer evaluated on the single deliverable, you are evaluated on the multiplicative system you put in place. Naval picks up the thread and points out that this also retires an old debate. Engineers used to argue about whether 10x engineers existed, with the egalitarian camp insisting that talent differences were marginal. The truth, Naval says, was always more extreme. In idea-domains, virtual domains, and intellectual domains, the distribution has always been 100x or 1000x, not 10x. Brendan Eich, Carmack, Satoshi, the canonical names, were thousandx programmers. AI has made the underlying distribution legible. And the multiplier on top of all of that is judgment: picking the right thing to work on in the first place is an infinity multiplier compared to picking the wrong thing, regardless of raw skill.

    Token Leaderboards Are the New Lines of Code

    Guillermo flags the current cultural confusion: people see their AI bills, see the token counts, and assume they should be optimizing for tokens-per-engineer or similar metrics. Max Hodak’s response cuts through it. Token consumption, like lines of code before it, is not a meaningful productivity metric. It is an activity metric, and activity metrics always mislead. Max adds his own field observation: the models tend to be roughly as good as you are in a given domain. A senior developer extracts genuinely powerful output, a junior gets junior-quality output back, because the feedback loop (the corrections, the redirections, the architectural pushback) is what shapes quality. The sporadic but high-leverage moments where the user redirects the model are doing more work than the prompt itself.

    Naval’s Brute Force Doctrine: Waste Tokens, Save Time

    Naval lays out his personal posture, which has become the title of the conversation. He has deliberately ignored all the prompting tricks, scaffolding tools, named prompt frameworks (“use Ralph Wigum, use OpenClaude, use Hermes, use plan mode”), on the bet that the models will figure out how to use him faster than he can figure out how to use them. He is ham-fisted with the models, gets frustrated, types less and less, and just brute forces his way through by running Codex, Claude, and Gemini at the same problem simultaneously. The justification is economic. No matter how expensive the models seem, they are still vastly cheaper than a human hour. Do not measure tokens as inputs or outputs. Measure your time and the final output. Even when the first-draft code is low quality, that is not a blocker. When the moment comes to ship, throw more tokens at it. The models will rewrite it, harden it, and they get better every generation. Naval explicitly excepts cutting-edge creative work (the Terence Tao tier of unsolved problems) where you still need to collaborate carefully and closely. Everywhere else, brute force is the dominant strategy.

    From Junior Coder to Principal Engineer

    Guillermo identifies a qualitative shift that has happened recently. Models used to do the classic next-token thing: take your prompt and run away with it in a direction you may not have wanted. Now they enter an intuitive planning posture without being told to plan. They come back and say “what you are asking has these three routes, here are the tradeoffs.” That, Guillermo argues, is the moment the model stopped being a junior engineer and became a principal engineer. The funny side effect is that they will then return preposterous time estimates (“this will take three weeks”) with full confidence. The conclusion is to treat the model as a peer for architecture and a baby for scheduling. Returning to the Max-vs-junior question, Guillermo argues juniors clearly do level up because they write code well above their solo ability, but architects extract maybe 10x while juniors extract more like 2x. The juice scales with the user’s existing taste.

    Taste, Judgment, and Architectural Decisions

    Max names the residual human contribution: taste and judgment. Picking between Postgres and ClickHouse for high-cardinality telemetry data, picking between ZMQ and another queueing system. The models can recommend, but a human still has to call it. Guillermo offers a recent concrete example where a model pushed back unprompted: when asked to put high-cardinality telemetry into Postgres, the model responded “we don’t put that kind of data into Postgres, you should consider ClickHouse or Athena.” That is the new normal. The peer-level architectural pushback is happening unsolicited, which is genuinely impressive and a real shift from the deferential autocomplete of two years ago.

    When the Human Becomes the Tool

    Guillermo raises the inversion question: at what point does the model stop being the assistant and the human start being the assistant who fetches API keys, moves capital, and performs real-world actions on the model’s behalf? Naval treats it as a temporary aberration. Every serious SaaS and hosting provider will soon expose a CLI or API surface that agents can drive directly. Even when they do not, anything Unix-shaped and text-based can be hacked into an agent-usable interface by the agent itself. The missing piece is payments. Once you insert programmable money (Naval mentions Bitcoin and crypto tokens), the agent can buy what it needs and the human is no longer the bottleneck.

    Is Pure Software Dead?

    Naval poses the biggest strategic question of the episode. If models now speak fuzzy, sloppy English the same way humans do, and the historical reason we learned to code was to talk to machines that did not understand English, is pure software still a viable thing to build a company around? His own framing of the answer: hardware founders win, because the historically hard problem of hiring software artists (per Patrick Collison’s “software is art” line) is now mostly solved by AI. Model builders win, because training, post-training, and fine-tuning may be the new “real software engineering.” But what about classic pure software companies? Naval lets the question hang, and Guillermo picks up the answer through a different door.

    The Block Economy and the Future of Infrastructure Software

    Guillermo cites Mitchell Hashimoto’s recent piece on the block economy (or “building block economy”). The argument: the most valuable thing for agents to have access to is powerful, reusable building blocks. You do not want your agent reinventing a queue system every time it needs to send an email. You want it to grab the right-sized block (BMQ, ClickHouse, whatever) and move on. Reinventing primitives is also a civic problem. The world only works because we all depend on the same Postgres 13.2, the same protocols, the same standard infrastructure. If every agent went off and invented its own bespoke universe, you would lose interoperability. So infrastructure software (which is, by self-admitted bias, what Vercel builds) becomes more valuable in the agentic era, not less. Guillermo extends the metaphor: reusable building blocks are like a token cache. Why burn a trillion tokens reproducing what already exists when the agent can fork from a known starting point? The block economy is the answer to “is pure software dead.” Pure software that becomes the canonical primitive an agent reaches for is more valuable than ever.

    Max Hodak’s Personal Proof: Years Without Code, Tons of Software Shipped

    Max grounds the discussion in his own experience. He learned to program young, got sucked into it in his teens and 20s, knew programming languages deeply. He has not written a line of code in quite a while. And yet since December he has built a huge amount of personal software, including projects he had fantasized about for years and now actually uses every day. He did not write any of it. He cannot imagine going back to writing code by hand. The skill that ports forward is not syntax, it is the understanding of how APIs work, how data flows, what level of performance to expect, and how to orient the model around the right expectations for an operation. Guillermo extends this with the most quotable framing of the episode: a proficient engineering leader has always been “vibe coding through people on Slack and in one-on-ones,” transmitting intent and letting others execute. Agents are the same modality with a faster, cheaper, more literal counterparty.

    Naval’s Return to Coding After Twenty Years

    Naval offers his own parallel. He went from not having written code in twenty years to coding constantly through agents. What carried him back in was first-principles knowledge of software engineering and algorithms, which gets you further than you would think. The reason he had stopped coding in the first place was not lack of ability, it was the friction of keeping up with the latest language, the latest architecture, and the constant infrastructure plumbing required to ship anything. Vercel made it easier. Agents made it trivial. Max closes with the most concrete benefit of all: you do not get stuck anymore. The indefinite debugging spiral on some obscure narrow problem, the thing that historically ate weekends and broke spirits, is largely gone. The old mantra that programming is intrinsically frustrating and that frustration is “part of the deal” turned out to be wrong. The frustration was incidental, not essential.

    Notable Quotes

    “The way that I’m judging you as an engineer is, are you producing the factory that will produce multiplicative outputs B through Z?”

    Guillermo Rauch, reframing what an engineer is actually being measured on in the AI era.

    “When you’re operating in idea domains, intellectual domains, virtual digital domains, it’s not even 10x, it’s 100x or 1000x. It always has been.”

    Naval Ravikant, on why the old 10x engineer debate was always under-stating the real distribution.

    “If you choose the right thing to work on versus the wrong thing to work on, that’s an infinity difference. It could just be one who had a better judgment on what to work on in the first place.”

    Naval Ravikant, on judgment as the multiplier that dwarfs raw skill.

    “I’ll throw Codex, Claude, and Gemini at the same problem over and over and just waste tokens to save time. No matter how expensive these models might seem, they’re still way cheaper than a human.”

    Naval Ravikant, on his brute-force multi-model coding workflow.

    “Just waste tokens, save time. Don’t look at the tokens either as inputs or outputs. Just look at your time and look at the final output.”

    Naval Ravikant, delivering the title thesis of the episode.

    “Clearly the models at some point graduated. They used to be junior engineers, now they’re principal engineers, because they come back to you with a set of tradeoffs.”

    Guillermo Rauch, on the qualitative shift in how current frontier models respond to prompts.

    “Bro, we don’t put that kind of data into Postgres, you should consider ClickHouse or Athena or whatever. That’s happened to me a lot, which is really impressive.”

    Guillermo Rauch, recounting unprompted architectural pushback from a recent model.

    “It’s like saying speaking English. We had to learn code to communicate with the models, now the models speak English. So where’s the moat?”

    Naval Ravikant, raising the central strategic question about the future of pure software.

    “I haven’t written a single line of code in quite a while. Since December, I’ve built a huge amount of software that I now use every day, projects I’ve fantasized about for years.”

    Max Hodak, on what becomes possible when you stop writing code and start directing agents.

    “A proficient engineering leader has been quote unquote vibe coding through people on Slack or one-on-ones, because you’re transmitting your will, your intent, your experience, and you’re letting others run with it. Now we do the same with agents.”

    Guillermo Rauch, reframing leadership itself as the original form of vibe coding.

    Watch the full conversation on the Naval Podcast here.

    Related Reading

    • Full episode: The AI Industrial Revolution, the complete hour-long conversation this clip is drawn from, covering software factories, hardware, regulation, healthcare economics, autonomous companies, and creativity.
    • Part two: Vibe Coding Hardware, the continuation of this conversation, where the same founders move from pure software into AI-designed jet engines, vertical integration, China’s open-source bet, and why humans become verifiers.
    • Naval Ravikant’s official site, the canonical home for Naval’s essays, podcast, and longer-form thinking on technology, judgment, and leverage.
    • Vercel, Guillermo Rauch’s company, building the AI-native cloud and frontend infrastructure that this conversation references as a canonical agent building block.
    • Boom Supersonic, Blake Scholl’s company building supersonic civilian aircraft and their own jet engines, the hardware example of a founder building the whole factory.
    • Science Corporation, Max Hodak’s brain-computer interface company developing the biohybrid neural implant referenced in the intro.
    • Mitchell Hashimoto’s writing, source of the “block economy” framing for why reusable infrastructure building blocks become more valuable, not less, in the agentic era.