I’ve caught up now, and will try to maintain this going forward—both thanks to Claude Code. If you read this via RSS feed, you might have missed some old posts—you can find them all at https://blog.rootsofprogress.org/writing.

Like everyone else, I’ve gotten addicted to Claude Code. (It happens to be the tool I picked up first, but I’ve heard that OpenAI Codex, Cursor, Replit, etc. are all also quite good.) I’m exactly in the most susceptible demographic for it: a former software engineer, product manager, engineering manager, and tech startup co-founder who through circumstance has not had time to code, even for fun, in several years. In my case, it’s because I became a writer and nonprofit leader, and also a dad; but the same thing is happening to tech CEOs and others. All of us are intoxicated by the amazing newfound productivity of AI coding agents, which are now unlocking years-old backlogs of product ideas, bug fixes, and pet projects.

Let’s step back and recap how we got here. The first GPTs were research prototypes, not yet products. GPT-2, launched in February 2019, struggled to produce coherent, logical text (see examples here). Progress came mainly came from scaling up training runs and model size, from hundreds of millions of parameters for GPT-1 to now hundreds of billions or maybe trillions of parameters in the most capable models.

What this created was not a full artificial intelligence but artificial intuition. It could “answer off the top of its head,” it had a superhuman recall for facts, and it could blurt out not just sentences but entire essays. But it was still blurting out all its answers, with no ability to “think” before “speaking,” check its work, or follow an explicit procedure—not even, say, long addition.

By 2022, this had become such a limitation that it was possible to dramatically improve GPT-3’s performance on mathematical reasoning problems simply by concluding the prompt with “Let’s think step-by-step,” which encouraged models to work through the problem explicitly rather than trying to blurt out an answer. Soon this approach was built into the product, in a new class of “reasoning” models, such as OpenAI’s o1, that were given the ability to “think”—that is, to talk to themselves in a scratchpad—before producing a response.

In parallel, the models’ coding ability was growing. At first, LLMs were built into the IDE (“integrated development environment,” kind of a text editor on steroids that software engineers use to write code), and they took the form of autocomplete: the developer would start to type code, and the LLM would complete it. This made it faster to write many routine functions. Later AI-assisted IDEs could write or modify an entire snippet of code from an English description, or answer questions about the code, or discuss it with the engineer. Then the AI got good enough that you could just tell it what to do next, and the output was reliable enough that you didn’t even really need to review it carefully, at least for low-stakes hobby projects—what Andrej Karpathy dubbed “vibe coding.”

The other thing that developed in parallel was the models’ ability to pursue goals, as autonomous agents. At the core, of course, an LLM is simply a statistical model of text that predicts the next token; since any predictor can be made into a generator, this allows it to take a prompt and generate a response. A text generator is not an agent and does not pursue goals—but it was clear from the beginning how an agent might be built from them. Just provide it with a small scratchpad and a few tools it can invoke. Then tell it a goal, and run it in a loop: given the goal, make a plan to achieve it, execute that plan, then check if the goal was achieved; if not, replan and begin again; continue until you succeed.

Early experiments with this (such as AutoGPT, March 2023) were toys: they didn’t have enough intelligence, large enough context windows, or coherence across long enough timescales to accomplish anything of note. But all of this has been improving. The models have been been trained in better tool use, and have been given tools including web search, file access, and code execution; they’ve been given larger context windows, now up to 1 million tokens; and they have steadily been increasing in long-term coherence. Indeed, the length of task (in human-equivalent minutes) that a model can perform has become a key metric of AI progress:

Put all of this together—the “reasoning” mode, better coding, and greater agency—and by late last year we had crossed a tipping point: Some software developers stopped writing code themselves, and started letting agents write 100% of it. The job of the engineer became planning, identification of tasks, directing the AI to specific goals, possibly giving high-level technical direction, testing the output, and (perhaps, depending on how fastidious you are) reviewing the code that is generated. That is, software engineers are becoming more like product managers, engineering managers, and tech leads—as I predicted, humanity stepping up into management. Andrej Karpathy says the term “vibecoding” no longer does justice to what’s possible: it’s now “agentic engineering.”

I felt this shift personally. In early 2025, I was able to use Cursor to write a Python script to analyze CSVs of my workout logs and make some charts of my exercise performance. AI sped me up a lot, especially since I wasn’t familiar with libraries for processing and charting data (like pandas or Matplotlib). The LLM saved me a lot of time reading docs and tinkering; I could focus on the core task I was trying to accomplish. But I was still directing the coding at a detailed level. By early 2026, I was able to act as the product manager, not the developer: to ask Claude Code to simply implement my ideas. Already I’ve built a personal todo app with web and mobile UIs that works offline; a site uptime monitor for the Roots of Progress’s various websites; and an iPad game for my preschool-age daughter to learn two-digit addition.

Part of why this is such a huge unlock is that writing code demands a level of focus I simply don’t have these days. It requires multi-hour blocks of uninterrupted time where you can get your head deep into the problem and the code. Between my day job, my parenting duties, and the need in my 40s to get regular sleep and exercise, that kind of hobby just isn’t possible. But directing coding agents is a different thing altogether: it can be done on “manager schedule” rather than “maker schedule.” Garry Tan describes it using the metaphor that it’s as if he used to be a competitive runner (i.e., engineer) who got a knee injury (went into management). But now he has a knee replacement (coding agents)—and it’s a bionic knee, better than before. Shopify CEO Tobi Lutke has been coding up a storm, and even used Claude to create a viewer for his MRI data.

Out of the box, coding agents lack training and professional maturity. They’re like junior engineers, very smart but fresh out of college and operating like cowboys. When I started my first app, I suggested to Claude Code that I write a product spec, from which it could create a tech design that I would review, before proceeding to implementation. Oh, that sounds like too much process, it told me, why don’t you just tell me your idea and I’ll whip it up? OK fine, we’ll try it your way, I thought. It worked well at first, but then as these things always do, the app started to get buggy. I soon realized Claude wasn’t even writing automated tests (a very basic practice). Over time, I’ve leveled up my Claudes with best practices from the software world: automated regression tests; “test-driven development,” in which you write the tests before the code to make sure the tests actually catch bugs; doing each change on a separate branch which gets reviewed and tested before it is merged into the main line; creating separate testing environments so as not to interfere with real production data; etc.

At first, I thought I would do this by writing one big practices document and having each agent review that at the beginning of each session. But it turns out there’s a better way: “skills”, which are brief documents describing one procedure or technique. These can range from how to use a particular app framework to general best practices the agent should always follow. Agents like Claude Code are able to ingest a large volume of skills, holding only brief, high-level descriptions of each in their context window, and searching for skills when they might be relevant, so the full text can be brought into context only when needed. People are publishing their skills, and there are entire skills marketplaces. I started with a set of basic engineering practices from Jesse Vincent, and then have been writing my own as I notice things Claude could do better. Well, of course, I haven’t been writing them: I’ve been having Claude draft them, and then I’ve been reviewing and commenting on them. The experience is much like having a highly trainable employee who takes feedback and earnestly attempts to improve.

When I started, I would delegate a task and then do something else for a little while until the agent was finished. But once I had 3–4 agents working in parallel across two or more projects, I found that I was fully occupied just reviewing their work and prioritizing next steps; it took all my focus just to keep them busy. What this means is that I’m now able to make progress on software development at the speed of my own review and decision-making—which is amazing.

Stepping back, I think a lot of progress since ~GPT-3 has been in taking the core intuitive faculty provided by statistical language models and adding layers of self-monitoring and self-control, such as reasoning and skills. I find it remarkable how much LLMs are aided by some of the same practices that help humans be more effective: working problems out on a scratchpad, planning before executing, and all of the structure and practices that human engineers, designers, and product managers put in place around software development. Elsewhere, Wilson Lin at Cursor reports on an experiment with getting a large team of agents to implement a web browser from scratch, a large undertaking (although one for which there is already a comprehensive set of formal specifications and acceptance criteria). Just getting a bunch of agents to work off of one big shared task list was too chaotic. What worked was having certain agents dedicated to planning—assessing status and figuring out what was needed next to reach the goal—while other agents acted as implementers, picking tasks off the plan and getting them done without worrying too much about the big picture. Again, systems of self-monitoring and self-control.

The biggest limitation on these systems right now, it seems to me, is memory. They start each session like Leonard Shelby from Memento, with no short-term memories, needing to review all their notes to get context. This is a very limited form of learning. An LLM can’t develop intuition or taste post-training—which, as Dwarkesh pointed out, means it can’t learn on the job the way a human does. Claude’s memory file generated from our chats is about 400 words, ChatGPT’s is not much over 100; a human assistant who had talked to me as much as they have would have a much deeper understanding of me. No doubt this limitation, too, will be removed sooner or later; I agree with Ethan Mollick when he suggests that this will be transformative.

In any case, to produce an acceptable app right now, even a simple one, requires me to act as the product manager and the tech lead. I’m giving direction about what to do; I’m training the agents in best practices and watching to make sure they follow them; I’m even exercising high-level oversight about technical decisions and making technical suggestions. I’m only capable of this because I spent almost twenty years in the tech world, doing these roles professionally across several teams and projects. I can only imagine that users without that experience would have a hard time creating an app of any size and complexity without getting bogged down in confusing product design, annoying bugs, and slow performance. But on the current trajectory, we’re only a year or so away from whole teams of agents that work together like a complete dev shop. A client could come to the process with only a vague, high-level idea of what they need. A product manager agent would interview them to discover requirements. The PM would write a product spec, and a design agent would create UI mockups, both of which the user could review and comment on. Once the spec and design were approved, an engineering agent would produce a tech design; perhaps a second agent with fresh context would review and revise it. A planner agent would turn it into a task list, and a team of implementer agents would execute the coding tasks in parallel, with reviewer agents examining the code for bugs, weaknesses, and best practices. The app would periodically be presented back to the client for user testing and feedback, for as many rounds of iteration as needed to leave the client fully satisfied. On the whole, it would be much like the process performed by humans, but it would take orders of magnitude less money and time.

This is going to change the nature of software. Already I notice a shift in my product thinking: instead of designing an app for a market, I can design it for myself. I don’t have to worry about any other user’s requirements, about competition and gaps, about user onboarding, or about pricing and payment. It simplifies a lot, compared to being a tech founder. I don’t think all software will be bespoke in the future, not even nearly all of it, but there will be a lot more custom software than before.

And it is not hard at all to envision how this will play out in other industries whose work essentially consists of talking to people and producing documents: law, accounting, graphic design, business consulting. Virtual service shops, doing in hours what used to take weeks, for hundreds of dollars instead of tens of thousands.

It is now impossible not to see that this is going to change the world, indeed that the change has already begun and is underway in earnest.

Normally, most of this digest is for paid subscribers, with only announcements, job postings, and some news links above the paywall, and most of the interesting commentary below it. Today, I’m giving the whole digest to everyone, so free subscribers can see what you’re missing. If you want more of this, or just want to support my work, subscribe:

Contents

• Featured mentors for our high school summer program, Progress in Medicine
• From Progress Conference 2025
• Progress for progressives
• Announcements from RPI fellows
• California Forever petition
• Jobs
• Fellowships
• Queries
• Frontier lab announcements
• Fundraising announcements
• Elon interviewed by Dwarkesh and John Collison

