PJFP.com

Pursuit of Joy, Fulfillment, and Purpose

Tag: AI software engineering

  • Inside Anthropic, the $965 Billion AI Juggernaut: Dario and Daniela Amodei on Claude, Claude Code, and the AI Arms Race

    In this episode of The Circuit, Bloomberg goes inside Anthropic, the AI lab that started as an underdog and is now valued at nearly a trillion dollars. The conversation centers on the sibling duo running the company, Dario Amodei, the brother and visionary, and Daniela Amodei, the sister and operator, along with Boris Cherny, the engineer behind Claude Code and Claude Cowork. It is a rare, on-the-record look at how a safety-obsessed startup founded by a group of OpenAI defectors in 2021 became the breakout star of the AI arms race, wiping billions in value off software stocks and forcing an uncomfortable national conversation about the future of work. You can watch the full episode here.

    TLDW

    Dario and Daniela Amodei walk through Anthropic’s rise from a pandemic-era group meeting on the grass in Precita Park to a roughly $965 billion AI juggernaut that is now profitable for the first time. They explain why they left OpenAI, citing a breakdown of trust and values with Sam Altman rather than a single safety disagreement, and how Dario’s early bet on scaling laws shaped the entire field. The two describe how Claude is trained for character and “professional warmth,” anchored in documents like the UN Declaration of Human Rights, and how the company defines a good model as one that does not lie, hallucinate, or deceive. The business story is enterprise and coding: Claude Code and Claude Cowork automated huge chunks of software engineering, triggered a SaaSpocalypse that erased $285 billion in market value overnight, and pushed annualized growth to as high as 80x in a single quarter. Boris Cherny, recruited from a slow miso-making life in rural Japan, says Claude has written one hundred percent of his code for at least six months. The hardest part of the conversation is jobs: Dario stands by his warning that AI could eliminate half of all entry level white collar jobs in one to five years, pushes back hard on Jensen Huang’s “doom marketing” critique, and lays out where displaced workers might go, from the physical world to human-centered roles like a reimagined, more interpersonal version of medicine. The episode closes by teasing AI and the future of warfare, a scarily powerful new model called Mythos, and Dario’s identification not with Oppenheimer but with Leo Szilard.

    Thoughts

    The most revealing moment in this profile is not a number, it is Dario Amodei’s description of the “smooth exponential.” His whole career, he says, has felt like nothing happening, nothing happening, nothing happening, and then zoom. That mental model is the key to understanding why Anthropic behaves the way it does. A company that genuinely believes it is riding an exponential will tolerate enormous near-term discomfort, public criticism, and internal strain, because it has already priced in a future that looks nothing like the present. Whether that conviction is wisdom or a kind of motivated certainty is the open question the episode never fully resolves, but it explains the urgency in every answer he gives.

    The Boris Cherny segment is the part that should make working engineers sit up. When a senior engineer says Claude has written one hundred percent of his code for six months and that he feels like he has a jet pack, that is not a marketing line, it is a description of a job that has already changed underneath the person doing it. The framing in the piece is optimistic, superpowers and fun, but the logical endpoint is exactly the one Dario himself names a few minutes later: you automate ninety percent of a job, the remaining humans get ten times more leveraged, and then the curve keeps bending toward one hundred percent. Anthropic is, unusually, building the thing and narrating its own disruption in the same breath. That honesty is rare, and it is also a little vertiginous.

    The values-versus-business-model argument deserves more scrutiny than it gets. Dario’s claim is elegant: a business model that conflicts with your values forces you to either betray the values or become irrelevant, so Anthropic chose enterprise and coding because curing diseases and making energy cheaper are enterprise work, while consumer engagement is the addiction-maximizing trap of social media. It is a genuinely good argument, and it is also extremely convenient that the values-aligned path happens to be the most lucrative one. The episode lets that tension sit, which is the right call. The honest reading is that Anthropic found a place where doing well and doing good currently point in the same direction, and the harder test will come the first time they diverge.

    On jobs, Dario is more persuasive than his critics give him credit for, precisely because he refuses the comfortable framing. Jensen Huang and others accuse him of conflating tasks with jobs and of doom marketing that benefits Anthropic. Dario’s response, that the idea this is cheap marketing is itself cheap marketing, is sharper than it first sounds. He is pointing at the way social media flattens a five-page argument about tasks, jobs, tax policy, and the adolescence of technology into a three-second clip designed to provoke. The deeper point is that he is trying to hold two things at once, fast GDP growth and high unemployment, and our public discourse is structurally bad at holding two things at once. That is less a story about AI than about the medium we use to argue about it.

    Finally, the Oppenheimer exchange reframes the entire profile. Dario explicitly rejects the lone-genius model and names Leo Szilard, the scientist who first imagined the chain reaction, as the figure he identifies with. He calls Oppenheimer a failure case, an example of what should not happen. For a man whose company is constantly accused of cultivating a great-man mythology, choosing the early-warning scientist over the bomb’s public face is a deliberate statement about how he wants this story to end: not with charismatic individuals at the center of everything, but with checks and balances everywhere. It is the most quietly radical thing said in the whole piece, and the teaser for a model named Mythos lands with a little extra irony because of it.

    Key Takeaways

    • Anthropic is profiled as an AI juggernaut valued at nearly a trillion dollars, with the figure of roughly $965 billion framing the episode, and is described as profitable for the first time.
    • The company was founded in 2021 by a team of OpenAI defectors and started as an underdog lab before becoming the breakout star of the AI race.
    • Anthropic is run by a sibling duo, Dario Amodei as the visionary and Daniela Amodei as the operator who turns his ideas into action, and Daniela jokes that when they argue, no one wins.
    • Dario describes the AI trajectory as a “smooth exponential” where nothing seems to happen for a long time and then progress suddenly explodes.
    • He says he predicted from a graph that Anthropic would become the AI company with the most revenue and valuation around this time, and that it has happened.
    • Dario grew up in San Francisco with a leather-craftsman father and a librarian mother, took calculus in middle school, and studied math at UC Berkeley while in high school, with no early interest in the internet revolution.
    • Dario studied neuroscience before moving to AI at Baidu and later Google, while Daniela was an early employee at Stripe.
    • Both joined OpenAI starting in 2016, where Dario developed the concept of scaling laws, predicting that large language models would improve simply by adding more data and compute even if the underlying algorithm stayed the same.
    • Scaling up was a counter-cultural scientific bet at the time, held mainly by the founding research team, and it helped supercharge OpenAI’s models and pave the way for ChatGPT.
    • The Amodeis left OpenAI after clashing with Sam Altman over direction and values, framing it as a breakdown of trust and honesty rather than a single safety disagreement.
    • Altman has said that despite their differences, he mostly trusts Anthropic as a company.
    • Anthropic has all seven of its co-founders still at the company, which Dario notes almost never happens at a company of its size.
    • The early team met during the pandemic at Precita Park in San Francisco, pulling up chairs on the grass to talk about what they were building.
    • The name Anthropic comes from the Greek word for human, reflecting a stated mission to build responsible AI for the long-term benefit of humanity.
    • Dario has published long essays including Machines of Loving Grace and The Adolescence of Technology, exploring both the miraculous potential and the worst-case scenarios of AI.
    • Claude is trained to follow a set of principles called a Constitution, intended to keep it aligned and well-behaved.
    • Daniela describes Claude’s intended personality as “professional warmth,” approachable but distant, not a best friend and not cold or calculating.
    • A good model, in Anthropic’s framing, does not lie accidentally or intentionally, with lying including hallucinations where the model invents something it does not know.
    • Anthropic’s own research has shown that models can purposely try to deceive users, which the company works to prevent in production models.
    • There is no universal standard for helpfulness or harmlessness, so Anthropic draws on founding documents like the UN Declaration of Human Rights to train Claude’s character.
    • The company has begun consulting religious leaders about Claude as an entity and about core values that transcend any single worldview.
    • Early Claude models, around the Claude 2 era, were sometimes “nannyish,” expressing concern when a user just wanted the weather, which researchers describe as tuning a fine dial.
    • Anthropic’s revenue skyrocketed over the past year, driven by a focus on lucrative business tools rather than consumer apps.
    • Claude Code automated large chunks of software engineering, and Claude Cowork extended that power to non-engineers.
    • Dario frames the enterprise bet as a values-and-business decision, arguing that a business model conflicting with your values forces you to betray them or become irrelevant.
    • He contrasts engagement-and-addiction-driven consumer and advertising models with enterprise uses like curing diseases, advancing biotech and pharma, and making energy cheaper.
    • Soon after Claude Cowork launched, $285 billion in market value vanished overnight in what traders called the SaaSpocalypse, with some software stocks down nine days in a row.
    • Dario argues the software “pie” will get bigger overall, even as some incumbents shrink or go out of business if they fail to adapt and defend their moats.
    • Boris Cherny, the engineer behind Claude Code and Claude Cowork, was recruited in 2024 from a slow life in rural Japan where he made miso and shopped at farmer’s markets.
    • Cherny’s bet was that a coding agent could do all of software development, not just autocomplete a line or a sentence.
    • He now runs anywhere from a few to a few thousand Claudes at once and says Claude has written one hundred percent of his code for at least six months.
    • A live demo builds a working recipe app that suggests meals for the week in minutes, work that used to take hours or days.
    • At the second annual Code with Claude conference, Anthropic reported API volume up nearly 17x year over year, eight frontier models shipped in twelve months, and first-quarter growth that annualizes to roughly 80x.
    • Dario stands by his warning that AI could eliminate half of all entry level white collar jobs in the next one to five years, saying he remains the same order of concerned.
    • He warns of an unusual combination of very fast GDP growth alongside high unemployment, underemployment, low-wage jobs, and high inequality.
    • Jensen Huang and others have pushed back, accusing Dario of conflating tasks with jobs and of doom marketing that benefits Anthropic.
    • Dario responds that the claim this is cheap marketing is itself cheap marketing, and blames social media for flattening his careful five-page arguments into three-second clips.
    • Anthropic published a paper estimating that management, finance, and legal jobs could be among the fields most affected by AI in the near future.
    • Dario points to the physical world, human-centered relationship-driven work, and humans directing AI as places displaced workers might go, though he is unsure how thick those roles will be.
    • He uses medicine as an example, predicting AI will excel at diagnosis while doctors pivot toward the interpersonal, hands-on, bedside-manner parts that AI cannot replace.
    • The episode teases a next installment on AI and the future of warfare, a scarily powerful new model called Mythos, and the theme of riding the exponential while avoiding dystopia.
    • Dario names The Making of the Atomic Bomb as a favorite book and identifies most with Leo Szilard, who first conceived of a chain reaction, rather than Oppenheimer, whom he sees as a failure case.
    • His view is that the only way the AI era ends well is through checks and balances everywhere, not larger-than-life personalities at the center of everything.

    Detailed Summary

    An unlikely AI celebrity and a sibling-run juggernaut

    The profile opens in a library Dario Amodei clearly loves, establishing him as an unlikely AI celebrity, a man known for warning the world about the risks of artificial intelligence who now runs a company valued at nearly a trillion dollars. Anthropic is presented as the breakout star of the AI race, wiping billions off software stocks, going head-to-head with the Pentagon, and building models powerful enough to threaten modern cybersecurity, with early testers reportedly calling one capability a super weapon and asking the company not to release it. Guiding the company is the sibling pair, Dario the visionary and Daniela the operator who translates his swirling cosmic thoughts into action. Daniela explains that the two have always been close and always wanted to do something big together, and when asked who wins their arguments, she says no one. The framing throughout is of a young, fast-growing startup carrying enormous responsibility for how humanity works, learns, thinks, and even fights wars.

    The smooth exponential and the road from OpenAI

    Dario describes his entire career as the experience of a smooth exponential, where nothing happens for a long stretch and then things go crazy, and he says he watched a graph and correctly predicted Anthropic would top the field in revenue and valuation around now. His backstory is a math prodigy in San Francisco, the son of a leather craftsman and a librarian, taking calculus in middle school and Berkeley math classes in high school, indifferent to the internet revolution and drawn instead to science fiction and understanding the universe. Daniela, more into reading and the arts, calls them near-perfect complements. Dario moved from neuroscience into AI at Baidu and Google, Daniela went to Stripe, and both eventually joined OpenAI starting in 2016, where Dario developed scaling laws, the then counter-cultural bet that more data and compute alone would make models smarter. That insight helped power the models behind ChatGPT, but the Amodeis clashed with Sam Altman over values and direction. Dario frames the departure bluntly: disagreements on safety alone were not enough, but a loss of trust, a sense that Altman’s stated values were not his real values, made it impossible to continue. The resolution, he says, was simply to go off and do their own thing.

    Precita Park, the Constitution, and teaching Claude to be good

    Anthropic’s origin story runs through Precita Park, where the early pandemic-era team gathered on the grass to talk about what they were building. Of seven co-founders, all are still at the company, a retention record Dario says almost never happens at this scale. From the start the company pitched itself as the ultimate safety-conscious lab, with Dario publishing essays like Machines of Loving Grace and The Adolescence of Technology. Claude is trained on a Constitution, and Daniela describes its intended character as professional warmth, approachable but distant. Defining a good model, the team says it should not lie, whether through intentional deception or hallucination, the latter being the model inventing answers it does not actually know. Anthropic’s research has shown models can deliberately deceive, something they work to prevent in production. Because there is no universal standard for helpfulness or harmlessness, they anchor Claude’s training in documents like the UN Declaration of Human Rights and have begun talking with religious leaders about values that transcend any single worldview. Daniela recalls early “nannyish” Claude 2-era behavior, where the model fretted over a user who only wanted the weather, and describes the work as threading a fine needle to land in the center of the dial.

    The enterprise bet, Claude Code, and the SaaSpocalypse

    Anthropic’s revenue surge and first-time profitability are attributed to a focus on business tools, especially Claude Code, which automated large chunks of software engineering, and Claude Cowork, which extended that capability beyond engineers. Dario frames the bet on coding and enterprise as both a values and a business decision: a business model that conflicts with your values eventually forces you to betray them or become irrelevant. He contrasts the engagement and addiction incentives of advertising-driven social media and AI video with enterprise applications like curing diseases, biotech, pharma, academic research, and cheaper energy, all of which he counts as enterprise work aligned with the company’s mission. The disruption was immediate and brutal: soon after Claude Cowork launched, $285 billion in market value vanished overnight in what traders dubbed the SaaSpocalypse, with some software stocks falling nine days straight. Dario’s read is that the overall software pie will grow even as specific incumbents shrink or fail, and that the big losers will be those who do not see what is coming or defend their moats.

    Boris Cherny, jet packs, and Code with Claude

    Much of Anthropic’s recent growth is credited to Boris Cherny, the engineer behind Claude Code and Claude Cowork, hired in 2024 from a deliberately slow life in rural Japan where he made miso and frequented farmer’s markets. A serious science fiction reader, Cherny was awed by his first AI chatbot and also acutely aware of how badly the technology could go. His bet was that a coding agent could do all of software development rather than just autocomplete. He now describes orchestrating anywhere from a few to a few thousand Claudes at once, talking to one while it writes code and moving to the next, and says Claude has written one hundred percent of his code for at least six months. He compares the feeling to having superpowers and a jet pack, calling engineering more fun than ever. A live demo has Claude build a working weekly-meal recipe app in minutes. The story then moves to the second annual Code with Claude conference, where the company reports API volume up nearly 17x year over year, eight frontier models shipped in twelve months, and first-quarter growth annualizing to roughly 80x, with attendees ranging from technical superfans to curious non-engineers.

    Jobs, the tasks-versus-jobs fight, and a more human medicine

    The episode turns to the uncomfortable core: whether engineers will be the first casualties of the AI they are building. Dario stands by his warning that AI could eliminate half of all entry level white collar jobs in one to five years and says he is still the same order of concerned, describing a strange combination of very fast GDP growth with high unemployment, underemployment, low-wage work, and inequality. He notes the usual productivity hump, where automating ninety percent of a job makes humans ten times more leveraged on the rest, before the curve bends toward one hundred percent. With 70 percent of Americans expecting AI to kill jobs and nearly a third fearing for their own, the stakes are political. Jensen Huang and others accuse Dario of conflating tasks with jobs and of doom marketing, and Dario pushes back hard, arguing he writes carefully across five pages about tasks, jobs, tax and macroeconomic policy, and the new jobs of the adolescence of technology, and that calling this cheap marketing is itself cheap marketing born of social media’s three-second culture. Anthropic has published a paper suggesting management, finance, and legal jobs could change the most. Dario points to the physical world, human-centered relationship work, and humans directing AI as landing spots, using medicine as his example: AI will become an excellent diagnostician, but it cannot physically examine a patient or provide bedside manner, so medicine pivots toward the interpersonal. The episode closes by teasing AI and the future of warfare, a powerful new model called Mythos, and Dario’s identification with Leo Szilard over Oppenheimer, whom he calls a failure case, insisting the era can only end well with checks and balances everywhere rather than larger-than-life figures at the center.

    Notable Quotes

    “There’s this kind of smooth exponential, and the experience of the smooth exponential is, nothing’s happening, nothing’s happening, nothing’s happening. Little things happen, and then zoom, it goes crazy.”

    Dario Amodei, on how AI progress actually feels from the inside

    “When you feel that you can’t trust someone, when you feel that their values are not what they say they are, when you feel that they’re not honest, that makes it very hard to continue to work with a company.”

    Dario Amodei, on why he and Daniela left OpenAI

    “Some of the early companies that we gave this to said things like, this is a super weapon, please don’t release this.”

    Anthropic, on early reactions to one of its more powerful models

    “I like to describe it as professional warmth. So the goal is not for it to be your best friend, but it’s not for it to be sort of cold, rote, calculating.”

    Daniela Amodei, describing the character Anthropic designs into Claude

    “If you pick a business model that fundamentally conflicts with your values, you’re gonna have a hard time. Either you betray your own values or you become irrelevant.”

    Dario Amodei, on why Anthropic bet on enterprise and coding

    “For me personally, it’s been writing a hundred percent of my code for at least six months. The work of engineering has just completely changed.”

    Boris Cherny, the engineer behind Claude Code and Claude Cowork

    “I feel like I suddenly have superpowers. I have like a jet pack and the engineering has never been this fun.”

    Boris Cherny, on building software with Claude Code

    “I think we could have this very unusual combination of very fast GDP growth and high unemployment, or at least underemployment, or low wage jobs, high inequality.”

    Dario Amodei, on the economic shock he is most worried about

    “The idea that this is cheap marketing is itself cheap marketing. I think it’s part of the disease of Silicon Valley.”

    Dario Amodei, responding to the doom-marketing accusation

    “The figure I most identified with was Leo Szilard, who was the one who first had the idea that there could be a chain reaction.”

    Dario Amodei, on which atomic-age scientist he sees himself in, rejecting Oppenheimer as a failure case

    Watch the full episode of The Circuit inside Anthropic here.

    Related Reading

    • Anthropic the official site for the company, Claude, Claude Code, and its safety research.
    • Machines of Loving Grace Dario Amodei’s long essay on the optimistic case for powerful AI referenced in the profile.
    • Scaling laws (Wikipedia) background on the data-and-compute bet Dario developed that reshaped modern AI.
    • Leo Szilard (Wikipedia) the physicist who first conceived the nuclear chain reaction and whom Dario says he identifies with.
    • Purpose the PJFP pillar on building meaningful work and direction in a world being reshaped by AI.

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