PJFP.com

Pursuit of Joy, Fulfillment, and Purpose

Tag: Naval Ravikant

  • The AI Industrial Revolution: Naval, Guillermo Rauch, Blake Scholl, and Max Hodak on Software Factories, Vibe Coding Hardware, AI Regulation, Healthcare Economics, and What Humans Can Uniquely Do

    This is the full episode of Naval Ravikant’s conversation with three frontier founders: Guillermo Rauch of Vercel, Blake Scholl of Boom Supersonic, and Max Hodak of Science. The premise is that all three are building their own factories rather than assembling off-the-shelf parts, so the interesting question is not what they are building but what they are learning about how to build in the age of AI. Over roughly an hour the discussion moves from software factories and the thousand-x engineer into hardware, regulation, healthcare economics, autonomous companies, and a long closing argument about what humans can still uniquely do. Watch the full conversation on the Naval Podcast YouTube channel. We previously published two segments of this same discussion: part one, Waste Tokens to Save Time, on software factories and whether pure software is dead, and part two, Vibe Coding Hardware, on jet engines, vertical integration, and China’s open-source bet. This post covers the entire episode end to end.

    TLDW

    Four builders argue that AI has turned the engineer’s job from shipping output into building the factory that produces output, which is why token leaderboards are the new vanity metric and why you should waste tokens to save time. Guillermo Rauch frames the thousand-x engineer and the building-block economy, and asks whether pure software is dead now that models speak English. Blake Scholl shows how Boom turned hardware engineering into software, letting two engineers design an entire jet engine and collapsing months of regulatory compliance documentation into minutes. Max Hodak makes the case for extreme vertical integration, a captive MEMS foundry, and a sober counter to Silicon Valley deregulation triumphalism: the bottleneck is the voters and the regulator’s asymmetric incentives, not just bad rules. The group works through healthcare as a fixed-bucket non-market, China’s cost-reduction strategy and its approved implantable brain interface, autonomous software that runs site reliability and security research with thousands of concurrent agents, a company-wide hackathon where the receptionist shipped a real automation, and a long debate on creativity, out-of-distribution surprise, intent, attribution, and the definition of art. The throughline: humans become verifiers, value moves to creativity, taste, and agency, and the single best move is to get extremely good with the tools, because it is people with AI versus people without AI.

    Thoughts

    The strongest idea in the episode is the quiet redefinition of what an engineer is for. Rauch’s point is that you no longer judge a person by how well they ship a single output. You judge them by whether they can build the factory that produces outputs B through Z. That reframe instantly explains why token leaderboards are nonsense. Counting tokens consumed is the same category error as counting lines of code written, a measure of motion mistaken for a measure of progress. Naval’s “waste tokens, save time” is the correct response: tokens are cheaper than people, so optimize for your own wall-clock time and the final output, and throw three models at the same problem if that gets you unstuck faster. The uncomfortable corollary, which the group says out loud, is that leverage in idea domains was never linear. The hundred-x and thousand-x engineer is not a new phenomenon. AI just made it impossible to keep pretending otherwise.

    The second thread that ties the whole hour together is verification. Everyone converges on the same future: humans stop producing the work directly and move up the stack to signing off on it. Rauch is precise about what that means. Saying “I understand this pull request” no longer requires reading every line. It requires being able to say you wrote the test harness, the proofs, the type checkers, and the simulations that let you stand behind it in production. That is a profound shift, because it accepts that the code may be spaghetti you do not fully understand while insisting that the evaluator around it is trustworthy. Blake extends the same logic to regulation, and this is the most underrated argument in the episode. If you treat a 200-page lightning-strike compliance document as a test suite and a regulation as an exit criterion for an agent loop, then a body of rules you once resented becomes a guard rail that lets you move faster, not slower. The cost of change collapses, change aversion drops, and you can finally afford to iterate on physical things.

    Max Hodak is the adult in the room on regulation, and the episode is better for it. The Silicon Valley consensus is that regulation is simply friction to be deleted, and there is plenty of dysfunction to point at: the NRC permitting essentially zero nuclear plants for decades, the FDA’s asymmetric incentives where approving a bad drug ends a career but blocking a good one costs nothing visible. But Hodak keeps pulling the conversation back to the harder truth. This is where the voters are. If you removed the current regulatory package, something very similar would get voted right back in, because the asymmetry reflects how the public actually weighs a visible death against an invisible delay. Real reform is not “deregulate,” it is narrow and surgical: prohibit the FDA from drawing adverse inferences across different users of a compound, build innovation zones where people consent to different rules, or copy Europe’s notified-body model so review capacity can actually scale. That is a far more serious position than the usual abundance-or-bust framing.

    The healthcare segment is the part of this conversation you will not find in the two clips, and it is the most heterodox. Hodak’s diagnosis is that healthcare is a fixed bucket of money that grows with tax receipts, not a technological growth industry where falling prices expand the market the way phones and laptops did. Because there is no real private market, you get a small communist society running inside a larger capitalist one, with the waiting lines and frozen product quality that implies. His prescription is not single payer and not insurance reform. It is to drive the cost of bringing devices and drugs to market so low that a patient can buy a restored sense or an extra decade of life on a credit card, the way they finance a car, and his warning is that China’s lower approval costs and its already-approved implantable brain interface put it on track to do exactly that. Whether or not you buy the twenty-percent-of-income deductible he floats, the framing that a private market is the missing feedback loop is the kind of argument that gets too little airtime.

    The closing debate on creativity is where the four of them disagree most productively, and they are careful enough to notice that their conclusions follow from their definitions. Hodak defines art as meaningful out-of-distribution behavior, which lets a military maneuver or a math proof count, and leads him to think a sufficiently capable model gets there too. Naval defines art as conveying an emotion with intent, which makes attribution load-bearing: the same photo down to the last pixel means more when a human took it, and a startup doing hardware attestation of human authorship suddenly has a real market. The shared observation that should worry every builder is that AI output collapses to a distribution mean. Every Claude-built website ends up the same serif font, the same brown and cream, the same monospace spacing, recognizable as slop precisely because it is in-distribution. The optimistic read, and the one Naval lands the episode on, is that this leaves an enormous and durable lane for humans who can step outside the system, and that the practical move for everyone is simply to become excellent with the tools, because the real divide is people with AI versus people without.

    Key Takeaways

    • The job of an engineer has shifted from shipping a single output to building the factory that produces multiplicative outputs, so people are now judged on the leverage they create rather than the work they personally do.
    • There were always 10x engineers, and in idea, intellectual, and digital domains the real spread is 100x or 1000x. AI leverage just made that gap impossible to deny.
    • Token leaderboards and token consumption are the new lines-of-code: a measure of activity that does not map to value. Measure your own time and the final output instead.
    • Waste tokens to save time. Models are still far cheaper than a human, so throwing Codex, Claude, and Gemini at the same problem repeatedly is rational even when it looks wasteful.
    • Low-quality first-pass code is fine because you can spend more tokens later to harden it for production. The constraint is verifiable domains, not code quality.
    • A model is roughly as good as you are in a domain. The quality of your prompting and reprompting strongly determines the output, though this dependence should fade as models improve.
    • Models graduated from junior to principal engineers: they now return with multiple routes and tradeoffs rather than running away with the first idea, even if their time and cost estimates are often wrong.
    • A junior gets knowledge they could never have produced alone, but an experienced architect still extracts far more juice. Taste and judgment, like picking Postgres versus ClickHouse, remain the human’s edge.
    • Pure software’s moat is in question now that models speak fuzzy, sloppy English. For hardware founders this is a boon, since good software finally becomes cheap to produce.
    • The building-block economy, from Mitchell Hashimoto, argues agents need powerful reusable infrastructure rather than reinventing queues and databases every time. Shared dependencies are a cooperation value, like everyone depending on the same Postgres version.
    • Naval and Max both stopped writing code for years, then started building software they use daily through agents, on the strength of understanding how the pieces fit rather than syntax.
    • With agents you stop getting stuck on narrow debugging problems that used to consume indefinite time. The intrinsic frustration that was once “how you learn” is largely gone.
    • Boom turned siloed hardware engineering, much of it trapped in Excel and VBScript with no source control, into real software with automated testing and repeatable flows.
    • Software engineers now build the architectures and hardware engineers vibe code their pieces, letting two engineers design an entire jet engine where a single turbine-blade analysis once took one engineer a full day across a thousand blades.
    • Enterprise collaboration software and even spreadsheets are getting cooked, because you can now code the exact custom tool you need instead of approximating it.
    • AI will soon generate step files and PCB layouts, bringing the current software boom to mechanical and electrical engineering, likely within the year.
    • China is betting on open-source models because its hardware and supply-chain superiority pairs with on-demand software generation to erase Silicon Valley’s software advantage. Fall behind on generating software and you fall behind on generating everything.
    • In real usage, frontier intelligence dominates the top. Gemini “slaps at scale” as an industrial production model for support and browser automation, while Chinese models are not in the frontier coding tier.
    • Intelligence is an unalloyed good. Because mistakes are invisible and models are cheaper than people, you reach for the smartest available model rather than running a weaker one many times.
    • Max’s vertical integration thesis: when you cannot buy a part, you make it. Science owns a captive MEMS foundry because tighter integration toward a single block of bonded matter yields lower power, smaller size, and longer life.
    • AI’s biggest near-term impact inside hardware companies is regulatory: generating documentation and tracing which of thousands of ISO standards apply, work that used to occupy a quality team for months.
    • Junior engineers got promoted to senior and junior engineering got handed to agents. The same pattern hits law, where basic NDAs and red lines no longer require a lawyer.
    • Humans are becoming verifiers. Signing off on a PR means standing behind its consequences via tests, proofs, and type checkers, not reading every line. Creating software is easy; keeping it secure, tested, and maintained 1000 days out is the real question.
    • A RAG over regulatory documents collapses a 200-page compliance test plan from months to minutes, which cuts change aversion: you can alter the airplane and regenerate compliance instead of crying over rework.
    • Regulations can act as a test suite and exit criteria for agent loops, as long as they are non-contradictory and reasonable. The alternative is shipping slop directly into the air.
    • Physical building is guilty until proven innocent, illustrated by the absurdity of pre-filing a driving plan before every trip. The fix is more enforcement-based regulation rather than pre-approval, though agents on both sides could trigger a red queen race and DDoS overwhelmed agencies.
    • Regulation often fails to make things safer, only slower: the 737 Max shipped a single sensor with full authority over pitch, and the NRC kept us perfectly safe by approving almost no nuclear plants for decades.
    • The deeper problem is the voters and the regulator’s asymmetric incentives. Approve a bad thing and your career ends; block a good thing and nobody notices. Removing one agency just elects its replacement.
    • Targeted fixes beat blanket deregulation: bar adverse inferences across users of a compound, use single-patient IND pathways, create opt-in innovation and YIMBY zones, or adopt Europe’s competitive notified-body reviewers.
    • Healthcare is a fixed bucket of money tied to tax receipts, not a growth industry, so spending 10x more on it would be a catastrophe rather than a triumph. With no private market you run a small communist society inside a capitalist one.
    • The escape is lower cost-to-market, not single payer, so people can finance care like a car. China’s lower approval costs and its already-approved implantable BCI point that direction. LASIK, dental, and plastic surgery advance because patients pay directly.
    • End-of-one medicine works at the high end, as with GitLab’s Sid Sijbrandij outliving his cancer prognosis through a self-built escalation ladder, but it demands enormous agency at the patient’s weakest moment. AI should democratize that knowledge.
    • Vercel automated much of site reliability engineering: anomalies fire alerts, an agent investigates, can open an incident, and begins remediation, stopping just short of changing production itself.
    • Running an open-sourced security tool against the whole monorepo with 10,000 concurrent agents produced several quarters of security research in a couple of days for about $14,000 in tokens. Code translation and optimization are similarly autonomous now.
    • Blake stopped all project work for a week and had everyone, receptionist to engineers, build something with AI and demo it. He expected mostly silly projects and got mostly needle movers, including a real automation from shipping and receiving.
    • The autonomous company of the future may have a workforce that trains the agents doing the work rather than doing it directly, with tooling that extracts reusable skills from your inputs and outputs.
    • Returns are shifting from intelligence toward agency for humans, since agents supply the intelligence. The people best fit for the future open a coding agent and ask what to build instead of defaulting to passive consumption.
    • Maybe 10x more people are coding than a year ago, yet around 99% still never will, because to a non-coder the starting step remains unimaginable. Vibe coding is described as more addictive and entertaining than video games, with real output.
    • AI video lacks taste and judgment for now, but by 2030 expect fan-made films: dozens of Lord of the Rings takes, or generating unmade seasons of The Expanse from the books. The bigger prize is a genuinely new imaginative work, not a remix.
    • What humans uniquely do is generate meaningful surprise out of the training distribution, with intent that makes it mean something. Gödel stepping outside the formal system is the archetype; Claude’s identical-looking websites are the counterexample of in-distribution slop.
    • Higher productivity historically means you hire more, not fewer, of the productive people. Expect a larger number of smaller teams, an entrepreneurship explosion, and generalists winning as credentials matter less than creativity, taste, and judgment.
    • The throughline is people with AI versus people without AI. The single best investment right now is getting genuinely good with the tools and learning the exact edges of what they can and cannot do.

    Detailed Summary

    Software Factories and the Thousand-X Engineer

    Guillermo Rauch opens with the idea that has him “pilled”: the engineer’s job has changed from shipping output directly to building the factory that produces multiplicative outputs. That reframes how you evaluate people and surfaces an old, controversial truth. He used to get flamed on Twitter for asserting 10x engineers, since it offends an equality instinct, but in intellectual and digital domains the real spread is 100x or 1000x, and choosing the right thing to work on is an infinite multiplier on top. AI leverage makes this less controversial, except that people now confuse token spend for productivity. The group agrees token leaderboards are the new lines-of-code. Max Hodak adds that a model is about as good as you are in a domain, so a capable developer gets a powerful collaborator while a junior gets junior-grade help, and the sporadic feedback you give, the reprompting, disproportionately determines the result. Naval’s posture is the opposite of fussy: he ignored every prompt-engineering trick on the bet that the models would improve faster than he could learn to game them, types less and less, and brute-forces problems by throwing multiple models at them. Waste tokens, save time, because tokens are cheaper than people.

    Is Pure Software Dead, and the Building-Block Economy

    Rauch describes models crossing from junior to principal engineer: they now return with several routes and explicit tradeoffs, push back when you try to jam high-cardinality telemetry into Postgres, and suggest ClickHouse or Athena instead. That elevates taste and judgment as the human contribution. He then poses the hard question: is pure software engineering obsolete now that models speak fuzzy, sloppy English and you no longer need code to communicate with them? For hardware founders it is a boon, echoing Patrick Collison’s line that software is art and artists are hard to hire. To temper the “agents reinvent everything” fantasy, he invokes Mitchell Hashimoto’s building-block economy: you do not want your agent rebuilding a queue from first principles every time it sends an email, and shared dependencies like a common Postgres version carry real cooperation value. Reusable infrastructure becomes more valuable in the agentic era, functioning like libraries and dependencies, or even a token cache, so models fork from existing starting points instead of burning a trillion tokens to recreate what exists. Naval and Max both note they had not written code in years and now build daily through agents, because understanding how APIs, data flow, and performance fit together matters more than syntax, and vibe coding is just transmitting intent the way a good engineering leader already did through people.

    Vibe Coding Hardware at Boom Supersonic

    Blake Scholl explains how AI changed the role of software and hardware developers at Boom. A great deal of hardware engineering lives in complex Excel spreadsheets and VBScript on individual laptops, with no source control and no automated testing, and handoffs happen manually over email like it is the 1990s. Boom had long tried to turn these flows into real software but could never afford enough software engineers. The new model is that software engineers create the architectures, because they understand systems, algorithms, and separation of concerns, and hardware engineers vibe code their own pieces. The result is mind-blowing productivity for small teams. His example: a turbine blade is cold at rest and expands when hot, so you must design both the cold and hot shapes and convert between structures and aerodynamics, work that took one engineer a full day per blade across a thousand blades in a jet. With a combined software-and-hardware tool you can now change blade geometry and see structural and aerodynamic results in real time, letting two engineers design an entire jet engine. The group extends this to the death of enterprise collaboration software and even spreadsheets, since you can now code the exact custom tool you need, and predicts AI will soon generate step files and PCB layouts, carrying the boom into mechanical and electrical engineering.

    China, Open Source, and Which Models Actually Get Used

    Naval argues China is going all-in on open-source models because its hardware and supply-chain superiority pairs naturally with on-demand software generation, which erases Silicon Valley’s software edge, and because the Chinese government has a history of funding ecosystem-wide efforts in network-effect businesses. Without frontier coding models there is no self-improvement, so a country that cannot generate frontier software falls behind on generating everything downstream. He notes the irony that almost all the open-source heft now comes from China, since OpenAI is not open, Grok and Google’s local models trail, and Anthropic ships no open models. On real usage, Rauch reports from Vercel’s AI gateway that frontier intelligence dominates the top, with a caveat: frontier intelligence at the right cost and performance, like Gemini, slaps at scale and is the best industrial production model for support and browser automation, while Chinese models are not in the frontier coding tier. Naval frames intelligence as an unalloyed good, since model mistakes are invisible and a smarter model is still cheaper than a person, which pushes everyone toward the most intelligent option and risks an oligopoly in AI.

    Vertical Integration, Verifiers, and the Slop Problem

    Max Hodak lays out Science’s vertical integration: the preference is always to buy, as with cheap PCBs from Asia, but when components do not exist you must make them, and the closer a product gets to a single block of covalently bonded matter the better it performs. Science owns a captive MEMS foundry on the east coast because there was no other way to do the packaging and assembly it needed. He notes AI’s most surprising internal impact so far is regulatory: generating documentation and tracing which of thousands of ISO standards apply, work that once tied up a quality team for months. Rauch raises the slop problem: mountains of AI-generated code arriving as pull requests nobody can read line by line. His standard is that an engineer must be able to say they understand and will stand behind the consequences of a PR, backed by the test harness, proofs, and type checkers, even without reading it all. Naval generalizes this into humans becoming verifiers, with lawyers, engineers, and operators moving to verifying the stack and standing behind it, and Rauch warns that creating software is the easy zero-to-one part while keeping it secure, tested, performant, and maintained a thousand days later is the real test.

    Regulation as Test Suite, and the Voter Problem

    Blake describes building a RAG that compresses a 200-page lightning-strike compliance test plan from months of a “monkey at keyboard” engineer’s work into minutes, with a powerful second-order effect: change the airplane and you regenerate compliance in minutes instead of crying over months of rework, which slashes change aversion and lets a small number of creative engineers iterate. Max reframes regulations as potentially good guard rails, a test suite and exit criteria for agent loops, provided they are non-contradictory and reasonable, since the alternative is shipping slop into the air. Naval warns of a red queen race of agent-on-agent compliance and agencies getting DDoSed by clever entrepreneurs flooding them with documents. Blake pushes for enforcement-based rather than pre-approval regulation, using the analogy that we would never tolerate filing a driving plan before every trip, yet that is exactly how physical infrastructure works: guilty until proven innocent. He cites the 737 Max’s single all-authority sensor and the NRC permitting almost no nuclear plants for decades as proof that this makes us slower, not safer. Hodak supplies the counterweight: the deeper issue is the voters and the regulator’s asymmetric incentives, where approving a bad thing ends a career and blocking a good thing goes unnoticed. Remove an agency and the electorate installs its twin. Naval and Max agree the real reforms are narrow, including innovation zones, opt-in YIMBY zones, and the experimental laboratory of fifty states.

    Drug Discovery, Healthcare Economics, and End-of-One Medicine

    Hodak explains why innovation zones do not solve drug discovery. The right-to-try act and single-patient IND already exist, and the FDA approves over 99% of such requests, sometimes by phone, but dosing requires clinical-grade drug that only the IP owner has, and the FDA will draw an adverse inference against the whole program if a very sick patient does worse. A targeted fix is to prohibit adverse inferences across different users of a compound. He points to Europe’s notified-body system, private certifiers blessed by governments, as a way to scale review capacity, and to China’s CFDA, which already approved an implantable brain-computer interface and brings products to market far cheaper. His core economic argument is that healthcare is a fixed bucket of money that grows only with tax receipts, unlike phones and laptops where falling prices expanded the market, so spending 10x more on healthcare would be a catastrophe rather than the triumph that 10x AI spending would be. With no private market you run a small communist society inside a capitalist one, with the lines and frozen quality that implies. The way out is lower cost-to-market so patients can finance care like a car, which is the direction China is pushing. Naval’s twist is a healthcare plan where the first 20% of income is the deductible to recreate a private market, citing LASIK, dental, and plastic surgery as fields that advance because patients pay directly. The group closes the segment on GitLab’s Sid Sijbrandij, who outlived a rare-cancer prognosis by building his own escalation ladder of drugs, noting that end-of-one medicine works at the high end but demands enormous agency exactly when a patient is weakest, which is where AI should democratize access to knowledge.

    Autonomous Software, Hackathons, and the Autonomous Company

    Asked how much autonomous software they run, Rauch describes Vercel automating much of site reliability engineering: instead of hand-set alarm thresholds, anomalies in error rate, latency, or throughput fire an alert, an agent investigates, can open an incident that loops in people, and begins remediation, stopping just short of changing production. Vercel also runs autonomous optimization and security research, and an open-sourced security tool run against the entire monorepo with 10,000 concurrent agents produced several quarters of security research in a couple of days for about $14,000 in tokens, the equivalent of months of red teaming. Max shares a vibe-coded bug-reporting queue where TestFlight users submit logs and screenshots, a daemon analyzes and fixes issues in the background, and ships him a build to try, raising the prospect of apps effectively built by their users, with the caveat that you would get a Homer Simpson car of every feature. Blake recounts stopping all project work for a week and requiring everyone, from the receptionist to the engineers, to build something with AI and demo it. He expected mostly silly projects and got mostly needle movers, including a genuinely useful automation from the shipping and receiving associate, concluding that most people have an idea worth building but cannot tell a good first idea from a bad one until they can iterate on a real thing. Rauch extends this to a workforce that trains the agents doing the work rather than doing it directly, and a coming feature to extract reusable skills from your inputs and outputs.

    Creativity, Out-of-Distribution Surprise, and What Humans Can Uniquely Do

    On the intelligence-versus-agency split, Max suggests returns to humans tilt toward agency since agents supply intelligence, while Naval counters that you stay 99% intelligence and 1% agency because the agents exercise the agency for you. They agree the humans best suited to the future are the agentic ones who open a coding agent and ask what to build. Coding has perhaps 10x more participants than a year ago, yet roughly 99% still never will, because the first step is unimaginable to a non-coder, even as vibe coding proves more addictive and entertaining than video games while producing something real. On AI video, the group notes it still lacks taste and judgment, but expects fan-made films by 2030, dozens of Lord of the Rings takes or generated seasons of The Expanse, while prizing a genuinely new imaginative work over a remix. The long closing debate turns on definitions. Hodak defines art as meaningful out-of-distribution behavior, broad enough to include a military maneuver, and expects models to reach it. Naval defines art as conveying emotion with intent, which makes attribution decisive: the same photo means more taken by a human, and a hardware-attestation startup gains a real use case. They cite Gödel stepping outside the formal system as the human archetype and the identical look of every Claude-built website as in-distribution slop. Naval lands the episode on optimism: productivity gains mean hiring more, not fewer, of the creative and AI-fluent, the future is a larger number of smaller teams and an entrepreneurship explosion where generalists thrive and credentials fade, and the single best move is to get extremely good with the tools, because it is people with AI versus people without AI.

    Notable Quotes

    “Now clearly there’s 100x or a thousandx engineers and the world hasn’t fully adjusted to this.”

    Guillermo Rauch, on why AI made the spread between engineers impossible to ignore

    “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, on the right way to measure AI’s return

    “We had to learn code to communicate with the models. Now the models speak English and they speak fuzzy sloppy English like a human and they understand things.”

    Guillermo Rauch, asking whether pure software engineering is now obsolete

    “It allows two engineers to design an entire jet engine, which is just wildly different.”

    Blake Scholl, on Boom turning hardware engineering into software

    “You need to be able to say I am signing off on understanding the consequences of this PR.”

    Guillermo Rauch, on what it means to stand behind code you did not read line by line

    “That is absolutely the way we build physical infrastructure in this country. It’s guilty until proven innocent. And what we should actually do is make more of these things enforcement based rather than pre-approval based.”

    Blake Scholl, comparing the permitting process to filing a driving plan before every trip

    “You’re basically running a small communist society inside a larger capitalist society. And that’s what we’re doing in healthcare.”

    Max Hodak, on why there is no real private market in healthcare

    “I expected we would get a large number of silly projects and a small number of needle movers. And what we got was a large number of needle movers and a very small number of silly projects.”

    Blake Scholl, on the week he had the whole company build with AI

    “If a person takes the photo versus AI generates the exact same photo down to the last pixel, the person taking the photo will have more meaning for me.”

    Naval Ravikant, on why intent and attribution make something art

    “It’s about people with AI versus people without AI. And so the single best thing you can be doing right now for yourself is just getting really good with these tools.”

    Naval Ravikant, closing the conversation on the only divide that matters

    Watch the full conversation here: The AI Industrial Revolution on the Naval Podcast YouTube channel.

    Related Reading

    • Part one: Waste Tokens to Save Time, our writeup of the first segment, on software factories, the thousand-x engineer, token leaderboards, and whether pure software is dead.
    • Part two: Vibe Coding Hardware, our writeup of the second segment, on AI-designed jet engines, vertical integration, China’s open-source bet, and humans as verifiers.
    • Naval Ravikant’s official site, the canonical home for Naval’s essays and podcast on technology, judgment, and leverage.
    • Boom Supersonic, Blake Scholl’s company building supersonic aircraft and its own jet engines, source of the turbine-blade and two-engineers example.
    • Science Corporation, Max Hodak’s brain-computer interface company, whose captive MEMS foundry and FDA arguments anchor the hardware and healthcare segments.
    • Vercel, Guillermo Rauch’s company, whose AI gateway data and autonomous SRE work inform the usage and automation discussion.

  • Vibe Coding Hardware: Naval, Guillermo Rauch, Blake Scholl, and Max Hodak on AI-Designed Jet Engines, Vertical Integration, China’s Open-Source Bet, and Why Humans Become Verifiers

    This is part two of Naval Ravikant’s conversation with frontier founders Guillermo Rauch of Vercel, Blake Scholl of Boom Supersonic, and Max Hodak of Science. Where the first part argued that you should waste tokens to save time and that the job of an engineer is now to build the factory rather than the output, this segment drags that thesis out of pure software and into atoms. The question on the table is what happens to hardware when models can vibe code the spreadsheets, the simulations, and eventually the step files and PCB layouts that aerospace, semiconductors, and biotech are built on. This segment is one half of the discussion, and you can watch and read the full episode here. The full conversation is on the Naval Podcast YouTube channel.

    TLDW

    Blake Scholl describes how Boom Supersonic took hardware engineering workflows that used to live in siloed Excel spreadsheets and VBScript on individual laptops, with handoffs done by email like it was the 1990s, and turned them into versioned, testable software. The new model is that software engineers build the architectures and the tools while hardware engineers vibe code their own domain-specific pieces, which collapsed a turbine-blade analysis that once took one engineer one day per blade into something where two engineers can design an entire jet engine in real time. Naval generalizes this into the cataclysm of enterprise software: there is no longer a startup that can sell you hardware collaboration tools because companies just code the exact thing they need on demand, and even spreadsheets are cooked because they only existed as a proxy for custom software nobody could previously afford to build. Blake predicts that within 2026 AI will move from generating software to generating step files and PCB layouts, which reshapes mechanical and electrical engineering. The group debates China’s open-source push as a way to neutralize Silicon Valley’s software advantage and protect its hardware and supply-chain superiority, lands on the point that if you fall behind on generating software you fall behind on generating everything, and Guillermo notes that frontier coding intelligence still dominates real usage while cheaper models like Gemini win at scale for support and browser automation. Max Hodak explains Science’s vertical integration, including a captive MEMS foundry on the East Coast, because the most innovative hardware cannot be bought off the shelf, and argues that software still needs hands since a model that cannot make physical things hits real boundaries. The conversation closes on the shift from writing to verifying: junior engineering got absorbed by agents while juniors got promoted, the same way paralegals could be seen as fired or promoted, and humans across law, engineering, and operations are becoming the verifiers who sign off on systems they did not write line by line.

    Thoughts

    The most important shift in this segment is that vibe coding stops being a software-industry story and becomes a deep-tech story. In part one the examples were Postgres, ClickHouse, and deploy targets. Here Blake Scholl is talking about turbine blades that change shape when they heat up, and the brutal fact that converting between cold and hot geometry, and between aerodynamics and structures, used to eat one engineer for one full day per blade in an engine that has a thousand blades. That is the kind of math that quietly kills ambition. When he says two engineers can now design an entire jet engine because the structural and aerodynamic results update in real time as you change the geometry, that is not a productivity improvement, it is a change in what a small team is allowed to attempt. The interesting move is the division of labor: software engineers build the architecture and the framework because they understand systems and separation of concerns, and the hardware engineers vibe code the pieces only they understand. Nobody has to become both.

    Naval’s “cataclysm of enterprise software” is the most investable idea in the episode, and it is darker than it sounds for anyone selling B2B tools. His claim is that the entire category of internal collaboration software is being eaten from the inside, because a company that can generate exactly the tool it needs on any given day will not pay a vendor for an approximation of that tool. His follow-on that even spreadsheets are cooked is the sharpest version of the point. The spreadsheet won for forty years precisely because it was the closest thing to custom software that a non-programmer could produce. Remove the constraint that custom software is expensive and the spreadsheet loses its reason to exist. The counterweight, which the group raised in part one with the block-economy thesis, is that the infrastructure primitives agents reach for get more valuable, not less. So the safe place to build is not the collaboration layer on top, it is the primitive underneath.

    The China discussion is the geopolitical center of the conversation and it lands on a genuinely uncomfortable insight. The argument is that China leans into open-source models not only because it is a model or two behind, but because open weights neutralize Silicon Valley’s software advantage and let China lean on what it already dominates: hardware, supply chains, and component ecosystems. If software can be generated on demand from open models, then the country with the factories wins the stack. The sharpest line is that if you fall behind on the ability to generate software, you fall behind on the ability to generate everything, because software is now upstream of every hardware pipeline. That reframes the open-versus-closed debate as a question about who controls the means of producing the means of production. It also quietly flatters the American frontier labs, since the same logic says self-improvement requires frontier coding models, and on that narrow axis the consensus at the table is that the Chinese models are not yet in the race.

    Max Hodak provides the necessary cold water, and it is the most grounding contribution in the episode. Everyone else is describing software eating the design layer, and Max points out that you still have to make the thing. Science owns a captive MEMS foundry on the East Coast not as a flex but because there was no other way to do the packaging and assembly for products that approach a single block of covalently bonded matter. His framing that the software still needs hands is the real boundary condition on all the AI-eats-everything talk: a model can be smarter than every engineer in the building and still be unable to deposit a layer, bond a wafer, or pass a regulatory inspection. The optimistic version, which he also makes, is that he has instrumented the foundry so that as models improve, the gains show up immediately in cell engineering and material science. The pessimistic reading is that the physical world remains a hard rate limiter, and the companies that own the atoms will capture more of the surplus than the companies that only own the bits.

    The closing thread on verification is where the whole conversation resolves into a job description for humans. Guillermo’s point that the biggest problem in software is mountains of slop arriving as a pull request, and that the answer is not pretending to read every line but being able to say “I am signing off on the consequences of this PR, and I wrote the harness, the simulations, the proofs, and the type checkers that let me,” is the most practically useful idea in the episode. It generalizes cleanly. The lawyer you trust is not the one who wrote every clause by hand, it is the one putting their reputation on the line that the document is sound. The production engineer who gets paged at 3am is the one signing off that the system is safe to ship. As models absorb the junior tier of every knowledge profession, the surviving human role is the verifier who carries the accountability. That is a promotion for the people who can hold it and an extinction event for the people whose value was doing the work nobody now needs done by hand.

    Key Takeaways

    • The factory framing from part one carries straight into hardware: you are judged on whether you build the system that produces multiplicative outputs, not on the single artifact, and the real multiplier was always 100x or 1000x, not 10x.
    • AI completely changes the role of software and hardware developers rather than just speeding either one up.
    • A huge amount of hardware engineering lives in complex Excel spreadsheets and VBScript on individual engineers’ laptops, with no source control, no automated testing, and handoffs done manually over email. It is software that is not treated as software.
    • Boom Supersonic’s move from day one was to turn traditional hardware engineering workflows into real software frameworks that are automatable and repeatable, to drive down the cost of iteration.
    • The old bottleneck was never being able to afford enough software engineers to build those frameworks. AI removes that constraint.
    • The new model: software engineers create the architectures because they understand systems, algorithms, and separation of concerns, and hardware engineers vibe code the domain pieces only they understand.
    • A turbine blade is cold when it starts and hot when it runs, so it changes shape, and you must design both the cold and hot geometry across aerodynamics and structures. Classically that was one engineer, one day, for one blade, in an engine with a thousand blades.
    • With software and hardware people combined, you can now change blade geometry and see the structural and aerodynamic results in real time, which lets two engineers design an entire jet engine.
    • Naval’s cataclysm of enterprise software: no startup can sell hardware collaboration tools anymore because companies just code the exact thing they need at any given time.
    • Even spreadsheets are cooked. Spreadsheets won only because nobody could build custom software, so a spreadsheet full of VBScript was the closest available approximation. Remove the cost barrier and the approximation loses.
    • Engineers are moving from Excel to Python models that produce believable simulations of physical systems.
    • AI can generate software today, but within 2026 it is expected to generate step files and PCB layouts, which opens up mechanical and electrical engineering as the next frontier.
    • The hardware software boon is biggest for small gadget and parts companies that historically shipped bad software because they could not afford good software. Now they can ship good-enough software, or skip the human front end entirely and expose hardware agentically for voice and agent control.
    • China goes all in on open-source models partly to neutralize Silicon Valley’s software edge: if software can be generated on demand from open weights, China’s hardware and supply-chain superiority stops being offset by a software disadvantage.
    • Other reasons cited for China’s open-source push: it is a model or two behind, it is distilling models, and the government has a history of funding efforts that lift the whole ecosystem, especially in network-effect businesses.
    • Open-source heft is coming almost entirely from China. OpenAI is not open, Grok publishes models but is seen as a model or two behind, Google’s local models are not very competitive, and Anthropic is not known for open-source releases.
    • Without frontier coding models you do not get self-improvement, and if you fall behind on generating software you fall behind on generating everything, because software now sits upstream of every hardware pipeline.
    • Real AI gateway usage shows open models do get used, but the top is heavily dominated by frontier intelligence.
    • Frontier intelligence at the right cost and performance slaps at scale. Gemini models are underrated and excel as industrial production models for support tasks and browser automation, even if they are not the top pick for coding.
    • For pushing the frontier you need the best possible coding model, which is now only two or three models, and the Chinese models are not among them.
    • One contrarian view at the table: use DeepSeek for 97% of tasks because it is cheap, run it repeatedly for harder problems, and reserve frontier models for the most advanced work. The counterargument: intelligence is an unalloyed good, mistakes are invisible and costly, and a smarter model is always cheaper than a person, so you default to the most intelligent option.
    • Always wanting the most intelligent model risks creating a monopoly or oligopoly in AI, because when two models disagree you cannot tell which is right, so you trust the smarter one and stop asking the weaker one.
    • Vertical integration is forced, not chosen: if you cannot buy it, you have to make it. The preference is always to buy when a vendor offers a service at a great price, like PCBs from Asia.
    • The closer a product gets to a single block of covalently bonded matter, the better it performs: lower power, smaller, higher performance, longer lasting. The components for that level of integration simply are not available to buy.
    • Science owns a captive MEMS foundry on the East Coast, bought because there was no other way to do the packaging and assembly the company needed.
    • One of the biggest near-term AI impacts inside hardware companies is regulatory and documentation work: tracing which of thousands of ISO standards apply used to occupy a regulatory and quality team for months, and now AI just knows.
    • Software still needs hands. A model can be smarter than us and still hit real boundaries if it cannot physically make things, which is why Science has instrumented its foundry so model improvements show up immediately in cell engineering and material science.
    • Basic legal work is already going away. People have stopped asking lawyers for NDAs and routine agreements, because law is spaghetti code in English with no real APIs, and the basic tasks are handled by AI.
    • Junior engineers got promoted to senior engineers while junior engineering itself got taken over by agents. The same framing applies to paralegals: fired, or promoted to senior lawyers who now spend their time thinking about the law.
    • What you value in a lawyer is a trusted authority who puts their reputation on the line, not someone who read every clause. The same trust model is coming to engineering.
    • The biggest problem in software engineering today is mountains of slop arriving as a pull request. The old norm of reading every line of a PR is gone.
    • The new standard is being able to say “I understand and I am signing off on the consequences of this PR,” backed by the test harness, simulations, proofs, and type checkers you built, even without reading every line.
    • Embrace a world where code is spaghetti you do not fully understand, but build the evaluators that give confidence, and rely on production engineers to sign off because someone gets paged if the system goes down.
    • Creating software is easy from zero to one. The hard part is a thousand days from now: is it secure, tested, production grade, and performant, and are you still motivated to invest the tokens to maintain it in prod?
    • Humans are becoming verifiers. The same way models are trained on good verification data, the old functions of lawyers, engineers, and operations people are moving to verifying the stack and standing behind it.

    Detailed Summary

    Turning Hardware Engineering Into Software

    Blake Scholl opens by describing how AI completely changes the role of software and hardware developers at Boom Supersonic. From day one the company tried to take traditional hardware engineering workflows and turn them into software. For anyone who has not been around hardware engineering, he explains that an enormous amount of it happens in complex Excel spreadsheets on individual engineers’ laptops, sometimes with VBScript code, all of which is actually software but is not treated as software. There is no source control, no automated testing, and when an aerodynamicist hands work to a structures engineer it is done manually with a spreadsheet over email, like it is the 1990s. Boom started building software frameworks to automate and make those flows repeatable so the cost of iteration would drop, but progress was slow because the company could never afford enough software engineers.

    Two Engineers, One Jet Engine

    The mind-blowing change, in Blake’s words, is a new division of labor. Software engineers create the architectures because they understand systems, algorithms, and separation of concerns, and then hardware engineers vibe code the pieces that draw on what they uniquely know about hardware. The result is wildly different productivity for small teams. His example is the turbine blade: it starts cold and gets bigger as it heats up in operation, so you have to design both the cold shape and the hot shape, converting between them and between structures and aerodynamics. Classically that was one engineer, one day, for one blade of analysis, in a jet engine with a thousand blades, which means you simply could not do much. Now, with software and hardware people working together, you can change blade geometry and see the structural and aerodynamic results in real time, which allows two engineers to design an entire jet engine.

    The Cataclysm of Enterprise Software

    Picking up on the point that software engineers now build the tools and architectures for everyone else, Naval names what he calls the cataclysm of enterprise software. There is no longer a startup that can build and sell hardware collaboration tools, because internally companies just code the right things they need at any given moment. Even spreadsheets are cooked, he argues, because the reason spreadsheets succeeded is that no one could build custom software, so a spreadsheet stuffed with VBScript functions was the closest available approximation. With that constraint gone, the proxy collapses. He notes he has personally moved almost entirely from Excel to Python models where he can get believable simulations of things.

    Generating Step Files and PCB Layouts

    The next frontier, Blake suggests, is the thing AI has not reached yet but probably will within 2026: today it can generate software, but soon it will generate step files and PCB layouts, and when it comes for mechanical and electrical engineering that will be a whole other thing nobody has seen yet. On the hardware side this is described as a particular boon for the many small gadget and parts companies that historically wrote bad software because they could not make great software. Now they can make good-enough software, or skip a human front end entirely and expose the hardware agentically, so that an agent accesses it and a person controls the hardware by voice.

    China’s Open-Source Bet and Hardware Superiority

    This leads into one of the reasons China is described as going all in on open-source models. With hardware superiority, complex supply chains, and deep component chains, China’s logic is that if it can generate software on demand it no longer suffers a software disadvantage against Silicon Valley. That is framed as not the only reason: China is also a model or two behind, it is distilling models, and the government has a history of funding efforts that lift the entire ecosystem, especially in network-effect businesses. Ironically, the open-source heft comes from China precisely because OpenAI is not open, Grok publishes models but is a model or two behind, Google’s local models are not very competitive, and Anthropic is not known for open releases. The deeper point is that without great frontier coding models you do not get self-improvement, and if you fall behind on the ability to generate software you fall behind on the ability to generate everything, because generating software is embedded in every piece of the hardware pipeline.

    Frontier Intelligence vs. Cheap Models

    Naval raises a dinner-table argument from the night before, where someone claimed you will use DeepSeek for 97% of things because it is cheap, run it repeatedly when you need more intelligence, and reserve OpenAI or Anthropic for the most advanced tasks. Naval pushes back: intelligence is an unalloyed good, you always want more of it, model mistakes are invisible, and a smarter model is always cheaper than a real person in real time, so you default to the most intelligent model available. He notes the downside is that this tends toward a monopoly or oligopoly, because when two models give different answers you often cannot tell which is correct, so you trust the smarter one and gradually stop asking the weaker one. Guillermo confirms with AI gateway data that open models do get used, but the top is heavily dominated by frontier intelligence. His caveat is that frontier intelligence at the right cost and performance slaps at scale: Gemini models are underrated but are excellent industrial production models for support tasks and browser automation, while for pushing the frontier you need the best possible coding model, now only two or three models, and the Chinese models are not in that set.

    Vertical Integration and the Captive MEMS Foundry

    Asked about his push into vertical integration and extreme urgency, Max Hodak explains that for many things you cannot buy what you need, so you have to make it. The preference is always to buy when a vendor offers a service at a great price, and he points to PCBs, which are basically free and available in unlimited quantity from Asia. But the closer a product gets to being a single block of covalently bonded matter, the better it is: lower power, smaller, higher performance, longer lasting. The components for that level of integration are not available, so to innovate beyond piecing together off-the-shelf parts you have to learn to do it yourself, which shows up as vertical integration. Science owns a captive MEMS foundry on the East Coast, bought because there was no other way to do the packaging and assembly work the company wanted.

    Software Still Needs Hands

    Max expects AI to heavily affect all of this over the next few years, though it is not quite there yet. Ironically, one of the biggest impacts already seen is in regulatory interactions and documentation: figuring out which of thousands of ISO standards apply to a product change, and tracing it through, used to occupy a regulatory and quality team for months, and now the AI just knows. But for things like the surgical program or the MEMS fab, he argues the software still needs hands. It will be smarter than us, but if it cannot make things, those are real boundaries. Science has instrumented its foundry and many other parts of the company so that as models get better, the improvement shows up immediately in cell engineering and material science.

    Lawyers, Paralegals, and the Promotion of Junior Work

    The discussion turns to law as a parallel to engineering. It has been a while since anyone at the table generated a basic legal document using a lawyer. Routine work like NDAs and standard agreements is gone, because law is essentially spaghetti code that contradicts itself and has no real APIs, expressed in complicated English. Junior engineers got a promotion to senior engineers while junior engineering itself was taken over by agents, and the same framing applies to paralegals: you can say they were fired, or you can say they were promoted to senior lawyers who now spend their time thinking about the law. What you actually value in a lawyer is a trusted authority who went to law school and puts their reputation on the line when they tell you a document is legit.

    Slop PRs, the Thousand-Day Problem, and Humans as Verifiers

    Guillermo argues the biggest problem in software engineering today is mountains of slop ending up as a pull request. The old meme of reading every line of a PR is gone. In infrastructure he wants engineers to be able to say they understand and are signing off on the consequences of a PR, backed by the test harness, simulations, proofs, and type checkers they wrote, so they have confidence it will be safe in production even without reading every line. There is a world where everyone embraces that the code is spaghetti nobody fully understands, but builds the evaluators that give confidence and relies on production engineers to say it is fine to ship, because someone gets paged if the system goes down. The further warning is that creating software is easy from zero to one, but a thousand days from now you have to ask whether it is secure, tested, production grade, and performant, and whether you are still motivated to invest the tokens to maintain it in prod. The resolution is that humans are becoming verifiers, the same way models are trained on good verification data, and the old functions of lawyers, engineers, and operations people are moving to verifying the stack and standing behind it.

    Notable Quotes

    “What I found is it completely changes the role of software and hardware developers.”

    Blake Scholl, on how AI reshaped engineering at Boom Supersonic.

    “If you want to hand something off from like an aerodynamicist to a structures engineer that’s done manually with like a spreadsheet over email. It’s the 1990s. It’s terrible.”

    Blake Scholl, describing the state of traditional hardware engineering workflows.

    “It allows two engineers to design an entire jet engine, which is just wildly different.”

    Blake Scholl, on collapsing turbine-blade analysis with real-time structural and aerodynamic feedback.

    “Even spreadsheets are kind of cooked, right? Because the reason spreadsheets were successful is that no one could build custom software.”

    Naval Ravikant, on the cataclysm of enterprise software.

    “Right now it can generate software, but soon it’ll be able to generate step files and PCB layouts. And when it comes for mechanical and electrical engineering, that will be a whole other thing that we haven’t seen yet.”

    Blake Scholl, on the next frontier for AI in hardware.

    “If you fall behind on your ability to generate software, you fall behind on the ability to generate everything.”

    Naval Ravikant, on why software now sits upstream of every hardware pipeline.

    “Anytime I’m working to push the frontier you need the best possible coding model, and that’s basically now like two or three models, and the Chinese are certainly not in it.”

    Guillermo Rauch, on where frontier coding intelligence actually lives.

    “You can’t buy it, so you got to make it somehow. The closer that our products get to being like a single block of covalently bonded matter, the better they’ll be.”

    Max Hodak, on why Science is forced into vertical integration.

    “The software still needs hands. It’s going to be smarter than us, but if it can’t make things, then those are real real boundaries.”

    Max Hodak, on the physical limits of AI in hardware.

    “You need to be able to say I am signing off on understanding the consequences of this PR, or I wrote the test harness, the simulations, the proofs, the type checkers, to be able to say even without reading this, I have confidence it’s going to be safe in production.”

    Guillermo Rauch, on what code review becomes in the age of slop PRs.

    “Creating software is really easy 0 to one. But think about a thousand days from now. Is it secure? Is it tested? Is it production grade? And are you still motivated to invest all of those tokens in maintaining it in prod?”

    On the long-term cost of software that is cheap to create and expensive to keep alive.

    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 one: Waste Tokens to Save Time, the first half of this same conversation, where Naval, Guillermo Rauch, Blake Scholl, and Max Hodak argue that the job of an engineer is to build the factory and that pure software is not dead.
    • Boom Supersonic, Blake Scholl’s company building supersonic civilian aircraft and its own jet engines, the source of the turbine-blade and two-engineers example.
    • Science Corporation, Max Hodak’s company, whose captive MEMS foundry and surgical program anchor the vertical-integration argument.
    • Vercel, Guillermo Rauch’s company, whose AI gateway data informs the point about frontier intelligence dominating real usage.
    • Microelectromechanical systems (Wikipedia), background on the MEMS technology behind the captive foundry Max Hodak describes.

  • 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.

  • Naval Ravikant 2026 Megasode: Every Lesson on Wealth, Happiness, Judgment & Truth (4-Hour Breakdown)

    TLDR

    Naval Ravikant sat down with Eric Jorgenson (author of The Almanack of Naval Ravikant) for a 4+ hour megasode on the Smart Friends podcast — his most comprehensive public conversation in years. Five years after the original Almanack, Naval updates and expands his thinking across five pillars: building wealth, building judgment, learning happiness, saving yourself, and philosophy. The biggest shifts? He now leans heavily on David Deutsch’s definition of wealth as “the set of physical transformations you can affect,” sees AI as the ultimate leverage tool (not a replacement for human judgment), and has moved past chasing happiness toward pursuing truth, love, and beauty. He’s working on a new stealth company, has met roughly a dozen people he considers genuinely enlightened, and believes the most important formula for life is: stay healthy, get wealthy, seek truth, give love, and create beauty.

    Key Takeaways

    On Wealth

    Deutsch’s definition is deeper than “assets that earn while you sleep.” Naval now defines wealth as the set of physical transformations you can affect — and the biggest driver of that capability is knowledge, not capital. If you removed Elon Musk from SpaceX, the wealth doesn’t just transfer. It disappears. The value is in the knowledge, not in the factory.

    Knowledge is the real multiplier. Ten modern humans can change more than ten paleolithic humans — not because of capital, but because of accumulated knowledge. As a society gains knowledge, it becomes wealthier. As an individual gains knowledge, they become wealthier. This is why Marx was fundamentally wrong: value is not in the capital. It’s in the people doing things.

    Ethical wealth creation is not only possible — it’s the norm in free markets. The common critiques of capitalism target cronyism, money printing, and government favoritism. None of that is free market capitalism. Real capitalism is a minimum structured set of rules that channels competitive energy into creating property instead of fighting over it.

    This is the greatest period for wealth creation in human history. More knowledge, more capital, more leverage than ever before. If you’re moderately intelligent, not afraid of hard work, and flexible, you can do extremely well. But it takes 10 to 30 years. There are no get-rich-quick schemes.

    AI is the ultimate leverage tool, not a replacement. Software engineers aren’t being replaced by AI — AI is letting software engineers replace everybody else. The people saying “programming is dead” are completely wrong. The most leveraged engineers are the ones building AI systems, then the ones using them. AI is great when wrong answers are okay. For anything requiring creativity or judgment at the edge, you still need humans.

    Good products are hard to vary. Drawing from David Deutsch’s epistemology, Naval argues that the best products — like the iPhone — are like good scientific explanations: you can’t change the details without breaking them. They encapsulate deep knowledge, have surprising reach into applications the creators never imagined, and exhibit winner-take-all network effects.

    On Judgment

    Judgment is the most valuable thing in the age of infinite leverage. The difference between a CEO who’s right 80% of the time and one who’s right 85% of the time is worth billions of dollars when you’re steering a multi-trillion dollar ship. Direction matters more than any other single thing.

    Judgment evolves into taste. First you reason through decisions logically. Then your subconscious enters into it (judgment). Then your whole body reacts to it (taste). The Rick Rubins and Steve Jobs of the world operate at the level of taste — they can’t fully explain why something is right, they just know. Naval says his investing is now “almost entirely taste.”

    It takes time to develop your gut, but once it’s developed, don’t listen to anything else. This applies to people, investments, products, and life decisions. Older people have very good judgment about other people because human interaction is the one area where everyone is constantly gaining experience.

    Learn from specific to general, not general to specific. This is Seneca’s insight: encounter reality, test it, learn from it, then generalize. Going the other way creates what Nassim Taleb calls “intellectual yet idiot” — someone overeducated and underpracticed. If you want to be a philosopher king, first be a king.

    Hard work is non-negotiable, but it shouldn’t feel like work. The most productive people work intensely on problems that fascinate them. The biggest breakthroughs come during deep immersion — 24-36 hour sessions where you can’t put the problem down. But if it feels like forced drudgery, you’ll lose to someone who finds it genuinely enjoyable.

    AI doesn’t have judgment. It has incredible information retrieval — the ability to cross-correlate all human knowledge and return the conventional correct answer. But for creative problems, novel situations, or anything requiring values and binding principles, AI falls short. It raises the tide for everyone, but there’s no “alpha” in the AI answer because everyone gets the same one.

    On Happiness

    Naval’s latest thinking: he’s not sure happiness exists. Happiness is a construct of the mind, a thought claiming to be a state. When the thought disappears, there’s no “you” there to be happy or unhappy. His focus has shifted from pursuing happiness to cultivating peace — being okay with things as they are, with few and consciously chosen desires.

    The three big ones are wealth, health, and happiness — pursued in that order, but their importance is reversed. Naturally happy people have the greatest gift and don’t need the others. Health matters more than wealth (a sick man only wants one thing). But most people will pursue them wealth-first simply because of energy, flexibility, and the practical reality of financial obligations when young.

    The more you think about yourself, the less happy you’ll be. Depressed people ruminate on themselves. Having motives larger than yourself — your mission, your children, your contribution — makes setbacks hurt less because they’re not personal. This is why Naval says: live for something larger than yourself, but only on your own terms.

    Chronic unhappiness is an ego trip. Acute unhappiness is real and useful — it’s a signal. But chronic unhappiness is wanting to feel more “you,” more separate, more important. Identity creates motivated reasoning. The thinner your identity, the more clearly you can see reality.

    The modern devil is cheap dopamine. Every deadly sin is a form of cheap dopamine. The direct pursuit of pleasure causes addiction and dopamine burnout. Virtues are the opposite — long-term individually beneficial behaviors that also create win-win outcomes for society. All virtues can be reinterpreted as long-term selfishness.

    Meditation isn’t about enlightenment — it’s about self-observation. When you’re more self-aware, you catch your mind doing things that aren’t in your long-term interest. You can reset, question whether a desire matters, and choose whether to reinterpret a situation or address the underlying problem.

    You don’t store memories — you store interpretations of memories. Changing those interpretations is what forgiveness actually is. Psychedelics, meditation, and honest introspection all work partly because they allow you to reprocess and reframe past experiences.

    On Saving Yourself

    Nobody is coming to save you. An ideal life is designed, not inherited. Naval claims his life is “really good” — at any given time he’s doing what he wants, nothing is obligatory, and if something stops being enjoyable, he changes it very quickly. This requires ruthless honesty about relationships, obligations, and what you actually want.

    Every relationship is transactional — and that’s okay. Naval draws a hard line against false obligations. He doesn’t attend obligatory events, weddings, or ritualistic celebrations. The result: he’s left with people who are similarly free, low-ego, and voluntarily present. Nobody takes each other for granted.

    The secret to a happy relationship is two happy people. You can’t be happy with your spouse if you’re not happy alone. Happiness is personal and must be tackled individually. Putting relationships ahead of your own inner work gets you neither.

    God, kids, or mission — find at least one. Naval has all three. His “God” is personal and unarticulated. Family is irreplaceable (expand your definition as you age). And mission means actively building — right now that’s a stealth company and this kind of conversation.

    Explore widely, then invest deeply. Modern society has made exploration easy, but all the benefits come from compound interest. You don’t learn through 10,000 hours — you learn through 10,000 honest iterations. Do, reflect, change, try again. Once your judgment tells you what fits, stop exploring and start compounding.

    The only true test of intelligence is whether you get what you want out of life. This is a two-part test: choosing what to want (the harder part) and then getting it. If you pass that test, there’s nothing to be envious of. Choose inspiration over envy — find the part of someone else’s success that resonates with something inside you.

    On Philosophy

    Naval’s philosophical foundation: evolution + Buddhism + Deutsch. Evolution explains humans. Buddhism is the most time-tested internal philosophy. David Deutsch’s epistemology — good explanations that are hard to vary, conjecture and criticism — provides the best framework for understanding progress in science, business, and society.

    Truth is a crystal in the multiverse. In the many-worlds interpretation, true knowledge replicates across more universes because it works. False knowledge is infinitely variable but gets eliminated. The “Rickiest of the Ricks” (from Rick and Morty) is the most truth-oriented version — lowest ego, least motivated reasoning, operating from the most universal principles.

    Enlightenment is binary, not a path. Naval has met about a dozen people he considers genuinely enlightened. They share one trait: persistent experience of “no self.” Nothing bothers them — not cancer diagnoses, not personal failures. It’s not that they lack desire or capability. They’re often more effective, not less. But they don’t take anything personally.

    The self is just a thought. When you look for the self — really look — you can never pin it down. It’s like a burning stick whirled in a circle that appears to be a flaming wheel. Just thoughts convincing you there’s someone there. Enlightened people have seen through this and their default state is pure awareness.

    The real truths are heresies. There’s a 2×2 matrix of truth vs. spreadability: conventional wisdom (true and spreads), fake news (false and spreads), nonsense (false and doesn’t spread), and heresies (true but don’t spread). Heresies don’t spread because any truth that lowers group cohesion gets suppressed. This is why the greatest philosophers are read long after their deaths — they told harsh truths while alive that society wasn’t ready to hear.

    Read the best 100 books over and over. Naval reads authors, not books. He reads philosophers, not authors. He’ll consume everything by Schopenhauer, Deutsch, Osho, Taleb, Krishnamurti — and until he’s finished everything by one thinker, he won’t move to the next. He judges philosophers by the outcomes they achieved in their own lives. A philosophy that led its creator to misery is suspect.

    Simulation theory is just modern religion. Every era maps its dominant technology onto religion — the sun god, the god-king, the mechanical universe, and now the computational universe. Naval finds understanding relativity, quantum physics, and cosmology more satisfying than saying “the universe is a computer.” He maps Buddhism onto simulation theory (the white room in the Matrix = pure consciousness = enlightenment) but considers sim theory unfalsifiable and reductive.

    Detailed Summary

    Part 1: Building Wealth (0:00 – 37:49)

    The conversation opens with Naval updating his definition of wealth through David Deutsch’s lens. Where he originally defined wealth as “assets that earn while you sleep” — a practical definition aimed at escaping the 9-to-5 trap — he now sees wealth more expansively as the set of physical transformations you can affect. This reframes wealth from a passive accumulation game to an active capability powered primarily by knowledge.

    Naval makes a forceful case that knowledge, not capital, is the real wealth multiplier. He uses SpaceX as his central example: remove Elon Musk and the wealth doesn’t just redistribute — it evaporates, because the knowledge that makes SpaceX valuable disappears with the people who hold it. This is why Marxism fundamentally fails. The value isn’t in the factories. You can’t slice it up and redistribute it like gold.

    He addresses the ethics of capitalism head-on, acknowledging that the majority of economic activity involves people fighting over existing wealth rather than creating new wealth (he draws an analogy to nature, where parasitic species outnumber standalone ones six to one). But he argues that free market capitalism, at its core, is the system that channels competitive energy into creation rather than destruction. The critiques of capitalism — bank bailouts, cronyism, government favoritism — target corruption of the system, not the system itself.

    On AI and leverage, Naval makes what may be his most quotable claim: “AI is not going to replace software engineers — AI is going to let software engineers replace everybody else.” He sees AI as an incredible information retrieval and calculation tool that raises the floor for everyone, but provides no lasting competitive edge because everyone has access to the same answers. The real edge comes from judgment, creativity, and taste — the things AI cannot provide.

    He connects Deutsch’s concept of “good explanations” to product building. Good products, like good scientific theories, are hard to vary — you can’t change the details without breaking them. The iPhone’s original form factor is still essentially unchanged because they nailed it. He notes that all technology has winner-take-all dynamics, and the best products amortize their development costs over the largest user base, making it impossible for any amount of money to buy a better alternative.

    Part 2: Building Judgment (37:49 – 1:12:30)

    Naval describes judgment as the single most important capability in an age of infinite leverage. He traces its development from conscious logical reasoning through subconscious intuition to full-body taste — the stage where you simply know what’s right without being able to articulate why.

    He quotes John Cleese on creative problem-solving: “You simply have to let your mind rest against the problem in a friendly, persistent way.” This captures Naval’s view that breakthroughs require both intense focus and a relaxed, non-forcing attitude. He shares his own experience writing a compiler in college, where his most productive sessions were 24-36 hour marathons because it took hours just to reload the problem into his head after time away.

    The section includes an important distinction between AI’s capabilities and human judgment. AI can cross-correlate all human knowledge and deliver the conventional correct answer for solved problems. But it lacks values, binding principles, and the ability to handle novel situations with idiosyncratic context. Naval sees AI as “magic” that looks like intelligence because of its staggering information retrieval, but it operates as a one-size-fits-all system trained on textbooks and data labelers’ opinions.

    He emphasizes learning from specific to general (Seneca’s principle), warns against academic over-education without practice (Taleb’s “intellectual yet idiot”), and shares how he now reads less but more deliberately — using reading to spark his own thinking rather than absorbing others’ ideas for regurgitation. He singles out Schopenhauer as a writer where every sentence is crafted and you get something different from the same essay on every re-read.

    Part 3: Learning Happiness (1:12:30 – 2:15:17)

    This is the most philosophical section, where Naval significantly updates his earlier thinking. He admits he’s “not sure happiness exists” as a distinct state, framing it instead as a thought that claims to be a state. When the thought disappears, there’s no observer left to be happy or unhappy. This is deeply Buddhist — the no-self doctrine applied to emotional states.

    His practical advice centers on cultivating peace rather than chasing happiness. He wants few, consciously chosen desires. He wants to act for reasons larger than himself (which paradoxically makes failure hurt less). And he wants to create space for authentic joy rather than ritualistic obligation.

    Naval introduces his framework of “truth, love, and beauty” as what remains after health and wealth are handled. Truth is pursued because even uncomfortable truths make life better (he uses The Matrix’s Neo vs. Cipher as his central illustration). Love is best experienced as giving rather than receiving — falling in love with someone or something is the high, not being loved. Beauty is creation — the highest human art form and what separates his view from pure Buddhist quietism.

    He discusses William Glasser’s choice theory at length, presenting the controversial view that depression often originates as a series of childhood behavioral choices that became unconscious habits. While acknowledging chemical components, he argues the explanation must be offered at the same level as the question — and that changing your brain through honest self-examination is more sustainable than long-term pharmaceutical intervention.

    The section on meditation is refreshingly honest: the first 20 minutes your mind goes berserk, then it calms, and most of the benefit comes from simply acknowledging emotions rather than solving them. He describes a personal experience of extreme unhappiness where a part of him was simultaneously watching and recognizing “there’s nothing actually here — you’re creating a drama to feel important.”

    Part 4: Saving Yourself (2:15:17 – 2:50:17)

    Naval gets deeply personal about how he’s designed his life. He claims to have “an amazing life” where at any given time he’s doing exactly what he wants. Nothing is obligatory. Every relationship is voluntary. He maintains zero estranged family members while refusing to attend weddings, obligatory events, or ritualistic celebrations.

    His stance on relationships is uncompromising: every relationship is transactional (providing mutual value), and pretending otherwise creates false obligations that breed resentment. He refuses to train his children to say “thank you” on command — if they feel genuine gratitude, it will emerge naturally. He believes the only real relationships are peer relationships, even employer-employee ones.

    The exploration-vs-investment framework is one of the most actionable parts of the conversation. Modern society has made exploration easy (you can fly anywhere, enter any career, date infinitely), but all benefits come from compound interest — which requires commitment. The key transition is recognizing when to stop exploring and start investing. Naval argues that learning happens through honest iterations (do, reflect, change, repeat), not hours logged.

    He names his sources of meaning: a personal relationship with “whatever this is” (God, loosely), his children and family, and his current stealth company. He explicitly says he doesn’t feel qualified to write a book about enlightenment because he hasn’t fully explored it himself — and he’s partly just lazy.

    Part 5: Philosophy (2:50:17 – End)

    The final section weaves together Naval’s philosophical commitments: evolution, Buddhism, and David Deutsch’s epistemology. He frames truth as “a crystal in the multiverse” — in the many-worlds interpretation, truth replicates because it works, while falsehood is infinitely variable but gets eliminated through skin-in-the-game dynamics.

    His account of enlightened people is fascinating and specific. He’s met about a dozen, verified to his own satisfaction through sustained observation (watching them encounter genuinely bad events without perturbation). They include well-known names like Rupert Spira, Mooji, and Sadhguru, plus personal friends and lesser-known figures. The key trait: a persistent experience of no self. It’s binary — not a gradient. They’re often more capable, not less. More authentic desires, less mimetic behavior, less ego-driven.

    He maps Buddhism onto simulation theory in an extended riff: breaking out of the Matrix is the quest for enlightenment, the white room is pure consciousness, and the boredom of the white room explains why consciousness generates infinite forms (why God forgets himself and goes back into the game). But he ultimately considers simulation theory a “lousy theory” — unfalsifiable, reductive, and just the latest version of mapping our dominant technology onto religion.

    The conversation closes with Naval’s 2×2 matrix of truth and spreadability (conventional wisdom, fake news, heresies, nonsense) and the observation that the only things that make it through the information environment are fake news — because conventional wisdom doesn’t need spreading, heresies can’t spread, and nonsense goes nowhere. The real truths, the heresies, can only be discovered, whispered, and perhaps read.

    Thoughts

    Five years after The Almanack of Naval Ravikant, this megasode feels like Naval 3.0. The original Naval (pre-Almanack) was focused on practical wealth creation and startup wisdom. Almanack Naval synthesized that with Eastern philosophy and general life principles. This version integrates David Deutsch’s epistemology into everything — wealth becomes knowledge creation, good products become good explanations, and even enlightenment gets framed through the multiverse.

    What strikes me most is the honesty about contradictions. Naval simultaneously says he’s “not sure happiness exists” while describing his life as amazing. He advocates dropping all obligations while maintaining zero estranged family members. He promotes laziness while admitting he’s working harder than ever on his new company. These aren’t inconsistencies — they’re the natural texture of a philosophy that’s been lived rather than theorized.

    The AI section is worth paying attention to. In a world where every AI influencer is either panicking about job replacement or promising utopia, Naval’s take is refreshingly grounded: AI is leverage, like every technology before it. It raises the floor for everyone. It provides no lasting edge because everyone gets the same answer. The edge comes from judgment, taste, and creativity — which are developed through experience, not downloaded from a model.

    His list of “enlightened” people is going to generate the most discussion and controversy. Claiming to have personally verified a dozen enlightened beings is a bold statement from someone who also says he’s “not sure there’s such a thing as enlightenment.” But it’s consistent with his framework: enlightenment isn’t a special state. It’s the absence of a constructed self. It’s binary. And it doesn’t prevent you from running a company, dating, or living a fully functional life.

    The deepest insight might be the simplest: stay healthy, get wealthy, seek truth, give love, and create beauty. If you internalize nothing else from these four hours, that five-part formula is worth the price of admission — which, in keeping with Naval’s philosophy, is free.

    This article is a summary and analysis of Naval Ravikant’s 4-hour megasode on the Smart Friends podcast with Eric Jorgenson, released January 2026. The full episode is available for free on YouTube and all major podcast platforms.

  • Naval Ravikant on AI: Vibe Coding, Extreme Agency, and the End of Average

    TL;DW

    Artificial intelligence is fundamentally shifting how we interact with technology, moving programming from arcane syntax to plain English. This has given rise to “vibe coding,” where anyone with clear logic and taste can build software. While AI will eliminate the demand for average products and hollow out middle-tier software firms, it simultaneously empowers entrepreneurs and creators to build hyper-niche solutions. AI is not a job-stealer for those with “extreme agency”—it is the ultimate ally and a tireless, personalized tutor. The best way to overcome the growing anxiety surrounding AI is simply to dive in, look under the hood, and start building.

    Key Takeaways

    • Vibe coding is the new product management: You no longer manage engineers; you manage an egoless, tireless AI using plain English to build end-to-end applications.
    • Training models is the new programming: The frontier of computer science has shifted from formal logic coding to tuning massive datasets and models.
    • Traditional software engineering is not dead: Engineers who understand computer architecture and “leaky abstractions” are now the most leveraged people on earth.
    • There is no demand for average: The AI economy is a winner-takes-all market. The best app will dominate, while millions of hyper-niche apps will fill the long tail.
    • Entrepreneurs have nothing to fear: Because entrepreneurs exercise self-directed, extreme agency to solve unknown problems, AI acts as a springboard, not a replacement.
    • AI fails the true test of intelligence: Intelligence is getting what you want out of life. Because AI lacks biological desires, survival instincts, and agency, it is not “alive.”
    • AI is the ultimate autodidact tool: It can meet you at your exact level of comprehension, eliminating the friction of learning complex concepts.
    • Action cures anxiety: The antidote to AI fear is curiosity. Understanding how the technology works demystifies it and reveals its practical utility.

    Detailed Summary

    The Rise of Vibe Coding

    The paradigm of programming has experienced a massive leap. With tools like Claude Code, English has become the hottest new programming language. This enables “vibe coding”—a process where non-technical product managers, creatives, and former coders can spin up complete, working applications simply by describing what they want. You can iterate, debug, and refine through conversation. Because AI is adapting to human communication faster than humans are adapting to AI, there is no need to learn esoteric prompt engineering tricks. Simply speaking clearly and logically is enough to direct the machine.

    The Death of Average and the Extreme App Store

    As the barrier to creating software drops to zero, a tsunami of new applications will flood the market. In this environment of infinite supply, there is absolutely zero demand for average. The market will bifurcate entirely. At the very top, massive aggregators and the absolute best-in-class apps will consolidate power and encompass more use cases. At the bottom, a massive long tail of hyper-specific, niche apps will flourish—apps designed for a single user’s highly specific workflow or hobby. The casualty of this shift will be the medium-sized, 10-to-20-person software firms that currently build average enterprise tools, as their work can now be vibe-coded away.

    Why Traditional Software Engineers Still Have the Edge

    Despite the democratization of coding, traditional software engineering remains critical. AI operates on abstractions, and all abstractions eventually leak. When an AI writes suboptimal architecture or creates a complex bug, the engineer who understands the underlying code, hardware, and logic gates can step in to fix it. Furthermore, traditional engineers are required for high-performance computing, novel hardware architectures, and solving problems that fall outside of an AI’s existing training data distribution. Today, a skilled software engineer armed with AI tools is effectively 10x to 100x more productive.

    Entrepreneurs and Extreme Agency

    A common fear is that AI will replace jobs, but no true entrepreneur is worried about AI taking their role. An entrepreneur’s function is the antithesis of a standard job; they operate in unknown domains with “extreme agency” to bring something entirely new into the world. AI lacks its own desires, creativity, and self-directed goals. It cannot be an entrepreneur. Instead, it serves as a tireless ally to those who possess agency, acting as a springboard that allows creators, scientists, and founders to jump to unprecedented heights.

    Is AI Alive? The Philosophy of Intelligence

    The conversation around Artificial General Intelligence (AGI) often strays into whether the machine is “alive.” AI is currently an incredible imitation engine and a masterful data compressor, but it is not alive. It is not embodied in the physical world, it lacks a survival instinct, and it has no biological drive to replicate. Furthermore, if the true test of intelligence is the ability to navigate the world to get what you want out of life, AI fails instantly. It wants nothing. Any goal an AI pursues is simply a proxy for the desires of the human turning the crank.

    The Ultimate Tutor

    One of the most profound immediate use cases for AI is in education. AI is a patient, egoless tutor that can explain complex concepts—from quantum physics to ordinal numbers—at the exact level of the user’s comprehension. By generating diagrams, analogies, and step-by-step breakdowns, AI removes the friction of traditional textbooks. As Naval notes, the means of learning have always been abundant, but AI finally makes those means perfectly tailored to the individual. The only scarce resource left is the desire to learn.

    Action Cures Anxiety

    With the rapid advancement of foundational models, “AI anxiety” has become common. People fear what they do not understand, worrying about a dystopian Skynet scenario or abrupt obsolescence. The solution to this non-specific fear is action. By actively engaging with AI—popping the hood, asking questions, and testing its limitations—users can quickly demystify the technology. Early adopters who lean into their curiosity will discover what the machine can and cannot do, granting them a massive competitive edge in the intelligence age.

    Thoughts

    This discussion highlights a critical pivot in how we value human capital. For decades, technical execution was the bottleneck to innovation. If you had an idea, you had to either learn complex syntax to build it yourself or raise capital to hire a team. AI is completely removing the execution bottleneck. When execution becomes commoditized, the premium shifts entirely to taste, judgment, extreme agency, and logical thinking. We are entering an era where anyone can be a “spellcaster.” The winners in this new economy won’t necessarily be the ones who can write the best functions, but rather the ones who can ask the best questions and hold the most uncompromising vision for what they want to see exist in the world.

  • The Rise of the Modern Sovereign: How Naval Ravikant and Patrick Williamson Explore Wealth, Independence, and the Power of the Internet

    TL;DW of the Naval Ravikant & Patrick Williamson Conversation:

    Naval and Williamson dive deep into what it means to live a sovereign life—a life defined by personal freedom, not societal scripts. They argue that the internet has unlocked permissionless opportunity, letting anyone build wealth, reputation, and independence without traditional institutions.

    Key ideas:

    • Sovereignty is being independent—financially, intellectually, emotionally.
    • Wealth ≠ money: true wealth means owning assets that work for you and give you time freedom.
    • The internet is the ultimate leverage, enabling anyone to scale themselves globally.
    • Traditional success (status, credentials) is outdated; real success is living life on your terms.
    • Health and peace of mind are essential foundations for freedom.
    • You escape the rat race by building or owning something, not by chasing jobs or status.

    In short: be intentional, own your time, build leverage, ignore the herd.

    Naval Ravikant, the entrepreneur and philosopher behind AngelList, sat down with Chris Williamson, host of the Modern Wisdom podcast, for a three-hour exploration of what it means to live a life of sovereignty in the modern age. Their conversation is a masterclass in rethinking success, wealth, and personal freedom—blending timeless wisdom with cutting-edge insights about the internet, human nature, and the pursuit of happiness. Far from a dry lecture, it’s a dynamic exchange filled with Naval’s signature clarity and Chris’s probing curiosity, offering a roadmap for anyone seeking to escape the herd and design a life on their own terms.

    1. Sovereignty: The Ultimate Prize

    Naval kicks off by reframing the idea of success not as a trophy case of accolades but as sovereignty—a state of independence that spans financial, intellectual, and emotional realms. “Sovereignty is about being free of the game,” he says, echoing his famous quip, “The reason to win the game is to be free of it.” To him, this means owning your time, your decisions, and your peace of mind, unbound by societal scripts or external validation.

    Chris pushes back, asking how one achieves this in a world that constantly demands conformity. Naval’s response is characteristically blunt: “You stop caring about what doesn’t matter. Most people are wasting their lives on status games—fame, likes, approval—that don’t cash out anywhere real.” Sovereignty, then, begins with a radical act of prioritization: deciding what’s worth your attention and letting the rest fall away.

    2. The Internet: A Revolution of Permissionless Power

    If sovereignty is the goal, the internet is the tool. Naval describes it as the ultimate lever for the individual, a “permissionless opportunity” that obliterates traditional gatekeepers. “You don’t need a degree, a boss, or a bank loan anymore,” he asserts. “You can learn anything, build anything, reach anyone—all from a laptop.”

    Chris amplifies this, noting how the internet has shifted leverage from institutions to individuals. “It’s not just about access,” he says. “It’s about scale. One person can now influence millions without a middleman.” Naval nods, adding that this shift is why old metrics of success—titles, credentials, corner offices—are crumbling. The new currency is what you create and how you distribute it.

    This isn’t abstract theory. Naval points to his own life—building AngelList, tweeting insights that resonate globally—as proof that the internet rewards those who seize its potential. “Productize yourself,” he advises. “Find what you do naturally, turn it into something scalable, and let the world find you.”

    3. Wealth Redefined: Beyond Money to Time

    Naval’s distinction between wealth, money, and status is a cornerstone of the discussion. “Money is how we transfer time and wealth,” he explains. “Status is a zero-sum game—someone wins, someone loses. But wealth? Wealth is assets that work for you while you sleep. That’s freedom.”

    Chris latches onto this, reflecting on how society fixates on money as the endgame. “We’re taught to grind for a paycheck,” he says, “but you’re saying the real win is owning something that compounds.” Naval agrees: “If you’re trading time for money, you’re still in the rat race. Wealth is about decoupling your effort from your reward.”

    Time, not money, emerges as the true measure of wealth. “Attention is the real currency of life,” Naval insists. “Money can’t buy you more hours, but it can buy you control over the ones you have.” This resonates deeply with Chris, who admits to once being trapped in a cycle of chasing dopamine hits—likes, views, applause—only to realize they left him empty.

    4. Dismantling the Old Success Myth

    The conversation takes a sharp turn as Naval dismantles the traditional success narrative. “The idea that you work 40 years to retire at 65 with a gold watch is a scam,” he says. “Why sacrifice now for a ‘someday’ that might never come?” Chris chuckles, recalling his own shift from a corporate path to podcasting—a move that felt risky but aligned with his authentic self.

    Naval doubles down, critiquing credentials as outdated proxies. “They’re just signals,” he says. “Today, you can signal trust directly—through what you build, what you say, how you show up.” He cites Elon Musk as an example: a man who bets on himself repeatedly, unburdened by pride or fear of failure, and wins by creating value at scale.

    For Naval, the old game—status, hierarchies, climbing ladders—is a trap. “Status is limited,” he explains. “Wealth is infinite. Focus on creating, not competing.” Chris ties this to his own journey, noting how shedding societal expectations freed him to pursue what truly mattered.

    5. The Bedrock of Freedom: Health and Peace

    Sovereignty isn’t just about money or leverage—it’s about the foundation beneath it. Naval stresses that health and peace of mind are non-negotiable. “You can’t be free if you’re sick or distracted,” he says. His recipe? Sleep well, move your body, meditate, and guard your attention fiercely. “A low-information diet is as important as a good diet,” he quips.

    Chris shares his own evolution, admitting that detaching from social media’s pull was a game-changer. “I used to check my phone obsessively,” he says. “Now I see it as a thief of focus.” Naval nods, adding, “The news drowns you in emergencies you can’t fix. Pick what you care about—something you can actually move—and let the rest go.”

    This emphasis on mental clarity ties back to happiness, which Naval sees as a choice. “Happiness isn’t the absence of problems,” he says. “It’s deciding to enjoy the journey, not just the destination.” Chris recalls a story Naval shares about a man in Thailand who chose to be “the happiest person in the world.” “Why not me?” Naval muses. “It’s a frame worth stealing.”

    6. Leverage: The Escape Hatch from the Rat Race

    Naval’s philosophy of leverage—using code, media, and systems to multiply your impact—takes center stage. “The old way was trading hours for dollars,” he says. “The new way is building something once and letting it pay forever.” Think software, content, or equity in a business—assets that scale without your constant input.

    Chris connects this to his podcasting career. “I record an episode once, and it reaches people for years,” he says. “That’s leverage.” Naval smiles, noting, “You’ve escaped competition through authenticity. No one can out-Chris you at being Chris.”

    The key, Naval argues, is ownership. “Don’t just work for someone else’s dream,” he says. “Build or own something—a product, a platform, a stake. That’s how you stop running on the treadmill.” For those stuck in jobs, he suggests a gradual shift: learn skills, create side projects, and transition to a life where your outputs outlast your inputs.

    7. A Call to Intentional Living

    As the conversation winds down, Naval and Chris distill their insights into a clarion call: live intentionally. “Most people drift,” Naval says. “They let others—bosses, culture, algorithms—steer their ship. Sovereignty is taking the wheel.” Chris agrees, emphasizing that this isn’t about instant transformation but persistent experimentation. “Try things, kill what doesn’t work, double down on what does,” he advises.

    Naval’s parting wisdom is both simple and profound: “Expect nothing. Define your own game. Play it well.” For him, the sovereign life isn’t about amassing trophies but crafting a story you’re proud to tell—one of freedom, impact, and peace.

    The Bigger Picture

    What makes this dialogue stand out is its blend of practicality and philosophy. Naval doesn’t just preach; he dissects—breaking down complex ideas into actionable truths. Chris, meanwhile, grounds it with his own lived experience, making it relatable to anyone who’s ever felt trapped by the system.

    Their message is clear: the tools for sovereignty are here—internet access, knowledge, leverage—but the mindset shift is up to you. In an era of noise and distraction, they offer a quiet rebellion: ignore the herd, own your time, build your future. It’s not just a conversation—it’s a blueprint for the modern sovereign.

  • 🤯 Naval Ravikant Just DESTROYED Conventional Thinking! (And It’s All Thanks to THIS Physicist) 🤯

    Naval Ravikant and Arjun Khemani discuss David Deutsch’s ideas, emphasizing the importance of seeking explanations, critical thinking, and creativity. They criticize the slowdown in scientific progress and warn against censorship, centralization, and the erosion of individual freedoms. Ravikant controversially links societal structures to violence, highlighting the need for individual rights. The discussion champions knowledge, technological advancement, and open inquiry as crucial for progress.

    Forget everything you thought you knew about knowledge, progress, and reality itself.

    In a mind-blowing new interview, tech investor and philosopher Naval Ravikant dives deep into the groundbreaking ideas of physicist David Deutsch, author of “The Beginning of Infinity.” Prepare to have your worldview shattered as they explore these key concepts:

    The REAL reason science is slowing down: Ravikant challenges the notion that we’ve simply picked all the “low-hanging fruit” in science. He argues that the slowdown is due to systemic issues like groupthink in academia, over-reliance on expensive equipment, suppression of unorthodox ideas, and bureaucratic hurdles. He calls for a return to bold conjecture and creative problem-solving, echoing Deutsch’s emphasis on the importance of generating new explanations.

    The 4 pillars of reality: Deutsch proposes four fundamental theories that form the basis of our understanding of the world: epistemology (how we know what we know), evolution by natural selection, quantum theory, and computation. These interconnected strands offer a comprehensive framework for understanding reality and highlight the importance of critical thinking and the pursuit of better explanations.  

    Why “knowledge” is like a crystal: Ravikant uses the analogy of a crystal to illustrate the interconnected nature of knowledge. Just as a crystal has a specific structure with each atom connected to others, knowledge is not simply a collection of facts but a network of interconnected ideas. This highlights the importance of creativity in generating new knowledge and making connections between seemingly disparate concepts.

    The SHOCKING truth about violence and society: In a controversial statement, Ravikant argues that all societies are ultimately structured around the ability to do violence. He claims that those who control the means of violence ultimately hold power. This underscores the importance of individual rights, self-defense, and decentralization of power to prevent tyranny.

    How to protect yourself from the REAL threats to freedom: Ravikant identifies censorship, centralization of power, and the erosion of individual freedoms as the biggest threats to Western civilization. He warns against the dangers of collectivism and emphasizes the importance of free speech, decentralized technologies (like cryptography and personal computing), and the right to bear arms as safeguards against these threats.

    This is NOT your typical interview. Ravikant and Khemani engage in a deep and thought-provoking conversation that challenges conventional wisdom and encourages viewers to think critically about the world around them.

  • Naval Ravikant and Scott Adams Discuss Power, Politics, and Philosophy: Key Takeaways on Influence, AI, and the Future of Society

    TL;DR / TL;DW
    Naval Ravikant and Scott Adams explore the intersection of politics, influence, and technology, discussing societal structures, power dynamics, simulation theory, AI, and the evolving roles of family and identity in modern society. They highlight Elon Musk’s impact and examine the philosophical implications of consciousness and personal legacy in a tech-driven world.

    Key Discussion Points: Political Influence and Media Power

    One major thread in the conversation is how political ideologies operate in today’s climate. Ravikant identifies the left as a coalition of groups aligned toward equal outcomes, often rooted in Marxism, race, and identity politics. He argues that the right, by contrast, consists of individuals who value independence and freedom from government interference. Ravikant notes that the right is fragmented, encompassing fiscal conservatives, cultural conservatives, and religious traditionalists who unite only through a shared opposition to the left’s vision.

    Both speakers agree that social platforms, especially Twitter, play a critical role in amplifying influence, noting that platforms punch above their weight because they reach influential figures in media and politics. Ravikant specifically mentions Elon Musk’s takeover of Twitter (now called X) as a transformative moment, one he refers to as a “Death Star” move for media freedom.

    The Role of Influencers in Shaping Society

    Ravikant and Adams explore the concept of “influencers of influencers,” citing Tim Ferriss and Joe Rogan as people whose reach extends to other influencers, creating ripples across public thought and opinion. They reflect on Musk’s rise as an influential figure, crediting him with shifting societal perspectives on everything from climate change to space exploration. Adams and Ravikant marvel at Musk’s capacity to live as though he’s in a simulation, pushing boundaries and pursuing audacious goals like Mars colonization. Ravikant sees Musk’s ambition not only as a personal quest but as a bold move to shape the future, interpreting Musk’s goals as a form of “planetary conquest.”

    Philosophy, Simulation, and the Nature of Reality

    The conversation takes a philosophical turn as Adams and Ravikant examine the simulation hypothesis, a theory suggesting that reality could be an artificial simulation. Adams, an advocate for the theory, shares personal anecdotes that support his perspective, suggesting that many strange occurrences in his life seem orchestrated by an external programmer. Ravikant, however, is skeptical, challenging the theory’s lack of scientific basis and calling it unfalsifiable. He argues that simulation theory merely shifts the question of existence one layer up, akin to religious belief, and fails to provide actionable insights.

    Ravikant also highlights the importance of epistemology—the study of knowledge—and emphasizes that understanding how to distinguish between truth and falsehood has become a vital survival skill in an era of information overload. He believes that most people lack the tools to critically assess claims, often succumbing to conspiracy theories or pseudoscience.

    AI, Consciousness, and Humanity’s Technological Future

    In an exchange about artificial intelligence and its trajectory, the two discuss whether large language models (LLMs) like ChatGPT could ever attain human-like consciousness. Ravikant expresses doubt, positing that AI is unlikely to reach the complexity of genuine consciousness but acknowledging its potential in transforming industries. He emphasizes that AI is still far from achieving creativity and adaptability comparable to human beings. Ravikant argues that AI-driven advancements are bounded by human-defined parameters and are currently effective in areas with clear boundaries, such as self-driving technology, translation, and data analysis.

    On the subject of personal legacy, Adams shares his long-term plan to create a robotic version of himself that could continue his work and thoughts posthumously. This leads them to discuss the ethical and philosophical implications of cloning, consciousness transfer, and personal identity—topics with significant relevance as technology advances in these fields.

    The Evolution of Family Structures and Societal Norms

    Their discussion also touches on evolving family dynamics, where Ravikant notes that contraception and technology have decoupled sex, marriage, and child-rearing, creating new norms. He suggests that while the traditional family structure remains ideal for many, societal changes have made alternative family configurations increasingly common. Ravikant shares a unique story of a divorced couple choosing to have a second child together, even after separation, because of mutual compatibility and existing familial bonds—a scenario that would have been considered highly unconventional in past generations.

    Closing Thoughts on Society and the Role of Free Speech

    Adams and Ravikant contemplate the role of free speech in sustaining a functional democracy. Ravikant points out that while free speech can lead to divisiveness, it’s essential for ensuring accountability and facilitating peaceful change. Without open communication, he argues, democracy would be compromised, leading to unrest and instability. Ravikant credits Musk’s takeover of Twitter as a major win for free speech, emphasizing that open discourse is essential in a world increasingly governed by algorithms and censorship.

    Their conversation concludes with a reflection on modern society’s challenges and opportunities, emphasizing the need for resilient systems that can withstand political and technological shifts. Both see potential in the current moment, likening it to a new era of revolutionary change with the rise of tech giants, renewed political fervor, and the continual questioning of traditional norms. Ravikant and Adams ultimately share a hopeful outlook, believing that forward-thinking individuals have the power to shape a more balanced and resilient future.

    This exchange between Ravikant and Adams showcases two influential minds dissecting the most pressing and nuanced issues of our time. It is a reminder that, amidst rapid technological progress and shifting societal structures, thoughtful discourse remains invaluable in understanding and navigating our evolving world.

    Summary:

    In a deep and wide-ranging conversation, Naval Ravikant and Scott Adams cover various topics surrounding politics, influence, and modern society. Ravikant analyzes the ideological divide between the political left and right, describing the left as an organized movement focused on equality, while the right is a fragmented collection of individualists. They discuss how influential figures, like Tim Ferriss and Elon Musk, shape discourse by influencing other influencers, creating ripple effects across society. Ravikant and Adams especially focus on Musk, whom they regard as a transformative figure pushing boundaries in areas like space exploration, electric cars, and media through his acquisition of Twitter.

    Philosophical topics also arise, particularly around simulation theory and consciousness. Adams supports the idea that reality may be a simulation, sharing personal anecdotes as evidence, while Ravikant challenges this view as unfalsifiable and akin to faith. They discuss the nature of consciousness and speculate on whether AI can achieve it, with Ravikant expressing doubts about AI reaching human-level creativity or true self-awareness.

    The discussion then shifts to the future of family structures, where Ravikant suggests that technology and societal changes have made alternative family arrangements more common. He shares a story about a couple having children post-divorce as an example of how norms are evolving. They conclude by discussing free speech and the role of platforms like Twitter in promoting open discourse. Ravikant praises Musk’s impact on media freedom, suggesting that free speech is crucial for a stable democracy, even if it creates societal tensions.

    Ultimately, the dialogue offers a comprehensive look at how power, technology, and personal philosophy influence society and individual lives, highlighting both the challenges and the potential for positive change in the current era.

  • Naval Ravikant and Niklas Anzinger Discuss Optimism for the Future with AI and Technological Progress

    This video is a discussion between Naval Ravikant and Niklas Anzinger, focusing on the optimistic outlook towards the future propelled by AI and technological advancements. The conversation was part of an event in Vitalia City, aimed at fostering the development of a city dedicated to advancing life extension technologies. Here are the key points and a summary of their dialogue:

    1. Optimism About the Future: Naval Ravikant expresses a strong optimism for the future, grounded in the belief that technology democratizes the power of creation, enabling individuals to become innovators, entrepreneurs, and scientists.
    2. The Legacy of the Enlightenment: The discussion credits the enlightenment era for setting the foundations of scientific discovery and innovation. It highlights the importance of error correction and the unlimited potential of human creativity when supported by freedom of thought and expression.
    3. Freedom as a Catalyst for Innovation: The conversation emphasizes that freedom is crucial for innovation. Examples include Próspera ZEDE, providing a novel legal framework aimed at accelerating biotech startups by offering a more liberal regulatory environment.
    4. Challenges of Regulatory Environments: The regulatory hurdles, especially in the healthcare sector, are discussed as significant barriers to innovation. The dialogue suggests that less restrictive frameworks could unleash entrepreneurial energy and technological advancements.
    5. Impact of Technological Progress: The overarching theme is that technological progress, when coupled with entrepreneurial spirit and less restrictive regulations, can lead to significant improvements in quality of life and accelerate advancements in critical fields like healthcare.
    6. The Role of AI and Technological Progress: AI is seen as a pivotal force in shaping a brighter future, with the potential to solve complex problems, enhance creativity, and drive unprecedented progress across various domains.

    The discussion between Naval Ravikant and Niklas Anzinger at the Vitalia City event centers on a hopeful vision of the future, underpinned by the belief in human creativity, the power of technology to solve pressing challenges, and the essential role of freedom in fostering innovation. They argue that despite the human tendency to focus on potential downsides, the capacity for scientific discovery and technological progress presents compelling reasons for optimism.

  • Naval Ravikant’s Reading Strategies

    This article was inspired by this Tweet:

    Renowned investor and thinker Naval Ravikant attributes his remarkable success to a simple yet powerful habit: reading for 1-2 hours every day. This dedication to reading has not only shaped his worldview but also contributed significantly to his professional achievements. In a recent compilation of insights, Ravikant shares 43 invaluable reading tips, offering a glimpse into the mindset that has propelled him to the forefront of success and innovation.

    1. Embrace Reading for Pleasure: Ravikant advocates for reading materials that genuinely interest you, as this nurtures a love for reading itself.
    2. Explore Controversial Literature: He encourages delving into books that face opposition or banning, suggesting these often hold significant insights.
    3. Quality over Speed: He emphasizes the importance of absorbing quality literature slowly and thoughtfully.
    4. Investing in Knowledge: Ravikant regards spending on books not as an expense but as a crucial investment.
    5. Revisiting Great Works: He advises re-reading and even re-buying books that have a lasting impact.
    6. Intelligent Reading: As one’s understanding deepens, reading becomes a slower, more thoughtful process.
    7. Depth over Brevity: Books that can be speed-read, he asserts, are likely not worth the time.
    8. Reading as a Fundamental Skill: He views reading as the ultimate skill that can open doors to endless knowledge and opportunities.
    9. Reading as a Vacation: Ravikant finds reading to be a fulfilling and peaceful way to spend one’s leisure time.
    10. Restful Reading vs. Audio Learning: He differentiates between the efficiency of reading in stillness and learning through audiobooks while in motion.

    Ravikant’s tips continue, covering a broad spectrum of advice that underscores the transformative power of reading. From advocating for self-directed learning to challenging oneself with complex texts, his insights reflect a deep appreciation for the written word and its capacity to enrich one’s life and mind. His approach to reading is not just as a pastime, but as a strategic tool for personal growth and intellectual development.

    Naval Ravikant’s reading tips are a testament to the profound impact that a dedicated reading habit can have on an individual’s success and intellectual growth. His advice spans from choosing engaging literature to viewing reading as a key investment in one’s future, offering a comprehensive guide for anyone looking to enhance their knowledge and thinking through the power of books.