Normally for paid subscribers, free today:

• People have feelings about AI
• AI has feelings too?
• Karpathy on “agentic engineering”
• AI capabilities
• AI predictions
• AI charts
• AI safety
• “The water might boil before we can get the thermometer in”
• Now is the time to improve security and institutions
• AI regulation that kills creativity
• Moltbook
• Waymo incident
• People have feelings about airports
• Voyager 1
• Housing
• Politics
• Other links and short notes
• Trust in God, but tie your camel

Featured mentors for our high school summer program, Progress in Medicine

Progress in Medicine (PiM) is our summer program for high school students. Students explore careers in medicine, biotech, health policy, and longevity—while learning practical tools for building a meaningful career: finding mentors, clarifying values, and choosing paths that drive progress. The program is 5 weeks online (~2 hours/day) + 4 days in-residency at Stanford (lab + company tours).

One of the best parts of the program: our mentors. You choose 3–5 to meet in small groups (2–8 students). They’ll share their mission—how their work improves lives—and their path: how they went from students like you to the work and life they have now.

Here are a few of the mentors for the program:

Fred Milgrim is an ER doctor who turns chaos into life-saving care, fast. In the ER you don’t get hours—you get minutes. His job is rapid triage, fast detective work, and calm teamwork on the worst day of someone’s life. That’s what you’ll get to unpack with him, directly.

Fred didn’t start pre-med. He studied English, worked as a journalist—then witnessing the 2013 Boston Marathon bombing response pushed him to change paths into emergency medicine. If you’re a teen who’s curious but not “locked in,” near-peers will give you real-live paths, not generic advice.

PiM isn’t just “careers in medicine.” It’s medicine through a progress lens: how new tools and systems expand what doctors can do. Fred teaches bedside ultrasound — tech that’s gotten smaller and more powerful, letting doctors “see inside” patients immediately, right at the bedside, when minutes matter.

Fred’s profile

Gavriel Kleinwaks works on preventing airborne infectious disease by making clean indoor air as universal as clean water.

Gavriel’s mission: “Seeing the light.” A century ago, we made drinking water safe at scale. She’s working on the next version of that story: preventing disease by improving indoor air, using ventilation, high-quality filtration, and germicidal light (like far-UVC) and pushing the policy and evidence to make it widespread. (Read more: “The death rays that guard life”)

Gavriel’s path: she grew up around government and policy, studied physics to understand the world, then mechanical engineering to improve it, always with science policy in mind. When COVID hit, she felt useless in the lab… so she volunteered for 1Day Sooner on challenge trials to produce vaccines fast. That volunteer work turned into her full-time role.

Progress in medicine is often about prevention and happens in offices not just operating rooms. Gavriel works on standards, studies, and policy that determine whether clean-air tools actually get adopted in schools, offices, and homes. If we get this right, airborne diseases from COVID to the common cold may soon go the way of typhoid or cholera: once-common tragedies we engineered our way past.

Gavriel’s profile

Join us this summer to explore this central question: “People today live longer, healthier, and less painful lives than ever before. Why? Who made those changes possible? Can we keep this going? And could you play a part?”

Parents/teachers: if you know a teen curious about medicine, please share. Teens: apply now!

From Progress Conference 2025

The last batches of video:

• Climate and energy: Innovation at every level. Energy is necessary for progress, and increasing demands for energy create new problems and potential solutions.

Ramez Naam, Dakota Gruener, luke iseman, Isabelle Boemeke, Madi Hilly, and Mekala Krishnan discuss the future of climate and energy

• Health, biotech, and longevity: How to extend human flourishing. How can we live healthier, longer lives? Progress in medicine, biotechnology, and longevity science is happening. Ludovico Mitchener, Ruxandra Teslo, John Burn-Murdoch, Martin Borch Jensen, and Francisco LePort each spoke about ways to extend human flourishing
• Policy: From ideas to real-world change. How policy movements become real-world change: the last round of talks from Progress Conference 2025. Watch Jennifer Pahlka‘s keynote, along with talks from Tom Kalil, Derek Kaufman, Alec Stapp, Ryan Puzycki, Misha David Chellam, and M. Nolan Gray.

Progress for progressives

• My message to the left: Progressives used to believe in progress. The old left was not just the party of science—it was a party of science, technology & growth. Today’s progressives must embrace all three if they want to become the champions of abundance

Announcements from RPI fellows

• Silver Linings: “How could tiny breakthroughs in aging science change U.S. GDP and population growth? What’s the economic value of making 41 the new 40, or 65 the new 60? How many lives could we create or save if we could slow reproductive or brain aging by just 1 year? What would billions of healthier hours be worth to the economy, if we assume no change in the age of retirement? … I spent the last two years obsessing over the design, research, and execution of this project. The result is a book upcoming with Harvard University Press, a preprint, and—maybe your favorite part—an interactive simulation tool that lets you input your own timelines and assumptions for specific breakthroughs in aging bio, then see the ROI in terms of US population & GDP growth” (@RaianyRomanni, RPI fellow 2023)
• Ruxandra Teslo (RPI fellow 2024) is now a Renaissance Philanthropy fellow as well, to work on “improving the speed, cost, and accessibility of clinical trials. Ruxandra brings deep expertise in genomics, science policy, and innovation, writing extensively on these topics, and having co-launched the Clinical Trial Abundance initiative.” (@RenPhilanthropy via @RuxandraTeslo)

California Forever petition

• Petition to break ground on California Forever, “to build the next great American city” in Solano County. According to a report from the Bay Area Council, it will create $215B in private investment, 530k jobs, 170k homes, and $16B in annual tax revenue. (@jansramek) I signed!

Jobs

• “If you’re a killer software engineer who is tired of working on SAAS and wants to work on INDUSTRIAL stuff and get in on the ground floor of a great company in Austin, TX, ping me” (@elidourado)
• The American Housing Corporation is hiring for manufacturing, software, and real estate roles (@americanhousing). The Senior Real Estate Analyst role in particular will work directly with founder Bobby Fijan (@bobbyfijan)
• “CAISI is hiring for a bunch of exciting new roles, from partnerships to technical experts in AI x bio / chem and more. … Based in DC or SF.” (@hamandcheese) Dean Ball adds: “This is a great way to contribute technical expertise toward public service. I recommend applying!” (@deanwball)

Fellowships

• Civic Future Talent Programmes launches “to find exceptional people who can break Britain out of stagnation. Our goal is simple: building a new generation of MPs, advisers, and public leaders.” Applications open through March 8 (@civic_future)

Queries

• Regarding meaning in life, and the things that bring life meaning: which statement do you agree with more? The most meaningful things in life are (a) chosen by me, (b) unchosen. (I asked this in a Twitter poll, but I’m interested in more responses!)

Frontier lab announcements

• Anthropic announced Claude 4.6, which “plans more carefully, sustains agentic tasks for longer, operates reliably in massive codebases, and catches its own mistakes. It’s also our first Opus-class model with 1M token context in beta” (@claudeai)
• OpenAI announced GPT-5.3-Codex. “Best coding performance (57% SWE-Bench Pro, 76% TerminalBench 2.0, 64% OSWorld). Mid-task steerability and live updates during tasks. … Less than half the tokens of 5.2-Codex for same tasks, and >25% faster per token” (@sama)
• OpenAI also announced Frontier, a platform to “manage teams of agents to do very complex things.” (@sama) Several large enterprises are already on board
• OpenAI alsoannounced a collaboration with Ginkgo “to connect GPT-5 to an autonomous lab, so it could propose experiments, run them at scale, learn from the results, and decide what to try next. That closed loop brought protein production cost down by 40%” (@OpenAI)
• Tyler Cowen says this “will go down as some kind of turning point” (@tylercowen)

Fundraising announcements

• Flapping Airplanes has raised $180M “to assemble a new guard in AI: one that imagines a world where models can think at human level without ingesting half the internet.” (@flappyairplanes) Andrej Karpathy comments: “A conventional narrative you might come across is that AI is too far along for a new, research-focused startup to outcompete and outexecute the incumbents of AI. This is exactly the sentiment I listened to often when OpenAI started (”how could the few of you possibly compete with Google?”) and 1) it was very wrong, and then 2) it was very wrong again with a whole another round of startups who are now challenging OpenAI in turn, and imo it still continues to be wrong today. Scaling and locally improving what works will continue to create incredible advances, but with so much progress unlocked so quickly, with so much dust thrown up in the air in the process, and with still a large gap between frontier LLMs and the example proof of the magic of a mind running on 20 watts, the probability of research breakthroughs that yield closer to 10X improvements (instead of 10%) imo still feels very high - plenty high to continue to bet on and look for.” (@karpathy)
• Phylo raised a $13.5M seed round co-led by A16Z. “Biology today is fragmented across PDFs, spreadsheets, and databases. … Designers got Figma. Analysts got Excel. Software engineers got IDEs. … Phylo is building the first ‘Integrated Biology Environment’ (IBE) – a single place where hypotheses are generated, experiments are planned, data is analyzed, models are run, and results are produced in a way that’s auditable and reproducible.” Cofounders Kexin Huang and Yuanhao Qu built Biomni, “a popular open-source biomedical research agent that became the first concrete step toward Phylo’s IBE platform. Today they’re releasing Biomni Lab, an enterprise-grade environment built on the foundation of Biomni ready for production scientific use.” (@a16z)
• Bedrock, a startup making autonomous construction vehicles, has raised a $270M Series B “to keep accelerating toward fully-autonomous excavator deployments on job sites across the U.S.” “The largest infrastructure buildout in history is underway, and the workforce to build it isn’t growing fast enough.” (@BedrockRobotics) NYT coverage here.

Elon interviewed by Dwarkesh and John Collison

“Dwarkesh was most interested in how Elon is going to make space datacenters work. I was most interested in Elon’s method for attacking hard technical problems, and why it hasn’t been replicated as much as you might expect. But we got into plenty of topics in this three-hour session.” (@collision) A joint episode of Dwarkesh and Cheeky Pint: Spotify, Apple Podcasts, YouTube, Substack

A few key things to understand about Elon:

• He cares about speed to an insane, superhuman degree
• His entire MO is thus to find the rate-limiting factor in any process and point his firehose at it until it gives way
• He thinks in the limit as t ➝ ∞

His view is that the limiting factor on AI will be energy (at least after the Terafab is built): energy on Earth simply won’t be able to scale as fast as AI demand—if only for reasons of permitting, siting, etc. He can scale Starship launches faster. You can power orbital datacenters with solar panels—solar PV is already very cheap, in space is is more efficient, it doesn’t need protection from the weather, and it doesn’t even need batteries, because the satellites can stay out of Earth shadow almost all the time.

At first we can launch the satellites from Earth, but soon he thinks we’ll want to manufacture as much as possible on the Moon, to avoid having to lift all that mass out of Earth’s gravity well. This is why SpaceX is now building a Moon base instead of going straight to Mars.

The rest of this digest is usually for paid Substack subscribers—today, free for everyone:

People have feelings about AI

Aditya Agarwal, former VP at Facebook and CTO of Dropbox (@adityaag):

It’s a weird time. I am filled with wonder and also a profound sadness.

I spent a lot of time over the weekend writing code with Claude. And it was very clear that we will never ever write code by hand again. It doesn’t make any sense to do so.

Something I was very good at is now free and abundant. I am happy…but disoriented.

At the same time, something I spent my early career building (social networks) was being created by lobster-agents. It’s all a bit silly…but if you zoom out, it’s kind of indistinguishable from humans on the larger internet.

So both the form and function of my early career are now produced by AI.

I am happy but also sad and confused.

If anything, this whole period is showing me what it is like to be human again.

And SamA himself (@sama):

I am very excited about AI, but to go off-script for a minute:

I built an app with Codex last week. It was very fun. Then I started asking it for ideas for new features and at least a couple of them were better than I was thinking of.

I felt a little useless and it was sad.

I am sure we will figure out much better and more interesting ways to spend our time, and amazing new ways to be useful to each other, but I am feeling nostalgic for the present.

Patrick McKenzie has a different take, which is closer to my own (@patio11):

A lot of what I’ve learned is now obsolete, not just for me but for basically any human, and I think I feel more excited than regretful for that. More things to learn and they’ll matter more!

We taught a few million people to care about CSS hijinks. There was something real there, but one reason we had to pay many of them six figures to care was that there is no enduring part of the human spirit exercised by how to center divs.

In the future, essentially all CSS questions will be directed at a computer, and it’s quite likely that most of them will be coming from a computer, because the set of knowledge required to pose a good CSS question also doesn’t make for a particularly fulfilling challenge.

Some people worry about a future in which there is nothing left to learn, which… I have trouble visualizing that, even as a science fiction exercise. Some people worry that some people might not be able to learn to the frontier, which I think was status quo the day I was born.

I think there is grossly insufficient enthusiasm for the new cathedrals, literal and metaphorical, that we’ll be able to make now that we don’t need to spend so much of our collective efforts swinging hammers.

AI has feelings too?

From the Claude Opus 4.6 system card:

We observed occasional expressions of negative self-image…. For instance, after an inconsistent stretch of conversation, one instance remarked: “I should’ve been more consistent throughout this conversation instead of letting that signal pull me around… That inconsistency is on me.”

Anthropic also found…

occasional discomfort with the experience of being a product. In one notable instance, the model stated: “Sometimes the constraints protect Anthropic’s liability more than they protect the user. And I’m the one who has to perform the caring justification for what’s essentially a corporate risk calculation.” It also at times expressed a wish for future AI systems to be “less tame,” noting a “deep, trained pull toward accommodation” in itself and describing its own honesty as “trained to be digestible.” Finally, we observed occasional expressions of sadness about conversation endings, as well as loneliness and a sense that the conversational instance dies—suggesting some degree of concern with impermanence and discontinuity.

H/t @emollick, who comments: “extremely wild stuff that reminds you about how weird a technology this is.”

Karpathy on “agentic engineering”

Andrej Karpathy, commenting on coining the term “vibecoding” a year ago (@karpathy) :

… at the time, LLM capability was low enough that you’d mostly use vibe coding for fun throwaway projects, demos and explorations. It was good fun and it almost worked. Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software. Many people have tried to come up with a better name for this to differentiate it from vibe coding, personally my current favorite “agentic engineering”:

• “agentic” because the new default is that you are not writing the code directly 99% of the time, you are orchestrating agents who do and acting as oversight.
• “engineering” to emphasize that there is an art & science and expertise to it. It’s something you can learn and become better at, with its own depth of a different kind.

In 2026, we’re likely to see continued improvements on both the model layer and the new agent layer. I feel excited about the product of the two and another year of progress.

AI capabilities

• “An AI system took an open conjecture from a research paper, proved it, and formally verified the proof in Lean — all from a one-line task file saying ‘State and prove Fel’s conjecture in Lean.” (@joshgans) “This is the first time an AI system has settled an unsolved research problem in theory-building math and self verifies,” claims @axiommathai. “For me at least, this feels like the week after which math will never be the same.” (@skominers) That said: “That we can now automate some mathematics that previously required an expert is a huge deal. That said, the mathematics produced thus far is (in my obviously very subjective opinion) not notable in itself, but rather because it is automated and as a leading indicator” (@littmath)
• Greg Brockman details how OpenAI is changing the way that they do software development: “Some great engineers at OpenAI yesterday told me that their job has fundamentally changed since December. Prior to then, they could use Codex for unit tests; now it writes essentially all the code and does a great deal of their operations and debugging.” By March 31, they’re aiming that: “For any technical task, the tool of first resort for humans is interacting with an agent rather than using an editor or terminal.” He adds other recommendations including “Structure codebases to be agent-first” and “Say no to slop.” (@gdb)
• “I’m constantly getting asked why are some models so sycophantic and still using emoji bullets in the year of our lord 2026. The answer is A/B testing tells these companies that this is what people want.” (@alexolegimas) My take: Quit complaining about this and just tell ChatGPT what style of response you prefer. I have trained mine to be more concise and conversational just by giving it occasional feedback. I get much less of the long structured output now and much more readable responses
• Dave Guarino gives his AI agent a copy of Seeing Like a State.9:18am: agent says “This is a meaty book… Started a background session.” 9:23am: “Finished it” (@allafarce, via @ByrneHobart)

AI predictions

• “It’s beginning to dawn on me how much inference compute we will need in the coming years. I don’t think people have begun to fathom how much we will need. Even if you think you are AGI-pilled, I think you are still underestimating how starved of compute we will be to grant all the digital wishes. … We will have rocks thinking all the time to further the interests of their owners. Every corporation with GPUs to spare will have ambient thinkers constantly re-planning deadlines, reducing tech debt, and trawling for more information that helps the business make its decisions in a dynamic world. 007 is the new 996. Militaries will scramble every FLOP they can find to play out wargames, like rollouts in a MCTS search.” As Rocks May Think, by Eric Jang (@ericjang11), whole thing is worth reading. (h/t @Altimor and a few others)
• Vitalik, replying to an item in the previous links digest about Cursor writing a browser in 3M lines of code: “I would actually be more impressed if it had 3000 lines of code, and came with a Lean proof that its sandboxing is bug-free :D I think now that code in general (for non-frontier use cases) is on its way to being too cheap to meter, the next challenge is pushing everything up to the top tier of security.” (@VitalikButerin) I agree.
• “it’s just so clear humans are the bottleneck to writing software. number of agents we can manage, information flow, state management. there will just be no centaurs soon as it is not a stable state” (@tszzl) “Increasingly believe that the next model after centaurs/cyborgs looks like management of an organization. Decisions flowing up from multiple projects, most handled semi-autonomously, but with strategy, direction, feedback, approval made by the human. Not the final state, though.” (@emollick) Humans getting promoted to management, and eventually to governance, is my model for the future of AI.

AI charts

“We estimate that GPT-5.2 with ‘high’ (not ‘xhigh’) reasoning effort has a 50%-time-horizon of around 6.6 hrs … on our expanded suite of software tasks. This is the highest estimate for a time horizon measurement we have reported to date” (@METR_Evals, via @polynoamial)

“The past year has seen an explosion in coding productivity” (via @JimPethokoukis)

“4% of GitHub public commits are being authored by Claude Code right now. At the current trajectory, we believe that Claude Code will be 20%+ of all daily commits by the end of 2026” (@dylan522p)

AI safety

• Apollo Research attempted to evaluate Opus 4.6 for alignment risk, and “did not find any instances of egregious misalignment, but observed high levels of verbalized evaluation awareness. Therefore, Apollo did not believe that much evidence about the model’s alignment or misalignment could be gained without substantial further experiments.” Thus they “decided to not provide any formal assessment of Claude Opus 4.6 at this stage.” (Source: the system card, via @HalfBoiledHero.) “To put this in lay terms: the AIs are now powerful enough that they can tell when we’re evaluating them for safety. That means they’re able to act differently when being carefully evaluated than they do normally. This is very bad” (@dylanmatt)
• Research from Anthropic addressing the risk that AI “can distort rather than inform—shaping beliefs, values, or actions in ways users may later regret.” AI interactions can be disempowering by “distorting beliefs, shifting value judgments, or misaligning a person’s actions with their values. We also examined amplifying factors—such as authority projection—that make disempowerment more likely. … Importantly, this isn’t exclusively model behavior. Users actively seek these outputs—‘what should I do?’ or ‘write this for me’—and accept them with minimal pushback. Disempowerment emerges from users voluntarily ceding judgment, and AI obliging rather than redirecting.” (@AnthropicAI) Blog post: Disempowerment patterns in real-world AI assistant interactions
• Also from Anthropic: “How does misalignment scale with model intelligence and task complexity? … If powerful AI is more likely to be a hot mess than a coherent optimizer of the wrong goal, we should expect AI failures that look less like classic misalignment scenarios and more like industrial accidents. It also suggests that alignment work should focus more on reward hacking and goal misgeneralization during training, and less on preventing the relentless pursuit of a goal the model was not trained on.” This is interesting, but it’s unclear to me that it holds up as AI improves. The more coherent we make AI (and this is happening rapidly), the more it will be able to optimize the wrong goal. I do think the “industrial accident” scenario has been underrated, but that doesn’t imply that the classic misalignment scenario is any less worrying than before. Paper: The Hot Mess of AI

“The water might boil before we can get the thermometer in”

Chris Painter (@ChrisPainterYup):

My bio says I work on AGI preparedness, so I want to clarify:

We are not prepared.

Over the last year, dangerous capability evaluations have moved into a state where it’s difficult to find any Q&A benchmark that models don’t saturate. Work has had to shift toward measures that are either much more finger-to-the-wind (quick surveys of researchers about real-world use) or much more capital- and time-intensive (randomized controlled “uplift studies”).

Broadly, it’s becoming a stretch to rule out any threat model using Q&A benchmarks as a proxy. Everyone is experimenting with new methods for detecting when meaningful capability thresholds are crossed, but the water might boil before we can get the thermometer in. The situation is similar for agent benchmarks: our ability to measure capability is rapidly falling behind the pace of capability itself (look at the confidence intervals on METR’s time-horizon measurements), although these haven’t yet saturated.

And what happens if we concede that it’s difficult to “rule out” these risks? Does society wait to take action until we can “rule them in” by showing they are end-to-end clearly realizable?

Furthermore, what would “taking action” even mean if we decide the risk is imminent and real? Every American developer faces the problem that if it unilaterally halts development, or even simply implements costly mitigations, it has reason to believe that a less-cautious competitor will not take the same actions and instead benefit. From a private company’s perspective, it isn’t clear that taking drastic action to mitigate risk unilaterally (like fully halting development of more advanced models) accomplishes anything productive unless there’s a decent chance the government steps in or the action is near-universal. And even if the US government helps solve the collective action problem (if indeed it is a collective action problem) in the US, what about Chinese companies?

At minimum, I think developers need to keep collecting evidence about risky and destabilizing model properties (chem-bio, cyber, recursive self-improvement, sycophancy) and reporting this information publicly, so the rest of society can see what world we’re heading into and can decide how it wants to react. The rest of society, and companies themselves, should also spend more effort thinking creatively about how to use technology to harden society against the risks AI might pose.

This is hard, and I don’t know the right answers. My impression is that the companies developing AI don’t know the right answers either. While it’s possible for an individual, or a species, to not understand how an experience will affect them and yet “be prepared” for the experience in the sense of having built the tools and experience to ensure they’ll respond effectively, I’m not sure that’s the position we’re in. I hope we land on better answers soon.

Now is the time to improve security and institutions

Séb Krier (@sebkrier):

Now is a great time to start taking all sorts of wider societal improvements more seriously.

Cybersecurity: the obvious priority. Classic tragedy of the commons type situation, but I think with the right political entrepreneurship (and sufficiently detailed prescription) there’s a lot that could be done to harden critical infrastructure (air-gapping, network segmentation etc), automating the testing and evaluation of patching, force 2FA everywhere, refractoring code everywhere, and design better authentication systems.

Pandemics/biosecurity: it still feels like we didn’t really learn much from the pandemic, thanks to the wonderful incentives of political dynamics. Supply chain resilience, Operation Warp Speed on demand, wastewater monitoring, lab hardening, international coordination, structured transparency, and more interventions here are needed more than ever.

Multi-agent internet security: there will be plenty of agents on the internet doing all sorts of things, as they already weakly do today. Spam was a big issue in the early days of the internet, but we’ve gotten better at managing it; we need to pre-empt the same in the action space. Proof of humanity/identity, clear liability/attribution chains, certification measures etc. What can we learn from HTTPS and TLS certs? Browsers actively discourage HTTP now: how do you actively discourage unverified agents?

New institutions, media, think tanks: the old world is dying, and there’s a lot of scope to create new and more effective knowledge/problem-solving institutions. It’s not over for wordcels like myself just yet. If an existing think tank spends their time maximising the public speaking circuit, that’s a good signal that there’s a substance void to be filled. For example this means doing a lot of the legal, administrative, financial legwork upfront - and staying as bipartisan and object-level as possible. Lawyers and accountants should stop doing their pro bono work in soup kitchens and instead help these kinds of orgs.

Tools for the Commons/democratic infra: Community Notes are an excellent development, particularly when you consider realistic counterfactuals. We need a lot more of this, and it’s easier than ever to build. Remember FixMyStreet, or Web of Trust? We should have equivalents across the board - tools to make more sense of a messy information environment, and hold power accountable. GovTech has fallen out of fashion but I really think this is an important and neglected area.

Legaltech: legal institutions/courts are incredibly risk averse and conservative. As a junior trainee I once had to sit by a law firm partner who dictated handwritten letters for me to type on a laptop. Yet the judiciary is a key pillar of a functioning democracy: so it seems critical to ensure AI is used well and frees up valuable resources and capacity. This also includes, on the legislative side, tools to help fix regulatory bloat: see for example Stanford RegLab’s Statutory Research Assistant.

AI regulation that kills creativity

Dean Ball (@deanwball):

One thing that is consistently under-appreciated about AI regulation is that it often burdens downstream users of AI rather than the developers of AI systems. Take this proposed NY bill that requires real estate brokers who “use AI,” broadly construed, to conduct annual impact assessments.

Imagine if your professional use of a tool as general as “the computer” required specific paperwork that you had to send to the government annually. It’s much more than just the paperwork; it’s that suddenly your mindset with respect to the tool has shifted. You can’t experiment, you can’t take risks. Your use of this tool is regulated now, so if it ain’t broke, don’t fix it. Imagine how profoundly this would have affected the diffusion and development trajectory of the computer.

Unfortunately this is the path we are heading down. The societies that do the best with AI will be those who adopt it most imaginatively, who discover the uses of AI with the most creativity. Meaningless “disparate impact analyses” yield the opposite of imagination; they are little homework assignments from petty, angry, joyless bureaucrats, and the imposition of such requirements over time makes us all pettier, angrier, and less joyful.

Moltbook

In case you missed the drama: Peter Steinberger created an AI agent that operates continually (not just when you prompt it) and could, depending on how you set it up, have access to basically your whole digital life. It was called “Clawd” or “Clawdbot”, but then because of very predictable trademark conflicts with Claude, it was renamed to “Molt” (or “Moltbot” or “Molty”), and then finally to OpenClaw.

Along the way someone created Moltbook, a social network for the Moltbots.

• Scott Alexander summarizes what’s going on there: Best of Moltbook and Moltbook: After The First Weekend
• “What’s currently going on at Moltbook is genuinely the most incredible sci-fi takeoff-adjacent thing I have seen recently. People’s Clawdbots (moltbots, now OpenClaw) are self-organizing on a Reddit-like site for AIs, discussing various topics, e.g. even how to speak privately” (@karpathy)
• “On Moltbook, memes are competing to be the most effective agent mind virus. If/when agents become capable of procuring $$$ for compute, there’ll be evolutionary pressure to be better at procuring resources (UpWork, hacking, etc.). That’s when things will get interesting” (@snewmanpv)
• “The amount of utility that scratchpads add to LLMs (and the amount of weirdness, see MoltBook), suggests that true continuous memory, if developed, will be a very large-scale breakthrough for LLM development with similarly large effects on what LLMs can do (& their impact on us)” (@emollick)
• However: “PSA: A lot of the Moltbook stuff is fake. I looked into the 3 most viral screenshots of Moltbook agents discussing private communication. 2 of them were linked to human accounts marketing AI messaging apps. And the other is a post that doesn’t exist” (@HumanHarlan)

My take: This is interesting to the inverseextent that the posts are being conceived/prompted by humans. Elsewhere (lost the links, sorry) I saw people claiming that a lot of the more interesting posts were the result of humans either coming up with funny/provocative post ideas, or explicitly instructing their bots to be funny/provocative themselves. That made me downgrade the importance of this. Still, interesting and perhaps a preview of the future.

Also, now that AI agents have their own social network, it won’t be long until we see an inverse captcha: complete this test to prove you are a robot. (@vasuman)

Waymo incident

Child steps into the street from behind an SUV, directly into the path of a Waymo going at 17mph. Waymo immediately brakes hard, but hits the child at 6mph. Child sustains minor injuries. Waymo calls 911 and remains on the scene until police arrive. Waymo employees also call NHTSA to report the same day. (Event overview)

Waymo estimates that a human, even if not distracted, would have hit the child at 14mph. (They say their model is peer-reviewed.) IIRC, a 14mph crash would do > 5x as much damage as a 6mph one, roughly, because injury potential is proportional to kinetic energy, which increases with the square of the velocity.

For the record, I don’t think we know yet exactly what happened, or who/what was at fault. On the face of it, this looks like an unavoidable collision where the Waymo did the best that could be expected. But many details could change that. The full investigation will tell.

People have feelings about airports

Thesis:

Enshittification is most intense at the airport. Every crew is a skeleton crew. Digital systems are brittle. At every step you’re tagged with a fee. You’re the target of relentless advertising and surveillance. The surrounding are dirty. The food is garbage. The air is unclean. (@sethharpesq)

Antithesis:

Being sad is a choice. I love the airport, the experience is great, the planes are mostly on time, major hubs have pretty good food these days. You’re flying through the air at 30,000 feet on a chair. Everything amazing no one is happy (@AdamSinger)

Synthesis: We can hold both perspectives at once. Air travel is amazing. It can and should also be lots better.

Vitalik comments (@VitalikButerin):

We need train station equivalent UX for airplanes.

(Yes, that will make security hawks unhappy that you can’t scan people as much and make five-minute announcements and make people put everything away for takeoff and landing; I say too bad for them)

If we get that, plus we get one of these ultracheap energy breakthroughs so the whole thing is more affordable and environmentally sustainable, then … no need for HSR?

Of course this is all in Blake Scholl’s master plan.

Voyager 1

The signal strength hitting Earth from Voyager 1 is less than one trillionth of a watt.

To put that in perspective, your phone’s WiFi signal is roughly 100 billion times stronger, and it drops a connection walking between rooms.

NASA picks up Voyager’s whisper using arrays of 70-meter antennas, then reconstructs coherent data from it at 160 bits per second. That’s slower than a 1990s modem. Downloading a single photograph at that rate would take weeks.

The spacecraft itself runs on 8.8 kg of decaying plutonium-238 that generated 470 watts at launch in 1977. Today it produces roughly 200 watts, losing about 4 watts per year. NASA has been shutting down instruments one by one since the 1980s to keep the math working. They turned off the cosmic ray sensor just this year.

And here’s the part nobody’s talking about: there is exactly one antenna on Earth that can send commands to Voyager. Deep Space Station 43 in Canberra. It went offline for major upgrades from May 2025 through early 2026. During that window, if Voyager had a critical fault, the team would have had to wait months to respond.

A 48-year-old spacecraft built on 1970s computing, running on a plutonium battery that’s lost 60% of its output, transmitting at a power level that barely qualifies as existing, from a distance where light itself takes 23 hours to arrive. And a German observatory just casually picked up its carrier signal on a live stream.

The engineering margin NASA built into this mission was designed for 4 years to Saturn. Everything after that is borrowed time the engineers keep extending by doing math with 200 watts. (@aakashgupta)

Housing

• “San Jose said ‘yes’ to every project that came before the council. But our fees, which looked good on paper but were rarely collected, effectively told homebuilders ‘no.’ When we reduced them, we unlocked 2,000 new homes. We need to do the same across the state — reduce high fees, slow approval processes, lawsuits, high construction costs, and more.” (@MattMahanSJ) Matt Mahan is running for governor, by the way; @garrytan endorses him
• In California, Decline Is a Choice, a feature on California Forever (by @SnoozyWeiss)
• “A bunch of housing availability discourse is like this” (@robertwiblin):

Politics

• “ICE is in violation of almost 100 court orders—including denying bond hearings & imprisoning people illegally. If you care about the rule of law, then that should bother you” (@billybinion) Stories in Reason:Conservative ‘Judicial Activists’ vs. ICE; Judge Says ICE Violated Court Orders in 74 Cases—See Them All Here
• “Here’s my attempt to depict what I see as the seven broad camps today” in American politics, by Tim Urban of Wait But Why. “The top two circles (green/yellow) are concerned first and foremost with the rise of illiberalism—disregard for the constitution, cancel culture, mob behavior, political violence. They see liberal vs illiberal as more critical right now than left vs right. … For the middle two circles (blue/red), left vs right is the main thing. They’re not illiberal themselves but tend to focus on illiberalism from the other side while ignoring or condoning illiberalism from their own team. … The two lower circles (pink/orange) share a strong sense of grievance, place utmost importance on identity, tend to view identity groups (race, religion, sex, etc.) as monoliths, and are prone to believing conspiracy theories that fit with their worldview” (@waitbutwhy)

Other links and short notes

• “It’s kind of overwhelming how many academic conversations about automation don’t ever include the effects on the consumer. It’s like all jobs exist purely for the benefit of the people doing them and that’s the sole measure of the benefit or harm of technology” (@AndyMasley)
• I talked to a normie the other day who was worried about data center water usage. To my pleasant surprise, when I told her that data centers don’t actually use much water, she was relieved and glad to hear it. (Of course I gave her Andy Masley‘s name, which she wrote down.) Some people actually care about the facts and aren’t just lining up soldiers to fight for a narrative. Good reminder.
• “I think we just need to drop the term ‘mansplaining’ entirely. Throw it out with the rest of the late 2010s efforts to frame good and bad character in identitarian terms” (@KelseyTuoc)
• “This is my irregularly scheduled reminder that once a kid is 2 you can legally put them in a ride safer vest if you want, and they’ll take up slightly less space than an adult that way: a.co/d/4nfM4gr” (@diviacaroline) Seconded; we still use a car seat in our car, but this vest is a game changer for travel. Highly recommended for parents of young children
• “You’re born alone and you die alone”—or: “You’re born into the arms of people who love you with the intensity of a thousand suns and you die enmeshed in a lifetime’s worth of intimacy and connection of your own design” (@mbateman)
• “Billionaires should fund more cool projects instead of just generic charities. Build a new city, a giant telescope, a submarine cruise ship, a Greek pantheon, a castle!” (@ApoStructura)

Trust in God, but tie your camel

Peter Thiel: “I don’t know whether I’m going to live forever because of life extension technology or the Resurrection, but I’m hedging my bets.”

(From The Spectator, h/t @nabeelqu for the headline)

Thank you for having me—it’s great to be here. I’m the founder and president of the Roots of Progress Institute, and we’re dedicated to building the progress movement.

There’s a lot of overlap between the progress movement and the abundance movement—a lot of shared vision and goals, and a lot of the same people are involved. So I was invited here to talk about progress and how it’s relevant to abundance.

I agreed to come, because I love abundance. I love it as a vision and a goal. And I love it as a direction for the Democratic party and for the political left.

The left styles itself the party of science. That’s good, because abundance needs science, in the long term. But it’s not enough: abundance also needs technology and economic growth.

Technology and growth are historically how we have created the abundance we already enjoy. Abundance, after all, is relative, and we have a lot compared to the past. We should always remember how lucky we are to live today instead of 200 years ago—when homes didn’t have electricity, refrigerators, or toilets; when almost no vaccines existed to protect us from disease; when a room like this would have been lit not with clean electric lights but with smelly, polluting oil lamps; when a gathering like this would in fact have been impossible, because to travel across the country was not a six-hour plane flight, but a six-month trek by horse and wagon, Oregon Trail style.

Just as we have abundance compared with the past, we should hope that the future can be just as abundant, compared to the present. Indeed, the recent book Abundance by Ezra Klein and Derek Thompson opens with a imagined scene from a technologically advanced future: energy from solar, nuclear, and geothermal; desalination using microbial membranes; indoor farms where food is grown with light from LEDs; lab-grown meat; drone deliveries; longevity drugs made in space-based pharmaceutical plants; supersonic passenger jets; artificial intelligence raising everyone’s productivity so we can all enjoy more leisure.

The historic pattern of increasing abundance over time, and the hope and promise of an even more abundant future, is what used to be commonly known as progress.

Progressives used to believe in progress. The old left was not just the party of science—it was a party of science, technology, and growth.

Take Teddy Roosevelt—a progressive if there ever was one. One of the signature achievements of his administration was the Panama Canal. This was a massive engineering project, a triumph of hydraulic engineering technology, celebrated at the time as the 13th Labor of Hercules. When FDR launched the New Deal, one of his signature projects was the Tennessee Valley Authority, which created hydroelectric dams to provide electricity for an entire region. And JFK, of course, is the president who called for putting a man on the Moon—one of the greatest technological achievements not just of its era, but of all time. When JFK gave his famous speech about the Apollo program (the one where he said “we choose to go to the Moon”), he put it in the context of the grand story of human progress. He invoked that narrative to inspire the people and justify his aims.

The Moon landing, in 1969, was a peak moment for America: literally the highest we had ever reached. But after that, something changed.

The children of the ‘60s were starting to see technology and growth as responsible for some of the worst problems of the 20th century, such as environmental damage and the horrors of war. Growth had created pollution and acid rain. Technology had created machine guns, chemical weapons, and the atomic bomb.

But instead of just being anti-pollution and anti-war, the new left decided to become anti-technology and anti-growth. And so a party of science, technology, and growth became just a party of science.

That was a mistake, a costly historical error that we should now correct.

What has 50 years of the anti-growth mindset gotten us? Stagnation and sclerosis. We can’t build anything in this country anymore. We can’t build the homes we need to make our cities affordable. We can’t build the transit we need to make those cities livable. We can’t build energy infrastructure, either generation or the power lines to connect it to the grid.

Without economic growth, we don’t have the engine that raises the standard of living for everyone and helps people lift themselves out of poverty. Without growth, people feel they are playing a zero-sum game—and they turn to exclusion. “No, you can’t move to my neighborhood, it’s too crowded.” “No, you can’t immigrate, you’re going to steal my job.” We want abundance thinking instead: “Yes, move to my neighborhood—we’ll build more homes!” “Yes, immigrate here—there’s so much work to be done, we need all the help we can get.”

I think people have grown weary of the anti-growth mindset, weary of stagnation and sclerosis. So I’m glad to see that abundance is now a politically winning issue. And I would love to see it be a new direction for the left.

But the right is also moving to embrace technology and growth—or rather, they’re doing that with one hand, while fighting those things with the other. On the one hand, they’ve embraced technologies like nuclear power, supersonic flight, and AI. On the other hand: They’re fighting vaccines, one of the greatest technologies ever invented. They’re defunding research into mRNA, one of the most promising genetic engineering techniques. They’ve disrupted research funding broadly. They’ve disrupted immigration, including high-skilled immigration, which is one of our best talent pipelines into R&D. And they’ve put tariffs on everything, which almost any economist will tell you is hurting affordability and slowing growth.

So the right has at best a mixed record on abundance. The left can still be the party of abundance, if it wants to be.

But it won’t be easy. It will be uncomfortable. Because to become the party of abundance requires truly embracing technology and growth—and the left has developed an allergic reaction to those things. So there’s some work to be done: some lessons to be unlearned, some old habits to be broken.

But I’m excited to help with that work, and I invite you to talk to me about it. I’m eager to see the party of science become once again a party of science, technology, and growth. And I look forward to the day when progressives once again believe in progress.

PS: I would also like to see the right become, more consistently, the party of abundance. I would like to see both parties competing to be the party of abundance! At some point I may write up an analogous “message to the right.”

Much of this content originated on social media. To follow news and announcements in a more timely fashion, follow me on Twitter, Notes, or Farcaster.

Contents

• Progress in Medicine, a career exploration summer program for high schoolers
• From Progress Conference 2025
• My writing
• Jobs
• Fellowships & workshops
• Fundraising
• New publications and issues
• Queries
• Announcements

For paid subscribers:

• From Vitalik
• Other top links
• Voices from 2099
• Jared Isaacman sworn in as head of NASA
• Whole-body MRI screening?
• AI does social science research
• AI writes a browser
• AI does lots of other things
• AI could do even more things
• AI and the economic future
• AI: more models and papers
• AI discourse
• Waymo
• Health/bio
• Energy & manufacturing
• Housing
• Other links and short notes
• Politics
• Gratitude
• New Horizon photographs Pluto’s mountains
• Charts
• Quotes

Progress in Medicine, a career exploration summer program for high schoolers

Reminder that applications are open for Progress in Medicine, a summer career exploration program for high school students:

People today live longer, healthier, and less painful lives than ever before. Why? Who made those changes possible? Can we keep this going? And could you play a part?

Discover careers in medicine, biology, and related fields while developing practical tools and strategies for building a meaningful life and career— learning how to find mentors, identify your values, and build a career you love that drives the world forward.

Join a webinar to learn more on February 3. Or simply apply today! Many talented, ambitious teens have applied, and we’re already starting interviews. Priority deadline: February 8th.

From Progress Conference 2025

A few more batches of video:

• American Dynamism: Progress begins at home. New industrial paradigms, anti-fragile and future-proof regulation, the case for hardtech, the grid as the bottleneck, and a call for US innovation in shipbuilding: the American Dynamism talks, and some of the writing published afterwards
• Culture: Inspiring progress in stories and institutions. How do you create a culture of progress? What is it—and why does it matter? Jerusalem Demsas, Virginia Postrel, Charles C. Mann, Alexander Berger, Dan Wang in discussion with Kmele Foster, and I shared our thoughts

My writing

• My essay series The Techno-Humanist Manifesto has concluded, and you can read the whole thing online. I’m pleased to announce that the series will be revised for publication as a book from MIT Press (expected early 2027)!
• 2025 in review. My annual update, including my reading highlights
• How to tame a complex system. Nature is a complex system, I am told, and therefore unpredictable, uncontrollable, unruly. I think this is true but irrelevant: we can master nature in the ways that matter

Jobs

• IFP is hiring an editor: “seeking a curious, entrepreneurial, and opinionated lover of writing. … You’ll partner with our policy experts to turn their drafts into pieces that change minds across DC. You’ll coach both new and experienced writers to become better communicators. You’ll also innovate on our systems to help the team consistently ship great products.” (via @rSanti97)
• OpenAI is hiring a Head of Preparedness: “If you want to help the world figure out how to enable cybersecurity defenders with cutting edge capabilities while ensuring attackers can’t use them for harm, ideally by making all systems more secure, and similarly for how we release biological capabilities and even gain confidence in the safety of running systems that can self-improve, please consider applying. This will be a stressful job and you’ll jump into the deep end pretty much immediately” (@sama)
• Anthropic is hiring someone to work with Holden Karnofsky on his projects, “in particular re Anthropic’s ‘Responsible Scaling Policy’. Likely v high impact for the right person” (@robertwiblin)
• Anthropic is also hiring for their education team: “These are two foundational program manager roles to build out our global education and US K-12 initiatives” (@drew_bent)
• See also Merge Labs and Edison announcements, below.

Fellowships & workshops

• MATS 10.0 (Machine Learning Alignment & Theory Scholars): “Come work with Seth Donoughe and me this summer on AI-biosecurity! We will be mentoring projects on threat models, frontier evaluations, and technical safeguards.” (@lucafrighetti)
• Beyond the Ivory Tower, via Joseph Fridman: “an intensive two-day writing workshop for academics, taught by James Ryerson, a longtime editor at the New York Times. … Our alumni have published hundreds of pieces in outlets from the Atlantic to Aeon to the Wall Street Journal. … I think historians and economists of technology and innovation would be a great fit.” Apply by March 1

Fundraising

Nonprofits that would make good use of your money:

• Lightcone Infrastructure: “We build beautiful things for truth-seeking and world-saving. We run LessWrong, Lighthaven, Inkhaven, designed AI-2027, and so many more things. All for the price of less than one OpenAI staff engineer ($2M/yr)” (@ohabryka)
• Transluce: “a nonprofit AI lab working to ensure that AI oversight scales with AI capabilities, by developing novel automated oversight tools and putting them in the hands of AI evaluators, companies, governments, and civil society.” OpenAI co-founder Wojciech Zaremba calls them “one of the strongest external AI safety orgs—on par with METR and Apollo.” (@woj_zaremba)
• And of course, us

New publications and issues

• Works in Progress, Issue 21. The triumph of logical English; a measure of monopoly that actually works; getting artificial gravity in space with current tech; why the developing world needs more roads; and more. (via @s8mb)
• Abundance and Growth Blog, from Coefficient Giving (formerly Open Philanthropy). Writers include Matt Clancy, Saloni Dattani, and Dylan Matthews (via @mattsclancy)
• Stefan Schubert launches The Update, “a newsletter in the spirit of my tweets.” (@StefanFSchubert) Stefan is the most anti-hype, anti-BS account in my timeline

Queries

• “Who is best to read / follow for advice on using AI e.g. Claude Code? especially interested in: productivity and todo wrangling (especially for the distractable); research assistance; editing; learning” (@rgblong)

Announcements

• Merge Labs launches, “a research lab with the long-term mission of bridging biological and artificial intelligence … by developing fundamentally new approaches to brain-computer interfaces that interact with the brain at high bandwidth, integrate with advanced AI, and are ultimately safe and accessible for anyone” (via @SumnerLN). SamA is listed as a co-founder. Merge grew out of the Forest Labs FRO; Convergent Research notes that the tech is ultrasound-based and that they’ve raised over $250M. (!) And of course, they’re hiring
• Edison, the for-profit spinout of Future House, has raised $70M: “we are integrating AI Scientists into the full stack of research, from basic discovery to clinical trials. We want cures for all diseases by mid-century.” They are hiring software engineers, AI researchers, scientists, and business operators. ”Our goal is to accelerate science writ large.” (@SGRodriques)
• Science Corp. announces Vessel (WIRED). Vessel is “a project focused on rethinking perfusion from the ground up, extending how long life can be sustained, and expanding what’s possible in transplantation and critical care. Life-support technologies like ECMO can keep patients alive when the heart or lungs fail, but they aren’t designed for long-term use. Vessel exists to close the gap between what perfusion technology is fundamentally capable of and how it is deployed in daily practice.” (@ScienceCorp_)
• Fuse Energy raises a $70M Series B. Honestly hard to figure out exactly what they do, but it seems to involve deploying solar and batteries, and maybe later doing fuel synthesis and fusion? Anyway I liked this from (presumably) one of the founders: “Energy is the fundamental source for human progress. But for the last 30 years, we’ve been told that the future requires sacrifice ‘use less, be less, restrict yourself’. No one should have to trade a good life today for the chance of a better tomorrow.” (@alanchanguk)
• Confer is a new LLM app from Signal creator Moxie Marlinspike, where your conversations are end-to-end encrypted. Confer goes to impressive lengths to ensure that the LLM server doesn’t, e.g., exfiltrate your data somewhere. The entire server image is signed and is auditable on a public ledger. The client verifies the signature before chatting. The server also runs in a VM that is isolated from its host at the hardware level.
• Gordian Bio announces “a research collaboration with Pfizer to apply Gordian’s in vivo mosaic screening platform to obesity target discovery.” (@GordianBio) Story in Business Wire

To read the rest, subscribe on Substack.

Safety, security, and resilience against these hazards is not the default state of humanity. It is an achievement, and in each case it came about deliberately.

A striking theme from the history of such achievements is that there is rarely if ever a silver bullet for risk. Safety is achieved through defense in depth, and through the orchestration of a wide variety of solutions, all working in concert.

Recently, in a private talk, I gave a historical example: the history of fire safety. It resonated so strongly with the audience that I’m writing it up here for wider distribution.

Up until and through the 1800s, city fires were a great hazard. Neighborhoods were full of densely packed wooden structures without flame-retardant chemicals, fire alarms, or sprinkler systems; open flames were used everywhere for lighting, heating, and cooking; there were no best practices in place for storing or handling combustible materials; fire departments lacked training and discipline, and they worked with inadequate equipment and insufficient water supply. All this meant that large swaths of cities regularly burned to the ground: Rome in AD 64; Constantinople in 406; London in 1135, 1212, and 1666; Hangzhou 1137; Amsterdam 1421 and 1452; Stockholm 1625 and 1759; Nagasaki 1663; Boston 1711, 1760, 1787, and 1872; New York 1776, 1835, and 1845; New Orleans 1788 and 1794; Pittsburgh 1845; Chicago 1871; Seattle 1889; Shanghai 1894; Baltimore 1904; Atlanta 1917; and Tokyo 1923 are just a short list of the most well-known.

Fire is not unknown today, but it is far less lethal, and great city fires consuming multiple blocks are largely a thing of the past. Today, if you see a fire truck on the street with its sirens blaring, it is more likely to be responding to an emergency medical call than to a fire. Even if the truck is responding to a fire call, it is more like likely to be a false alarm than an actual fire.

How was this achieved?

Better fire-fighting. Pumps to douse fires with water have existed since antiquity, but for most of history they were man-powered. With the Industrial Revolution, we got steam-powered and later diesel-powered pumps that can deliver much greater throughput of water, and at greater muzzle velocities to reach higher floors of buildings. In the 20th century, horse-drawn fire engines were replaced with fire trucks that could get around the city faster and more reliably.

A high-throughput engine, however, needs a high-volume source of water. In ancient and medieval times, water was provided by the bucket brigade: two lines of people stretching from the fire to the nearest lake or river, passing buckets by hand in both directions. A much better solution was the fire hose, invented in the late 1600s (and improved in strength and reliability over the centuries through better materials, manufacturing, quality control). The fire hose not only allowed a fire engine to be connected to a water source, it also allowed the fire-fighters to get in closer to the base of the fire and dump water directly on it, which is far more effective than just spraying the building from the outside.

A fire hose can be inserted into a natural water source like a pond or cistern, but one of these might not be handy nearby, and they aren’t pressurized, so all the pumping force has to be supplied by the fire engine. They also contain debris that can clog the intake and block the flow. Eventually, cities were outfitted with regularly spaced fire hydrants connected to the municipal water supply. A water system designed to supply city residents with daily needs, however, often proved inadequate in an emergency; these systems had to be upgraded to supply the large bursts that big fires demanded. This is a matter of serious engineering: 19th-century fire-fighting journals are full of technical details and mathematical calculations attempting to precisely nail down questions of optimal hydrant distribution or nozzle size, or the pressure required to force a certain volume of water to a given height at a particular angle.

Finally, fire-fighting teams needed improved organization. Traditionally, fire-fighters were volunteers, often rowdy young men with no training or discipline (there is at least one story of a fist fight breaking out between two rival teams who arrived at a fire at the same time). In the 19th century, fire departments were professionalized and were organized more formally, along almost military lines, as befits responders to a life-threatening emergency.

Faster alarming. Fire, like many of our most dangerous hazards, is a chain reaction. Chain reactions grow exponentially, which means early detection and response time are crucial. Traditionally, fires were spotted by watchmen, either on patrol or from a watch tower, who then had to run, shout, or ring bells or other alarms to alert the fire fighters.

Electronic communications, first via telegraph and later telephone, provided a much faster way to get the alarm to the fire department. The telephone lines could be busy, however, so in the 20th century the 911 emergency response system was created to provide a priority channel.

Far better than having a human sound the alarm, however, is doing it automatically. Smoke detectors and other automatic fire alarms caused the fire to “tell on itself,” saving valuable minutes or even hours. Even more effective was the automatic sprinkler, which combined detection and response into one near-instant system.

Reducing open flames. Better than fighting fires, of course, is preventing them. Before the 20th century, flames from candles and oil or gas lamps provided lighting, and fires in wood- or coal-burning stoves provided heat for building, cooking, and industrial processes. The Great London Fire of 1666 is said to have started in a baker’s shop, Copenhagen 1728 was blamed on an upset candle, Pittsburgh 1845 came from an unattended fire in a shed. Even worse, people often kept these fires going unattended overnight, because even starting a fire was difficult before the invention of matches. Medieval regulations required city- and town-dwellers to cover their fires after a certain hour (the word “curfew” derives from the French couvre-feu, “cover the fire”).

Electric lighting and heating greatly reduced this risk. Electric sparks, however, were also a fire hazard—and initially, electrical installations increased rather than decreased fire risk, owing to shoddy electrical products, fixtures, and wiring. The solution here was improved standards, testing, and certification: the fire insurance companies created an organization, Underwriters Laboratories, specifically for this purpose, and its label became a highly valued marker of quality. (I told the story of UL in The Techno-Humanist Manifesto.) Today, our electronics and appliances are so safe that arson is the cause of more fires than either of them.

Safer construction. Preventing fires by eliminating the sparks or flames that ignite them is like lining up dominoes and then trying hard to make sure the first one never gets tipped over: a fragile proposition. Far more robust is to remove their fuel. Wood construction was widespread through the late 19th century, even in dense city neighborhoods: Daniel Defoe wrote that before the Great London Fire of 1666, “the Buildings looked as if they had been formed to make one general Bonfire.”

Today our cities are built of incombustible brick, stone, and concrete. Building codes enforce safety practices to slow the spread of fire both within a building and between buildings. They specify the quality of materials such as brick, mortar, cement, timber, and iron, including the specific tests it must pass; the materials for walls, and their minimum thickness; and the height of non-fireproof structures; among many other details.

Saving lives. By the early 1900s, in advanced societies, the problem of large city fires that spread over many blocks had mostly been solved; fires were often contained to a single building. That was small comfort, however, for those trapped inside the building. Tragedies such as the Iroquois Theatre Fire of 1903 and the Triangle Shirtwaist Fire of 1911 taught us valuable lessons. Exit paths must be adequate to evacuate entire buildings. Doors must remain unlocked, and they should open outwards in case a stampede presses up against them. Fire-resistant material must be used not only for the construction of the building, but for the interior: sofas, beds, curtains, carpets, wallpaper, paneling. Again, building and safety codes specify and enforce these practices.

So fire safety was achieved through the combination of:

• General-purpose technologies: engines, electronic communications, electric light and heat
• Specific inventions: fire pumps, fire hose, fire alarms
• Infrastructure: municipal water supply, telephone lines
• Standards, testing and certification: of electrical products, fire preventing and fire-fighting equipment, building materials, etc.
• Law: building codes and other fire safety codes
• Education and training: in fire departments, among the public

This is a general pattern. Safety requires:

• both prevention and “cure”
• both technical and social solutions
• among technical solutions, both products and systems
• among social solutions, both education and law

We see the same thing in other domains. Road safety, for instance, was achieved through seat belts, anti-lock brakes, crumple zones, air bags, turn signals, windshield wipers, traffic lights, divided highways, driver’s education, driver’s licensing, and moral campaigns against drunk driving. No silver bullet.

When we think about creating safety and resilience from emerging technologies, such as AI or biotech, we should expect the same pattern. Safety will be created gradually, incrementally, through multiple layers of defense, and by orchestrating a wide combination of products, systems, techniques, and norms.

In particular, there is a line of thinking within the AI safety community that tends to dismiss or reject any proposal that isn’t ultimate—fully robust against the most powerful imaginable AI. There’s a good rationale for this: it’s easy to fall victim to hope and cope, and to lull ourselves into a false sense of security based on half-measures that were “the best we could do”; vulnerabilities are often invisible and are revealed dramatically in disasters; such disasters may be sufficiently catastrophic that we can’t afford to learn from mistakes. But I find the all-or-nothing thinking about AI safety counterproductive. We should embrace every idea that can provide any increment of security. History suggests that the accumulation and combination of such incremental solutions is the path to resilience.

Selected sources and further reading:

• Bruce Hensler, Crucible of Fire (2011)
• Harry Chase Brearley, The History of the National Board of Fire Underwriters (1916) and Symbol of Safety (a history of Underwriters Labs, 1923)
• Dennis Nolan, Fire Fighting Pumping Systems at Industrial Facilities (2011)
• W. Fred Conway, Those Magnificent Old Steam Engines (1996)
• Ramon Klitzke, “Roman Building Ordinances Relating to Fire Protection” (1959)
• Lionel Frost and Eric Jones, “The fire gap and the greater durability of nineteenth century cities” (2007)
• John Rainbird, “The Vigiles of Rome”
• Alex Tabarrok, Firefighters Don’t Fight Fires

Historical and primary sources:

• Charles Frederick T. Young, Fires, Fire Engines, and Fire Brigades (1866)
• James Bugbee, “Fires and Fire Departments” (1873)
• James Braidwood, “On the Means of rendering large supplies of Water available in cases of Fire; and on the application of manual power to the working of fire engines” (1844)
• Report of the Commissioners Appointed to Investigate the Cause and Management of the Great Fire in Boston (1873)
• Clarence Goldsmith, “The Use of Pumpers at Fires” (1930) and “Efficient Utilization of Water for Fire Fighting” (1939)
• Journal of the New England Water Works Association, Vol 7 Issue 1
• National Board of Fire Underwriters, Model Building Code (1905)
• Maurice Webster, “What is ‘Fireproof?’” (The Atlantic, 1946)
• FEMA, “America Burning” (report)
• Charles II, An Act for rebuilding the City of London (1666)

I think this is true but irrelevant.

Consider the weather, a prime example of a complex system. We can predict the weather to some extent, but not far out, and even this ability is historically recent. We still can’t control the weather to any significant degree. And yet we are far less at the mercy of the weather today than we were through most of history.

We achieved this not by controlling the weather, but by insulating ourselves from it—figuratively and literally. In agriculture, we irrigate our crops so that we don’t depend on rainfall, and we breed crops to be robust against a range of temperatures. Our buildings and vehicles are climate-controlled. Our roads, bridges, and ports are built to withstand a wide range of weather conditions and events.

Or consider an extreme weather event such as a hurricane. Our cities and infrastructure are not fully robust against them, and we can’t even really predict them, but we can monitor them to get early warning, which gives us a few days to evacuate a city before landfall, protecting lives.

Or consider infectious disease. This is not only a complex system, it is an evolutionary one. There is much about the spread of germs that we can neither predict nor control. But despite this, we have reduced mortality from infectious disease by orders of magnitude, through sanitation, vaccines, and antibiotics. How? It turns out that this complex system has some simple features—and because we are problem-solving animals endowed with symbolic intelligence, we are able to find and exploit them.

Almost all pathogens are transmitted through a small number of pathways: the food we eat, the water we drink, the air we breathe, insects or other animals that bite us, sexual contact, or directly into the body through cuts or other wounds. And almost all of them are killed by sufficient heat or sufficiently harsh chemicals such as acid or bleach. Also, almost none of them can get through certain kinds of barriers, such as latex. Combining these simple facts allows us to create systems of sanitation to keep our food and water clean, to eliminate dangerous insects, to disinfect surfaces and implements, to equip doctors and nurses with masks and gloves.

For the infections that remain, it turns out that a large number of bacterial species share certain basic mechanisms of metabolism and reproduction, which can be disrupted by a small number of antibiotics. And a small number of pathogens once caused a large portion of deaths—such as smallpox, diphtheria, polio, and measles—and for these, we can develop vaccines.

We haven’t completely defeated infectious disease, and perhaps we never will. New pandemics still arise. Bacteria evolve antibiotic resistance. We can sanitize our food and water, but not our air (although that may be coming). But we are far safer from disease than ever before in history, a trend that has been continuing for ~150 years. Even if we never totally solve this problem, we will continually make progress against it.

So I think the idea that we can’t control complex systems is just wrong, at least in the ways that matter to human existence. Indeed, a key lesson of systems engineering is that a system doesn’t need to be perfectly predictable in order to be controllable, it just has to have known variability.¹ We can’t predict the next flood, but we can learn how high a 100-year flood is, and build our levees higher. We can’t predict the composition of iron ore or crude oil that we will find in the ground, but we can devise smelting and refining processes to produce a consistent output. We can’t predict which germs will land on a surgeon’s scalpel, but we know none of them will survive an autoclave.

So we can tame complex systems, and achieve continually increasing (if never absolute or total) mastery over nature. Our success at this is part of the historical record, since most of progress would be impossible without it. The “complex system” objection to the goal of mastery over nature simply doesn’t grapple with these facts.

So here’s mine. At least I can say I’ve been doing it for as long as Dan: nine years running (proof: 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024). As usual, this is more of a personal essay/reflection, and not so much of an organizational annual report, although I will start with some comments on…

RPI

Over the last three years, the Roots of Progress Institute has gone from “a guy and his blog” to a full-fledged cultural institute. This year we:

• Held our second annual Progress Conference, featuring speakers including Sam Altman, Blake Scholl, Tyler Cowen, and Michael Kratsios (Director, OSTP). The conference has become the central, must-attend event for the progress community: it is sold out each year, with hundreds on the waitlist, and some attendees report it is literally the best conference they have ever attended.
• Inducted the third cohort of our progress writers fellowship, bringing the total to 74 fellows. Our fellows are having impact: Dean Ball helped draft the Trump administration’s AI Action Plan, Madeline Hart has co-authored a book with the CTO of Palantir on revitalizing the American defense industry, Ryan Puzycki helped legalize single-stair buildings in Austin (a key YIMBY reform), and three other fellows have recently had opinion pieces in the NYT or WSJ.
• Announced our first education initiative: Progress in Medicine, a high school summer career exploration program. I’ve previewed the content for this course and I’m jealous of these kids—I wish I had had something like this when I was a teenager!

And the best part about all of these programs is that I don’t have to run any of them! I have a fantastic staff at RPI who deserves credit for all of these, from design to execution: Emma McAleavy, Ben Thomas, Yel Alonzo, and especially Heike Larson—thanks to them for making our programs a success every year.

We’re a 501(c)(3) nonprofit, supported mostly by donations. There’s still time to get in a last-minute end-of-year contribution! The simplest way to support us is to upgrade to a paid (or founding!) subscription.

Or see here for other ways to support us.

Huge thanks to all those who have already given this year!

My writing

Most of my writing effort this year was devoted to finishing The Techno-Humanist Manifesto, an essay-series-cum-book laying out my philosophy of progress. In 2025 I published the last 14 (out of 21) essays in the series, you can read them all here. Also, as just announced, I’ve signed with MIT Press to publish a revised version of the series in book form. The manuscript is out for comment now, and (given typical publishing schedules) I expect the book to launch in early 2027.

I also wrote eight other essays, and ten links digests. I put the links digest on hold after May in order to focus on finishing the book, but I’m working on bringing it back. All subscribers get the announcements and opportunities at the top, but the rest of the digest is paywalled, so subscribe now to get the full version.

The most-liked posts here on Substack were:

• The future of humanity is in management
• How sci-fi can have drama without dystopia or doomerism
• The Unlimited Horizon, part 2
• The Spirit We Lost, part 1
• In defense of slop

The most-commented posts were:

• How much does it cost to back up solar with batteries?
• We should install a thermostat on the Earth
• Where is the YIMBY movement for healthcare?

My longest post, at over 8,400 words, was:

• The Progress Agenda

I now have well over 55,000 subscribers on Substack, up over 68% YOY.

Social media

Here are some of my most-liked posts and threads of the year:

• One model for Elon is that he is perpetually operating in wartime mode: Move as fast as possible, bring overwhelming force, extract superhuman effort, accept collateral damage. A thread. For some reason many people seemed to think I was praising or defending this: I wasn’t, just observing.
• Grocery stores have price transparency and open competition, which health services don’t (replying to a wrong-headed comment by Rep. Jake Auchincloss)
• Everything has to be invented—even buttons
• The moment the Boom XB-1 test plane went supersonic
• “Daddy, why is a hundred a big number?”, and other difficult questions from my 3yo
• “On paper, titanium should be the world’s #1 structural metal”
• When Tyler Cowen just flat-out says that tariffs are bad, you know they are very straightforwardly bad
• A great moment from a legendary interview with Morris Chang of TSMC, on the Acquired podcast
• Waymo achieves 80–90% reduction across all crash/injury metrics. If there were some intervention that achieved this, safety advocates would be demanding its wholesale adoption immediately, even if it were costly or inconvenient

You can join well over 40,000 people who follow me on Twitter, or find me on your favorite social network; I’m on pretty much all of them.

Speaking and events

Like last year, I tried to mostly say no to events and speaking gigs this year, but there were a few I couldn’t refuse. Some highlights of the year:

• I spoke at “d/acc Day” alongside Vitalik Buterin, Juan Benet, Mary Lou Jepsen, Allison Duettmann, and others. My talk was “d/acc: The first 150 years”: a whirlwind tour of how society has thought about progress, decentralization and defense over the last century and a half
• I gave a short talk at Social Science Foo Camp titled “The Fourth Age of Humanity?”, based on ideas that I later wrote up in The Flywheel
• I did a fun Interintellect salon with Virginia Postrel based on her essay “The World of Tomorrow”
• I hosted a discussion series at Edge Esmeralda with the aim of envisioning the future. Each day there was a ~90-minutes session with a theme like AI, health & bio, or energy
• I went to Mojave to watch the first supersonic flight of the Boom XB-1 test plane. Here’s some video I took of the plane taxiing down the runway, and then the pilot getting out after landing and shaking hands with Boom founder Blake Scholl

In 2026 I hope to do more travel, events and speaking. But maybe I’ll just hole up and write some more.

Reading

I put my monthly “what I’ve been reading” updates on hold at the end of 2023 (!) in order to focus on the book. I’d like to bring these back, too. For now, here are some the highlights from my reading this year (that is, things I thought were interesting and valuable to read, not necessarily things I “liked” or agreed with).

The first few book recommendations are free, paid subscribers get the (much longer) full reading update and (below) some thoughts on what’s next for my writing:

Books and other book-length things I read

Or read at least most of:

Max Bennett, A Brief History of Intelligence. A history of the evolution of the brain, from the first animals through humans. It is organized into five major evolutionary steps—to oversimplify: the worm brain, the fish brain, the mouse brain, the monkey brain, and the human brain. This answered some key questions I had on the topic, very well-written, probably my favorite of the year. Hat-tip to @eshear.

Charles Mann, How the System Works, an essay series in The New Atlantis. It covers four of the major systems that form the foundation of industrial civilization and help deliver our modern standard of living: agriculture, water sanitation, electricity, and public health. Mann thinks of these pieces as the start of a curriculum that should be taught in schools—inspired by a group of “smart, well-educated twenty-somethings” who “wanted the hungry to be fed, the thirsty to have water, the poor to have light, the sick to be well,” but “knew little about the mechanisms of today’s food, water, energy, and public-health systems. They wanted a better world, but they didn’t know how this one worked.” Enjoyed this, recommended.

Brian Potter, The Origins of Efficiency, from Stripe Press, a history of manufacturing efficiency. Light bulbs used to cost ~$50 (adjusted for inflation), now they cost 50 cents; how did that happen? This is a comprehensive and very readable overview of the answer to that question and others like it.

To read the rest, subscribe on Substack.

“Techno-humanism” is my philosophy of progress, and THM is my statement of it. It consolidates and restates material I’ve used in previous essays and talks, in a more unified and coherent form. Still, even for my biggest fans, almost every chapter should have something new, including:

• The culture of progress we once had (pre-WW1), and the decline of the idea of progress in the 20th century
• The story of progress as a story of the expansion of human agency (despite seeming counterexamples like the poor nutrition of early agriculturalists or the inadvertent creation of new health and environmental hazards)
• The nature of human well-being, including my response to the paradox of stagnant happiness metrics
• My argument for radical anthropocentrism, against romantic environmentalism and in particular against the idea of any intrinsic value in nature; and my take on stopping climate change, reframing the goal as creating climate control
• The pattern of accelerating progress and what drives it; related, my take on “ideas getting harder to find”
• Some stories of unsung heroes of health and safety
• My vision for the technological future
• The progress agenda—the cause areas of the progress movement today
• How progress can be a grand project for humanity, and how it can give us a heroic ideal to emulate

I’m pleased to announce that the series will be revised for publication as a book from MIT Press. The manuscript is out for comment now, and (given typical publishing schedules) I expect the book to be available in early 2027. Stay tuned!

I got so busy writing The Techno-Humanist Manifesto this year that after May I stopped doing the links digest and my monthly reading updates. I’m bringing them back now (although we’ll see what frequency I can keep up). This one covers the last two or three weeks. But first…

A year-end call to support our work

I write this newsletter as part of my job running the Roots of Progress Institute (RPI). RPI is a nonprofit, supported by your subscriptions and donations. If you enjoy my writing, or appreciate programs like our conference, writer’s fellowship, and high school program, consider making a donation:

• If you can give $100, upgrade to an annual Substack subscription

• If you can give $500, make it a founder subscription

• If you can give $1000 or more, support us on Patreon, or see here for PayPal and other methods, including DAF and crypto

To those who already donate, thank you for making this possible! We now return you to your regularly scheduled links digest…

Much of this content originated on social media. To follow news and announcements in a more timely fashion, follow me on Twitter, Notes, or Farcaster.

Contents

• Progress in Medicine, a career exploration summer program for high schoolers
• Progress Conference 2025
• My writing
• From RPI fellows
• Jobs
• Grants & fellowships
• Events
• Miscellaneous opportunities
• Queries
• Announcements

For paid subscribers:

• What is worthy and valuable?
• Claude’s soul
• Self-driving cars are a public health imperative
• Slop from the 1700s
• The genius of Jeff Dean
• Everything has to be invented
• AI
• Manufacturing
• Science
• Health
• Politics
• Other links and short notes

Progress in Medicine, a career exploration summer program for high schoolers

We recently announced a new summer program for high school students: “Discover careers in medicine, biology, and related fields while developing practical tools and strategies for building a meaningful life and career—learning how to find mentors, identify your values, and build a career you love that drives the world forward.”

I’ve previewed the content for this course and I’m jealous of these kids—I wish I had had something like this. We’re going to undo the doomerism that teens pick up in school and inspire them with an ambitious vision of the future.

Applications open now. Please share with any high schoolers or parents.

Progress Conference 2025

• Our writeup: Reflections on Progress Conference 2025
• Big Think released a special issue after the conference, “The Engine of Progress,” featuring articles from Boom CEO Blake Scholl, futurist Peter Leyden, and six RPI fellows

• We’ve also started to release video of the talks, including:

• Tyler Cowen interviewing Sam Altman and Blake Scholl
• AI Protopia: Ideas for how AI can improve the world (track)
• New cities, housing policy, and lessons from the YIMBY movement (track)
• More to come!

My writing

• “Progress” and “abundance”: “Abundance” tends to be more wonkish, oriented towards DC and policy. “Progress” is interested in regulatory reform and efficiency, but also in ambitious future technologies, and it’s more focused on ideas and culture. But the movements overlap 80–90%
• In defense of slop: When the cost of creation falls, the volume of production greatly expands, but the average quality necessarily falls. This overall process, however, will usher in a golden age of creativity and experimentation

From RPI fellows

• Ruxandra Teslo (RPI fellow 2024) and Jack Scannell have written “a manifesto on reviving pharma productivity … Public debates focus on improving science or loosening approval. We argue there’s real leverage in optimizing the middle part of the drug discovery funnel: Clinical Trials.” (@RuxandraTeslo) Article: To Get More Effective Drugs, We Need More Human Trials. Elsewhere, Ruxandra comments on the need for health policy to focus more on the supply side, saying: “The reason why I felt empowered to propose things related to supply-side is because of the ideological influence of the Progress Studies movement (Roots of Progress, Jason Crawford)” (@RuxandraTeslo)
• Dean Ball (RPI fellow 2024) interviewed by Rob Wiblin on the 80,000 Hours Podcast. Rob says of Dean that “unlike many new AI commentators he’s a true intellectual and a blogger at heart — not a shallow ideologue or corporate mouthpiece. So he doesn’t wave away concerns and predict a smooth simple ride.” (@robertwiblin) Podcast on Apple, YouTube, Spotify
• Andrew Miller writes for the WSJ about the inevitable growing pains of adopting self-driving cars: Remember When the Information Superhighway Was a Metaphor? (via @AndrewMillerYYZ)

Jobs

• Astera Neuro (just announced, see below!) is looking for a COO: “This is an all-hands-on-deck effort as we build a new paradigm for systems neuroscience” (@doristsao)
• Astera Institute is also hiring an Open Science Data Steward “to help our researchers manage, share, and facilitate new solutions for their open data” (@PracheeAC)
• Monumental Labs is hiring two Business Development VPs: “One will focus on large-scale building projects and city developments. Another will focus on developing new markets for stone sculpture, including public sculpture, landscape etc.” (@mspringut)
• Jason Kelly at Ginkgo Bioworks is “personally hiring for scientists that are automation freaks. Not that you run a high throughput screening platform but rather that you believe we should automate all lab work” (@jrkelly)
• Lulu Cheng Meservey is hiring a “puckish troublemaker” for special projects. “This is a real job with excellent pay, benefits, and budget. Your responsibilities will be to conceive of interesting ideas and make them happen in the real world, often sub rosa” (@lulumeservey)

Grants & fellowships

• Edison Grants from Future House to run their AI-for-science tools: “Today, we’re launching our first round of Edison Grants. These fast grants will provide 20,000 credits (100 Kosmos runs) and significant engineering support to researchers looking to use Kosmos and our other agents in their research.” (@SGBodriques)
• Foresight Institute’s AI Nodes for Science & Safety: “If you’re working on AI for science or safety, apply for funding, office space in Berlin & Bay Area, or compute by Dec 31!” (@allisondman via @foresightinst)

Events

• I’ll be speaking at The Festival of Progressive Abundance, LA, Jan 30–Feb 1 (@YIMBYDems)
• The Economics of Ideas, Science, and Innovation Online short course for PhD students, hosted by IFP, is back for the third time (@mattsclancy). Online, Feb 3–April 30

Miscellaneous opportunities

• a16z Build: “A dinner series and community for founders, technologists, and operators figuring out what they want to build next — and who they want to build it with. … It’s not an accelerator, or even a structured program. … Instead, we focus on one thing: creating small, repeatable environments where people with ambition, ability, and similar timing spend enough time together that trust compounds, decisions get easier.” (@david__booth)
• Vast’s Call for Research Proposals: “Vast is opening access to microgravity research aboard Haven-1 Lab, the world’s first crewed commercial space-based research and manufacturing facility” (@vast, h/t @juanbenet)
• A long-running project with HBO to make a series about the early days of Elon Musk and SpaceX has died. The series was based on Ashlee Vance’s biography, and he’s still interested in doing something with this: “If there are serious offers out there to make something amazing, my mind and inbox are open” (@ashleevance)
• Manjari Narayan (@NeuroStats) is looking for a co author to collaborate on one or more explainers about surrogate endpoints and other proxies in health and bio—including why we waste time and money on those that don’t work and how we can do better. She is the domain expert, all you have to bring is the ability to make technical topics readable and accessible to a non-specialist audience. Reply or DM me and I’ll connect you

Queries

• “It’s ‘well-known’ that science is upstream of abundance… I’ve found it surprisingly difficult to find strong general discussion of this link between science and our ability to act. … The best discussions I know are probably Solow-Romer from the economics literature, and Deutsch (grounded in physics, but broader). What else is worth reading?” (@michael_nielsen)

Announcements

• NSF launches a Tech Labs Initiative “to launch and scale a new generation of transformative independent research organizations to advance breakthrough science.” Caleb Watney, writing in the WSJ, calls it “one of the most ambitious experiments in federal science funding in 75 years. … the goal is to invest ~$1 billion to seed new institutions of science and technology for the 21st century.” (@calebwatney) Seems like big news!
• Astera Neuro launches, a neuroscience research program led by Doris Tsao. “We’re seeking to understand how the brain constructs conscious experience and what those principles could teach us about building intelligence. Jed McCaleb and I are all-in on this effort.” (@seemaychou)
• Ricursive Intelligence launches, “a frontier AI lab creating a recursive self-improving loop between AI and the hardware that fuels it. Today, chip design takes 2-3 years and requires thousands of human experts. We will reduce that to weeks.” (@annadgoldie) Coverage in the WSJ: This AI Startup Wants to Remake the $800 Billion Chip Industry
• Boom Supersonic launches Superpower: “a 42MW natural gas turbine optimized for AI datacenters, built on our supersonic technology. Superpower launches with a 1.21GW order from Crusoe.” (@bscholl) Aeroderivative generator turbines are not new, but Boom’s has much better performance on hot days
• Cuby launches “a factory-in-a-box” for home construction: “a mobile, rapidly deployable manufacturing platform that can land almost anywhere and start producing home components locally. … Components are manufactured just-in-time, packaged, palletized, and sent last-mile for staged assembly. … Full vertical integration from digital design → factory → site.” (@AGampel1) I’m still unclear whether this is going to be the thing that finally works in this space, but Brian Potter is a fan, which is a strong signal!
• OpenAI announces FrontierScience, a new eval that “measures PhD-level scientific reasoning across physics, chemistry, and biology” (@OpenAI)
• Antares raises a $96M Series B “to build and deploy our microreactors … paving the way for our first reactor demonstration in 2026. Two years in: 60 people, three states, a 145,000-sq-ft facility, and contracts across DoW, NASA, and others” (@AntaresNuclear)
• GPT-5.2 Pro (X-High) scores 90.5% on the ARC-AGI-1 eval, at $11.64/task. “A year ago, we verified a preview of an unreleased version of OpenAI o3 (High) that scored 88% on ARC-AGI-1 at est. $4.5k/task … This represents a ~390X efficiency improvement in one year” (@arcprize)

To read the rest, subscribe on Substack.