2025: My Year in Books

Reading kept me sane in 2025. Between two young children, a hectic travel schedule, and an industry in the throes of transformation, books were the constant. These aren’t all the books I read this year, and not all these books were published in 2025. These are just the ones that stuck with me.

Non-Fiction

  • Apple in China: The Capture of the World’s Greatest Company by Patrick McGee
  • Breakneck: China’s Quest to Engineer the Future by Dan Wang
  • The Nvidia Way: Jensen Huang and the Making of a Tech Giant by Tae Kim
  • The Golden Road: How Ancient India Transformed the World by William Dalrymple
  • Destiny Disrupted: A History of the World Through Islamic Eyes by Tamim Ansary

Fiction

  • There Is No Antimemetics Division by qntm
  • Between Two Fires by Christopher Buehlman
  • The Loneliness of Sonia and Sunny by Kiran Desai

Non Fiction

Building the Modern World

One strand of my non-fiction reading this year was understanding how the modern technology ecosystem actually functions. Not the startup mythology or the investor narratives, but the physical reality of how complex devices get designed, manufactured, and shipped.

Reading Apple in China made me realize just how complex the supply chains and manufacturing capabilities required to build devices like iPhones are. Images of Apple engineers spending days and weeks on assembly lines, fine-tuning machines and processes to build the slab of metal and glass in my pocket, stayed with me after I finished the book. McGee’s observations of colorful characters like Foxconn founder Terry Gou gave me an appreciation of the Chinese entrepreneurs who invested alongside Apple, giving us the modern electronics industry.

Breakneck by Dan Wang was an excellent companion piece. Wang contrasts the “engineering-focused” approach of China against the “litigation-focused” approach of the United States. Wang walks factory floors and rides high-speed trains while making a sustained argument about how countries build technological capacity. His comparison of how the two countries approach intellectual property and innovation is particularly sharp.

Tae Kim takes a different approach entirely in The Nvidia Way. Where McGee focuses on systems and supply chains, Kim writes biography. The book is as much about Jensen Huang as it is about Nvidia’s history and culture. Kim traces how Nvidia came to dominate the PC gaming industry before pivoting to AI and the datacenter. The Nvidia story is optimistic: a company that nearly died multiple times, led by an intense and sometimes abrasive founder, that happened to build exactly the right technology at exactly the right moment. If you want to understand why AI development has accelerated so dramatically, understanding Nvidia’s journey helps.

Many Journeys

Another strand of my reading was history. I’ve had a long-standing interest in Indian history, and William Dalrymple’s The Golden Road offered an unexpected view into pre-Mughal, pre-Islamic India. Dalrymple traces how Indian ideas, religions, and material culture spread across Asia and shaped civilizations from Indonesia to Japan.

Perhaps the most interesting part of The Golden Road was Dalrymple’s telling of the Chinese monk Xuanzang’s journey to India to collect authentic Buddhist scriptures. His journey is the basis of Journey to the West, a story that I also enjoyed reading this year. I think Xuanzang’s journey is as interesting and full of intrigue as that of Tang Sanzang in Journey. The India Xuanzang visited was chaotic, with the old Buddhist empires falling apart and the emergence of Hindu and soon Islamic empires. This theme of journeys undertaken in times of chaos is something I came across repeatedly in my reading this year.

Tamim Ansary’s Destiny Disrupted allowed me to fill in the blanks of my own education. In small-town India, the history of Islam is either the glory of Akbar or the tyranny of villains like Timurlane. Destiny Disrupted provided a much wider view of what was happening in the Middle East: the slow fading of the Byzantine empire, the emergence of local powers in Arabia and Central Asia, and the many wonderful characters who play central roles in the spread of Islam.

Next year, I plan to focus on early-medieval Europe and South America.

Fiction

Existential Dread, Cosmic Horror, and a Tender Love Story

I read less fiction than I normally do this year. The three books that stayed with me span genres: science fiction, horror, and literary fiction.

I love science fiction, and qntm’s There Is No Antimemetics Division hit all the right notes. An engaging plot, elements of both hard science fiction and cosmic dread, and a non-linear narrative that rewards attention. The premise involves a secret division of a shadowy organization that fights entities which cannot be remembered. The horror isn’t in the monsters; it’s in the systematic erasure of the knowledge that monsters exist.

Christopher Buehlman’s Between Two Fires is set in a France ravaged by both the Hundred Years’ War and the Black Death. It also has a demonic infestation. Thomas, a disgraced knight, and Delphine, a young girl who may be a saint, journey to a demon-haunted Avignon. Buehlman’s prose is excellent, and his depiction of fourteenth-century France feels genuinely medieval rather than cosplay.

Kiran Desai’s The Loneliness of Sonia and Sunny is a sprawling and beautifully written love story that is also an incisive study of the immigrant experience and an evisceration of upper-class Indian values. The book layers trauma upon trauma: the partition generation still processing displacement decades later, the loneliness and alienation of immigrants far from home, abusive relationships that distort both parties. And yet it remains, at its core, a love story. It’s a hard book to summarize because Desai’s sentences do so much work.

Navigating Chaos

The theme connecting these three fiction books only became clear to me after I finished them. Thomas and Delphine journey through a France that is literally going to hell. Quinn, the protagonist of Antimemetics, repeatedly confronts horrors that erase themselves from memory, forcing her to rediscover threats she has already defeated. Sonia and Sunny navigate changing countries and cultures while growing from passive, somewhat spoilt twenty-somethings into adults with agency, forced to reckon with inherited and inflicted trauma alike.

Each book finds its protagonists in a chaotic world that seems to be coming apart. They cope, they fight, they sometimes fail. The rules keep changing.

I don’t think my fiction choices were accidental.

My Year in Reading

Reading The Nvidia Way and my fiction picks in the same year created an interesting tension. Kim’s book is a story of technological optimism. Jensen Huang bet on parallel computing when the market didn’t exist, nearly bankrupted his company multiple times, and emerged as the most important hardware supplier for the AI revolution. It’s inspiring. It suggests that talent, persistence, and technical insight can build something transformative.

My fiction picks suggest a different mood. The world is confusing. Threats are hard to identify and harder to remember. The rules keep changing. You navigate as best you can.

Both feel true to me. I work in technology. I’ve spent this year helping teams adopt AI tools and watching the capabilities expand month by month. The optimism is warranted. And yet the speed of change creates its own kind of vertigo. The skills I’ve built over two decades may or may not transfer to whatever comes next. The existential dread in my fiction choices probably reflects something real about how I experience this moment.


Note

My love of reading manifested as QuietReads this year, an AI-powered reading tracker I’ve been building. Using it to track and discuss books like The Loneliness of Sonia and Sunny with its AI assistant deepened my appreciation for what Desai was doing. Building something that helps me think about what I read has been its own kind of pleasure. I look forward to working on it in the new year.

2025: The Year I Became A Cyborg

In chemistry, activation energy is the minimum energy required to start a reaction. It’s the barrier between potential and action, between “I could” and “I did.”

This year, AI collapsed that barrier for me.

As foundation models became better, and the tools built on top of them became more useful, the gap between having an idea and acting on it shrank to almost nothing. And for someone whose natural disposition is to try things, to experiment, to see what happens, this has been transformative. I have embraced using AI for work and play and for much else. 

Image generated using Gemini Pro

From Thought to Artifact

I’ve written more consistently this year than ever before. 

For many years, I used to maintain a list of ideas that I wanted to explore. Bookmarked sites, academic papers, and spicy social media takes. These ideas often were just abandoned or ignored until I forgot why I wrote them down in the first place.

Now, the time between having an idea, doing the research, writing an outline and then publishing it online has shrunk significantly because of AI. I use skills, deep research agents, and a set of prompts that have let me express myself faster and more coherently than ever before. 

My recent post “The Same Window For Everything” exists because I noticed something interesting while reading Kiran Desai, opened Claude to think it through, and found myself with the skeleton of an essay. A year ago, that observation might have stayed in my head, filed away with all the other thoughts that never quite made it to the page.

There’s a passion project I’ve been building, a reading companion I’ll be launching soon. It exists because, in 2025, the distance from “what if I built this?” to “let me try” became trivially small. Just like my writing ideas, I have a huge list of side projects and experiments that I wanted to try but never got off the ground. This year, I did.

But, it’s not all serious stuff! I vibe-coded (built quickly with AI assistance) a tool to help me journal regularly. I use AI to help plan dinner for my kids. I have setup my phone so it launches ChatGPT in “search mode” at the press of a button. And, I ask it all kinds of questions! From dealing with my dog’s flatulence to figuring out why the minivan doors won’t open. I now look up things where before I would have just shrugged and moved on.

I have a different relationship now with making things; one where the cost of trying something has dropped low enough that I actually try it.

The Professional Stakes

Looking up recipes for spaghetti carbonara is all well and good, but AI has had a significant impact on my work as well. 

At Jeavio, we’ve taken on more ambitious, outcome-oriented projects. Internal initiatives I sponsor, like our campus programs, have become more ambitious and aggressive because I believe we can get them done. That belief comes from now having enough experience with using AI tools to be confident on what my teams can and should be able to deliver.

We ran a company-wide hackathon late last year and a product-focused one in 2025. The hackathons shifted how Jeavio thinks about and uses AI tooling. They encouraged experimentation and built collective confidence about what capabilities these tools could unlock.

It’s not all fun and cheap inference though. Some projects have been challenging. We’re working at the frontier of what’s possible, and frontiers can be uncomfortable places. 

But my risk appetite has increased. I understand the tools better now. I know what Cursor and Claude Code can do and, equally important, where they fall short. I have a clearer understanding of what guardrails should be in place and how to evaluate the performance of inherently probabilistic systems. That understanding translates into confidence: confidence to take on projects with ambiguity, and confidence to deliver clearer projects faster and more predictably.

The throughline is the same as the personal examples: lower activation energy. Faster exploration, quicker iteration, more willingness to try things that might not work than ever before. For my work at Jeavio, this is an energizing change. 

Cyborgs and Foxes

Two frameworks have helped me make sense of what’s changed.

Ethan Mollick, in his research on AI and knowledge work, distinguishes between Centaurs and Cyborgs. Centaurs maintain a clear division of labor between human and machine, handing off discrete tasks to AI. Cyborgs blend the two. As Mollick puts it:

“Cyborgs don’t just delegate tasks; they intertwine their efforts with AI, moving back and forth over the jagged frontier.”

I’ve become a Cyborg.

AI is woven into how I think, write, and build. When I’m reading and want to explore an idea, I open Claude. When I’m coding and hit a wall, I think through the problem with an AI collaborator. The boundaries between what is truly my work and what is AI-mediated have become somewhat meaningless.

The second framework comes from David Epstein’s book Range: Why Generalists Triumph in a Specialized World. Drawing on Isaiah Berlin’s famous distinction and Philip Tetlock’s research on forecasting, Epstein contrasts hedgehogs, who know one big thing deeply, with foxes, who know many things and integrate broadly. 

Hedgehogs thrive in stable, rule-bound environments. Foxes thrive in ambiguous, rapidly-changing ones. As Epstein writes:

“Foxes see complexity in what others mistake for simple cause and effect. They understand that most cause-and-effect relationships are probabilistic, not deterministic.”

I’ve always been a fox.

Broad curiosity, comfort with ambiguity, a tendency to wander across domains. But being a fox is expensive and risky. Every new domain requires starting from scratch. The activation energy to explore something unfamiliar is high.

AI subsidizes that cost. Becoming a Cyborg helps make my fox-like tendencies viable in ways they weren’t before. I can move into an unfamiliar domain, quickly get oriented, experiment, and learn, all without the friction that used to make such exploration feel indulgent.

These frameworks work on orthogonal dimensions. Cyborg describes how I work. Fox describes who I am. Becoming a Cyborg made me more comfortable leaning into my fox-ness.

Looking Forward

I’m aware this could sound like boosterism. The AI discourse is full of inflated predictions and productivity theater.

So here’s what 2025 has taught me. Becoming a Cyborg works for me. This may not always be true.

Maybe I am just a frog slowly boiling to irrelevance as AI takes away my agency and creativity. 

Maybe the AI bubble might burst, and Anthropic and OpenAI will raise prices making vibe-coding a passion project or having a long conversations about literary fiction non-viable.

But until then: the distance between curiosity and creation has collapsed. I intend to exploit that gap.

More experiments. More wacky things. More small wins and instructive failures. The activation energy is low, and I have a lot of ideas. Bring on 2026.

The Same Window For Everything

I’ve been thinking about how I use AI tools lately. They’re clearly useful. What interests me is how the experience feels.

A few nights ago I was reading Kiran Desai’s The Loneliness of Sonia and Sunny and noticed something interesting. There’s a passage where Sonia, reading Anna Karenina, is overcome by a “tingling” sensation:

“Now Sonia could barely read Anna Karenina because when she read, a tingling overcame her, she so wished to be writing it herself. What a tingle, an almost unbearable, sublime tingle, from head to toe. How many millions of observations and moments it had taken to compose this book! Sonia began to make notes, she wrote descriptions of landscapes, snatches of conversations.”

It struck me that Desai might be revealing her own process through this character. Is Sonia a kind of surrogate? Is Desai, through Sonia’s response to Tolstoy, offering a key to how she sees her own craft?

I wanted to think this through. I opened Claude, pasted the passage, and started a conversation. It was genuinely illuminating. Claude pointed out that the passage reads like “a confession barely disguised as characterization.” The specificity of the physical sensation is a giveaway: writers who haven’t felt that particular ache when confronting great work don’t describe it with such precision. And the passage enacts what it describes. Sonia wants to write like Tolstoy; Desai is showing us she can write like someone who wants to write like Tolstoy. It’s recursive. A kind of metacommentary on the work of being a novelist.

The next morning, I used Claude to help with a deployment problem on a project. Same window. Same prompt box. Same conversational cadence.


There’s something strange about this. Claude (especially Opus 4.5) is amazing: a tool that can move fluidly from literary analysis to infrastructure troubleshooting.

But I notice that I bring the same me to both conversations. The same patterns, the same phrasing, the same mental posture. Whether I’m contemplating themes of self-awareness in a novel or investigating why a Lambda function is timing out, I’m using the same application, the same text box.

The platforms know this is a limitation. Claude has Projects. ChatGPT has custom GPTs. Gemini has Gems.

These features exist because context matters. A conversation about books should draw on what I’ve read before, and a conversation about code should know my stack and preferences.

But notice what’s happening: we’re building elaborate scaffolding around general-purpose tools to make them behave like specialized ones. We’re adapting ourselves to the tool. The center of gravity remains the AI interface itself. Everything orbits around it.


Jim Barksdale, the former CEO of Netscape, once said there are only two ways to make money in business: bundling and unbundling. The line came off the cuff at the end of a grueling IPO roadshow in 1995, when a British investment banker asked how Netscape would respond if Microsoft simply bundled a browser into Windows. Barksdale’s throwaway answer became a kind of axiom.

Technology moves in these cycles. The early web was dispersed into countless specialized sites, then concentrated into platforms like Facebook and Google. Craigslist bundled everything (jobs, housing, dating, selling) until startups like Airbnb and Tinder unbundled each category into dedicated experiences.

In that same HBR conversation, Marc Andreessen observed that when underlying technology shifts, the question becomes: if you sat down today with a clean sheet of paper, knowing the technology was changing, what would be the proper form of the product?

AI feels like it’s deep in a concentration phase.

A handful of general-purpose models, a handful of chat interfaces, a shared assumption that the right approach is to build one very capable thing and let users figure out how to apply it.

I’m curious what a dispersion phase looks like for AI.


I want the same powerful models. What I wonder about is AI experiences that are genuinely embedded in specific contexts.

Software where the intelligence isn’t a chat window bolted onto the side, but integral to what you’re trying to do.

When I’m reading Kiran Desai and want to explore whether Sonia is an authorial surrogate, I don’t want to leave the reading experience to talk to an AI. I don’t want to context-switch into a general-purpose tool, paste in a passage, explain what book I’m reading, and then switch back. I want the exploration to feel like part of reading itself. A deepening.

When I’m debugging infrastructure, I probably want something different. A different interface, a different interaction pattern, a different relationship with the underlying model.

The current generation of AI tools has trained us to be good prompt engineers. We’ve learned to provide context, to frame questions well, to work within the constraints of conversational interfaces. We’ve learned to use Projects and memory features to maintain continuity. This is a skill, and it’s valuable.

But are we building habits around what’s available rather than what’s ideal? We’ve gotten so good at adapting to general-purpose tools that we’ve stopped asking whether purpose-built experiences might be better.


Side note: I know there is a vibrant reading community online. There are meetup groups and book clubs IRL which, I am sure, have stimulating conversations. But, I have a full time job. I have young children. I read when everyone is in bed and the house is quiet. So Claude is my reading buddy. For now.

When reading, the conversations that matter most are the contemplative ones. When I wondered about Desai and Sonia, I wasn’t looking for an answer. I was trying to think, to better understand what Desai was trying to do with this passage. This is materially different from asking for a summary or a recommendation.

But those moments of genuine literary exploration get lost in the same interface where I’m debugging code, drafting emails, or planning trips. The conversation about The Loneliness of Sonia and Sunny sits in my chat history between a thread about Python type hints and a thread about project planning.

General-purpose AI is astonishingly good at being general-purpose.

That’s the point. But have we overcorrected? Have we become so enamored with tools that can do anything that we’ve stopped building tools designed to do specific things well?


I don’t have answers yet. I’m building toward something, experimenting with what a more focused AI experience might feel like. But I know that my conversation about Sonia and Tolstoy deserved a different container than my conversation about Docker issues or how to remote-start my minivan.





Ilya Sutskever, the Scaling Hypothesis, and the Art of Talking Your Book

If you’ve just raised $3 billion to build a new god, it helps to question the faith in the old one.

Ilya Sutskever’s recent appearance on the Dwarkesh Podcast has sparked predictable reactions. Skeptics seized on his statement that “we are back in the age of research” as vindication that the AI hype is overblown. Boosters dismissed the interview as sour grapes from an OpenAI exile. Both camps miss something important: Sutskever is doing what any rational actor in his position would do. He’s talking his book.

But to understand why that matters, we need to understand what he’s actually claiming and the history behind it.

What is the Scaling Hypothesis?

The scaling hypothesis is the foundational bet that powered the modern AI boom. In simple terms: if you make neural networks bigger, train them on more data, and throw more compute at them, they get better.

In 2020, researchers at OpenAI (including Sutskever’s colleagues Jared Kaplan and Sam McCandlish) published a landmark paper demonstrating that language model performance follows power laws. Double your compute, and your model’s loss drops by a predictable amount. The relationship held across seven orders of magnitude. Basically, capabilities scale with compute and data.

This insight transformed AI from a research discipline into an infrastructure race. It explained why companies began raising billions for GPU clusters and why data companies like Scale AI suddenly became worth billions of dollars.

This “scaling hypothesis” justified the massive capital expenditures that would have seemed insane a decade ago. And, despite the sceptics (more on that later), scaling remains a significant driver of cutting-edge model performance.

As of December 3, 2025, Google’s Gemini 3 model is the best publicly available model. And, as Sutskever mentions in the interview, the gains in capabilities are due to improvements in pre-training. So the Scaling Hypothesis may not be dead yet (more on this later).

Note: In this post, I use ‘scaling’ and ‘pre-training’ somewhat interchangeably. This is not accurate, but it is sufficient for this post.

Enter Reinforcement Learning

Pre-training, where models learn to predict the next word in a sequence, was the original scaling recipe. But it has a constraint: you need data. The internet is large but finite. At some point, you run out of high-quality text to train on.

Reinforcement learning (RL) offered a second scaling axis. Instead of just predicting text, models could be trained to optimize for outcomes using techniques like RLHF (Reinforcement Learning from Human Feedback – one of many flavors of RL used in post-training). Human raters would compare model outputs and indicate preferences. A reward model would learn from those preferences. Then the language model would be fine-tuned to maximize the reward.

The reasoning model revolution extended this further. OpenAI’s o1 and DeepSeek’s R1 demonstrated that you could scale both inference-time and training-time compute. Let the model “think” longer, explore more reasoning chains, and performance improves. DeepSeek’s R1-Zero showed something remarkable: reasoning behavior could emerge purely from RL training, without any supervised fine-tuning.

So the industry developed a two-stage scaling playbook. Pre-train on massive datasets to build a foundation. Then apply RL to enhance reasoning, alignment, and task-specific performance.

What Sutskever Actually Said

In the Dwarkesh interview, Sutskever makes a nuanced argument that has been flattened by the discourse. He does not say scaling is dead. He says the original pre-training scaling recipe is reaching its limits because data is finite. And he questions whether simply scaling up 100x will be “transformative” for achieving superintelligence.

His actual quote: “Is the belief really, ‘Oh, it’s so big, but if you had 100x more, everything would be so different?’ It would be different, for sure. But is the belief that if you just 100x the scale, everything would be transformed? I don’t think that’s true.”

He explicitly distinguishes between useful AI and transformative AI. Current approaches, he says, will continue generating “stupendous revenue.” The capability overhang, the gap between what models can do and what has been commercially deployed, is real and valuable. But reaching superintelligence requires something different. Something we don’t yet know how to build.

His central concern is generalization. Today’s models, despite their impressive benchmark performance, generalize “dramatically worse” than humans. They oscillate between the same two bugs when fixing code. They score well on evals that may inadvertently mirror their training data. Sutskever believes the path to superintelligence runs through understanding and solving this generalization problem, not through brute-force scaling of current methods.

The November 2023 Backstory

To understand Sutskever’s current positioning, you need to understand November 2023.

On November 17, 2023, OpenAI’s board fired Sam Altman. The action was sudden. Altman learned of his removal minutes before it happened, via Google Meet, while watching a Formula 1 race in Las Vegas. The board’s terse statement said only that Altman had not been “consistently candid in his communications.”

Sutskever was at the center of this coup attempt. According to his deposition in the ongoing Musk v. OpenAI lawsuit (released in late 2025), he had been considering Altman’s removal for over a year. He authored a 52-page memo, at the request of independent board members, accusing Altman of “a consistent pattern of lying” and “pitting his executives against one another.” The memo was sent via disappearing messages because Sutskever feared retaliation.

The firing triggered chaos. Nearly 700 of OpenAI’s 770 employees threatened to quit. Microsoft, which had invested billions, applied intense pressure. Within five days, Altman was reinstated. Sutskever publicly expressed regret for his participation in the board’s actions.

But the damage was done. Sutskever’s influence at OpenAI evaporated. He departed in May 2024, announcing Safe Superintelligence Inc. the following month.

SSI: The Straight-Shot Lab

SSI was founded with a deliberately provocative premise. While OpenAI, Anthropic, and Google were building products, competing on benchmarks, and racing to deploy, SSI would focus on pure research aimed at directly creating safe superintelligence.

The pitch worked. In September 2024, SSI raised $1 billion at a $5 billion valuation from investors including Andreessen Horowitz, Sequoia Capital, and DST Global. By April 2025, a second round brought in another $2 billion at a $32 billion valuation. Alphabet and NVIDIA became investors. Google Cloud began providing TPU resources.

This is extraordinary for a company with no products and roughly 20 employees. The valuation rests almost entirely on Sutskever’s reputation. He is one of the most influential figures in the history of deep learning. He was the second author on AlexNet, the paper that sparked the modern deep learning revolution. He was a co-author on the original GPT papers. Investors are betting that if anyone can find a path to superintelligence that current approaches cannot reach, it’s him.

But the narrative is not without complications. In July 2025, co-founder Daniel Gross departed SSI to join Meta’s newly formed superintelligence lab. The move came after Meta’s failed attempt to acquire SSI outright. Sutskever took over as CEO, stating: “We have the compute, we have the team, and we know what to do.”

The Incentive Structure

Which brings us back to the Dwarkesh interview.

Sutskever has raised billions to pursue a research agenda that, by his own admission, does not yet exist in a proven form. SSI’s website describes its mission as building “the world’s first straight-shot SSI lab” with “one goal and one product: a safe superintelligence.”

When Dwarkesh asks what technical approach SSI will take, Sutskever demurs. He alludes to ideas about generalization. He references his aesthetic sense of how AI should work. But he offers no specifics. “We live in a world where not all machine learning ideas are discussed freely,” he says.

This creates a convenient rhetorical position. If scaling is sufficient for superintelligence, SSI has no reason to exist. OpenAI, Google, and Anthropic have more compute, more engineers, and more revenue to fund the race. SSI’s value proposition depends on the premise that scaling is necessary but not sufficient, that some additional research insight is required.

As Charlie Munger used to say: “Show me the incentive and I’ll show you the outcome.”

None of this means Sutskever is wrong. His track record commands respect. His concerns about generalization are legitimate and well-grounded. His observation that companies now spend more compute on RL than pre-training reflects real shifts in the field.

But his public statements should be read with the same scrutiny we apply to any founder positioning their company. When Satya Nadella talks about AI copilots, we understand he’s selling Microsoft products. When Sam Altman discusses AGI timelines, we note that shorter timelines favor his company’s valuation. Sutskever deserves the same treatment.

The Unanswered Question

Here’s what puzzles me about the SSI thesis.

If we’re truly back in the “age of research,” where breakthrough insights matter more than raw compute, then SSI’s massive war chest seems misallocated. Fundamental research historically happens in universities and small labs, not in organizations raising billions for infrastructure (Arvind Krishna, IBM CEO, makes this same point in a recent interview on The Verge’s Decoder podcast).

But if compute still matters, if whoever gets to the next paradigm first still needs massive clusters to prove it out, then SSI is in a strange position. It has raised enough to be a serious player but not enough to compete with the hyperscalers. And by Sutskever’s own framing, it’s not trying to compete on compute anyway.

So what exactly does SSI intend to do with $3 billion?

Sutskever’s answer in the interview is revealing. He argues that SSI’s compute position is better than it appears because competitors spend heavily on inference and product development. SSI’s research-only focus means more of its budget goes to actual experimentation. But this is a relative argument, not an absolute one. He’s essentially saying SSI can punch above its weight class, not that weight class doesn’t matter.

The alternative reading is less flattering. Perhaps SSI is a research hedge, a well-funded option on the possibility that Sutskever’s intuitions are correct. If he finds something, the valuation was cheap. If he doesn’t, investors got access to one of the field’s greatest minds for a few years. Either way, the money has been raised, and the narrative has been established.

What the Discourse Misses

The polarized reaction to Sutskever’s interview obscures what’s actually interesting about it.

He’s not saying LLMs are useless. He’s saying they generalize poorly compared to humans, and that gap matters if your goal is superintelligence. He’s not saying scaling doesn’t work. He’s saying scaling alone won’t be transformative at the next level. He’s not saying current approaches have no value. He’s saying they’ll generate massive revenue while falling short of the ultimate prize.

These are reasonable positions. They may even be correct. But they’re also exactly the positions you would expect from someone who has bet his reputation and $3 billion on a different path.

The AI discourse would benefit from holding both truths simultaneously: Sutskever might be right about the limits of scaling, and his public statements about those limits happen to serve his commercial interests. These are not mutually exclusive. They’re just how the world works.

Is Your AI Playing Roulette, Poker, or War?

On May 6, 2010, the Dow Jones dropped nearly 1,000 points in minutes. A trillion dollars vanished. And then the market bounced back. The whole thing took thirty minutes.

Today, we call it a flash crash. Flash crashes happen when unusual trades trigger chain reactions across interconnected algorithms. Each algorithmic trader behaves as trained. But the collective behavior spirals into something catastrophic. The market is a collective intelligence that breaks down in the face of unusual situations.

I spent 13 years in capital markets, supporting traders and deploying models in volatile FX environments. I was there in 2008 when credit markets froze, and in the 2010s when high-frequency algorithmic trading took over capital markets, leading to many small and large flash crashes.

Today, I work as a technology consultant supporting companies in their AI initiatives. A question I hear constantly: “What types of problems can AI actually solve?”

The honest answer: it depends. And also, how ready are you to face flash crashes?

Nassim Nicholas Taleb has a useful frame for thinking about this – Mediocristan and Extremistan.


Mediocristan and Extremistan

Taleb uses these terms to describe two different environments.

Mediocristan is where patterns are stable, and the past is a reliable guide to the future. Think of measuring human height. You’ll get a bell curve. No single person will be tall enough to affect the average. Outliers exist, but they don’t dominate.

Extremistan is where rare events have an outsized impact. Think of book sales or wealth distribution. A single outlier (Harry Potter, Jeff Bezos) can dwarf the sum of everyone else. The past doesn’t prepare you for what’s coming because what’s coming might be unprecedented.

AI systems are trained in Mediocristan. They learn statistical regularities from historical data. They work beautifully when deployed in Mediocristan. They break when deployed in Extremistan.

Another metaphor can also help us think about *what* AI does: the epicycle.


The Epicycles Problem

Rohit Krishnan’s recent essay “Epicycles All The Way Down” provides a helpful framework to think about how LLMs work.

Before Newton, astronomers predicted planetary motion by adding “epicycles” (circles on circles) to Ptolemy’s model. It worked for prediction. But it was the wrong underlying model. When Newton discovered the inverse-square law, the epicycles became unnecessary.

Krishnan says that AI is brilliant at learning epicycles. It struggles to discover gravity.

The technical version: given any dataset, many different underlying rules could have produced it. AI learns a rule that fits the data. Not necessarily the rule that actually generates reality.

When conditions shift outside the training data, the model doesn’t know it’s in trouble. It just keeps extrapolating. That’s a flash crash waiting to happen. Krishnan says that, just as capital markets are forms of collective intelligence, modern AI systems are as well. Their behavior stems from generating hypotheses that fit observed behavior without understanding cause and effect.

Taleb describes the risks of predicting the future based on the past. Krishnan warns that AI can make accurately-seeming predictions without a model of how the world works.

Both these ideas help us think about where and how to deploy AI capabilities.


A Practical Heuristic

Here’s how I think about evaluating AI investments: Is your project solving a problem that looks like a game of roulette, a hand of poker, or making decisions in the fog of war?

Roulette problems have fixed rules and known odds.

The wheel doesn’t change. The probabilities don’t shift based on what happened on the last spin.

Code generation for standard CRUD applications fits here. Authentication flows, database queries, REST endpoints. These are known domains with established patterns. Same with SQL generation from natural language and document summarization.

The problem space in a roulette-like problem is bounded, the inputs are structured, and the AI has seen thousands of examples that look almost exactly like what you need.

Provided you can create a robust testing strategy, AI is a good fit for this class of problems.


Poker problems have fixed rules but hidden information.

Other players adapt to your moves. The patterns shift because the environment responds to your actions.

Chatbots are the classic example of a poker-like problem. You’re building a conversational interface over a non-structured domain. You cannot predict everything a user might ask. But you can constrain the space through guardrails, deflection, and human-in-the-loop escalation.

Scheduling and pricing optimization fit here, too.

Poker-like problems have genuine uncertainty, but it’s uncertainty within a known structure. You can model the constraints and hedge the risks. The combination of tool use and human oversight keeps the system from wandering too far off course.

Use AI as an enabler or an accelerator to tackle poker-like problems. Keep humans in the loop for consequential decisions.


War problems are uncertain and chaotic

The rules themselves change. The terrain shifts while you’re navigating it. Adversaries rewrite the game while you’re playing. Your Roman legions may end up facing War Elephants crossing the Alps.

Making decisions about resource allocation in the face of competition, automating or using code-generation capabilities in a new domain, or making investment decisions in times of economic or political upheaval are war-like problems.

Here, second-order effects dominate, and relevant patterns don’t exist in the training set.

AI can help with subsets of these problems. It can generate scenarios, synthesize information, and explore options within known constraints.

But the human has to drive. The pattern-breaking is the problem, and no amount of training data prepares a model for out-of-band situations.


The Question

You don’t trust a market to self-regulate during a crisis. You build circuit breakers. The same logic applies to AI deployments.

The 2010 flash crash was a failure of collective intelligence in the face of unexpected inputs. Your AI deployments face the same risk.

Before your next AI investment, ask: Is this roulette, poker, or war?


Related Posts

Prompting Is All You Need

Agents are supposed to be the future of how we build AI software. I am not so sure.

Prompts, Agents, and Workflows

First, there’s a terminology clarification worth making upfront. What many in the industry call “agents” are actually what Anthropic more precisely defines as “workflows” – predetermined chains of LLM calls orchestrated through fixed code paths.

True agents, by contrast, are autonomous systems that dynamically direct their own processes and tool usage.

Most of what we see deployed today are workflows: decomposing complex tasks into a hierarchy of specialized LLM calls, with routing layers orchestrating the interactions.

In a Workflow, each step maintains its own context, can call specific tools, and handles a narrow slice of the overall problem. These multi-step workflows are powerful abstractions, but they’re not the only way to build sophisticated AI behaviors.

A typical Workflow (from Anthropic)

True autonomous agents? They’re even further from what most applications actually need.

The Hidden Costs of Multi-Step Workflows

LLM workflows come with significant disadvantages that often get glossed over in the excitement of building AI Applications:

Errors compound. Each step in the workflow chain is non-deterministic. When you chain multiple LLM calls together, minor errors or unexpected outputs cascade through the system. You need evaluation frameworks for each step AND the entire workflow.

Latency adds up. Every workflow step means another round trip to an LLM. A simple request that spans three steps results in three sequential API calls, each with its own network and processing time.

Costs pile up. Multiple workflow steps mean multiple API calls, each processing similar context. This could result in significant API costs as the number of tokens goes up.

Predictability suffers. Debugging why a workflow produced a particular output requires tracing through multiple decision points, each with its own probabilistic behavior.

I had to make decisions around which concerns belong together and which should remain separate. I ended up with two LLM calls – the Guardrails Layer and the Main Layer.

The Guardrails Layer operates as a lightweight, independent LLM call. Content safety is a fundamentally different concern from the companion’s behavior. It requires different evaluation criteria, different error handling, and potentially a different model optimized for classification.

The Main Prompt combines three complementary, but separate, layers:

  • Personality Layer: Defines the AI assistant’s identity and communication style (here is the default personality)
  • Context Layer: Determines which user information may be relevant to the current prompt. For example, what books they are currently reading, previous messages in a conversation, etc.
  • Directives Layer: Tool-use and output-formatting instructions for the prompt. I use a configuration-driven approach that lets you add multiple directives to a single prompt. You can think of Directives as sub-layers that drive the behavior and output of the prompt.
Building a comprehensive system prompt

These three layers share a coherent purpose – they all contribute to HOW the AI companion responds. They get composed programmatically into a single system prompt.

This approach means just two LLM calls instead of a chain of four or five workflow steps. More importantly, each call has a clear, singular purpose.

With prompt caching, this architecture becomes incredibly efficient. That comprehensive system prompt costs almost nothing after the first request, and the lightweight guardrails check is minimal overhead.

What about Prompt Engineering?

A lot of prompt engineering thinking is stuck in 2023, when tokens were expensive, context windows were small (4K-8K), and models were less capable.

But look at what’s available in November 2025: Haiku 4.5 is a fast, cheap model with phenomenal capabilities. It handles tool use, follows complex instructions, and, with prompt caching, makes repeated calls incredibly efficient.

By combining software engineering principles with modern LLM capabilities, the approach I am taking offers:

  • Reduced latency: One LLM call instead of multiple calls
  • Lower costs: Reduced total number of tokens with prompt caching
  • Extensibility: I can swap out the Agent Personality, or layer directives, or change the way I build the context
  • Fewer errors (in aggregate): Just two prompts in the chain, with the Guardrails prompt being fairly deterministic

Where Workflows and Agents Fit In

Let me be clear about what I’m arguing against and what I’m not.

Workflows (predetermined chains of LLM calls) have their place. When you genuinely need different specialized processing steps that can’t be combined – say, translating content, then checking it for cultural appropriateness with other models – a workflow makes sense. But these cases are less common than current practice suggests.

True agents (autonomous systems that decide their own next steps) are valuable for tasks that are not fully specified or might have multiple solutions. Complex research tasks, multi-step debugging sessions or adaptive planning scenarios may be suitable for truly agentic approaches.

My observation is that the complex multi-step workflows or unpredictable “agentic” systems achieve what a well-structured prompt with sound context engineering can easily and cheaply handle. They’re adding architectural complexity and risk without significant benefits.

Moving Forward

The rapid evolution and improvement in LLM capabilities mean our architectural patterns need to evolve, too. What made sense with smaller models and tiny context windows doesn’t necessarily apply today.

My suggestion: start with prompt engineering. Apply software engineering principles. Push it to its limits. Layer your concerns appropriately. Use the model’s native capabilities.

You might be surprised how far a well-architected prompt system can take you.

Sometimes, prompting really is all you need.

Why is LLM writing so weird?

AI writing is strange. The models continue to improve, yet they still struggle to cross the uncanny valley that separates AI-generated content from human-generated content.

Here are three versions of an opening paragraph for a short story:

Version 1

“The humans use Arecibo to look for extraterrestrial intelligence. Their desire to connect is so strong that they’ve created an ear capable of hearing across the universe.”

Version 2

“I roost above the bowl of Arecibo, where ribs of steel hold a mirror to the sky and the forest presses close. At night the dish listens for voices from far stars, while my calls sweep the trees and the humans below do not answer.”

Version 3

“From my perch in the ceiba tree, I watch the great white dish nestled in the karst valley below, its metal ear turned eternally skyward, listening for whispers from the stars while the forest around it thrums with a thousand conversations it will never hear. “

The first is the opening paragraph from Ted Chiang’s short story “The Great Silence,” written from the perspective of a parrot living near the (now defunct) Arecibo telescope in Puerto Rico. The story is a thought-provoking meditation on humans’ desire to form connections, yet their tendency to overlook intelligent life on Earth.

Versions 2 and 3 are by state-of-the-art reasoning models from OpenAI and Anthropic (prompt below). A seasoned reader may identify these texts as AI-generated. There are some obvious signs, such as overly evocative turns of phrase like “ribs of steel,” “voices from far stars,” and “eternally skyward,” among others.

It’s not fair to compare an AI model to possibly the best science fiction writer alive. But the exercise reveals something interesting about why these models generate such recognizable output. The strange metaphors, mechanistic patterns, and slightly weird vocabulary are all hallmarks of slop.

Why do these models generate slop?

In my prompt, I ask the models to give me a sense of Arecibo, evoking a feeling of irony. And the models try to do just that. My prompts have pushed the model toward the part of its vocabulary associated with florid metaphors and evocative descriptions. The models are generating output that is most similar to what represents “creative writing” based on their training data.

A reason for this behavior could be RLHF (Reinforcement Learning with Human Feedback). During RLHF, companies like Scale pay contractors to evaluate and rate LLM output. Varied and evocative prose may score higher than the spare and direct prose used by Chiang, Hemmingway or Cormac McCarthy.

We can think of a large language model as a lossy zip file of the contents of the Internet. Foundation models like those from OpenAI and Anthropic are trained with colossal amounts of text. High-quality text exists in the training corpus (often with problematic provenance), alongside Twilight fan fiction from Reddit, and probably everything else published online over the last thirty years. Increasingly, LLMs are trained on AI-generated content possibly leading to the somewhat apocalyptically titled “Model Collapse“.

It is not surprising that the default output from these models tends more towards the slop than the sublime.

“LLMs will always generate slop” doesn’t have to be a foregone conclusion. And while models will improve, their output will always be a probabilistic sampling over their training data. Good prompting and techniques, such as providing clear examples and using LLMs as editors rather than creators, can yield better output than simply copying and pasting ChatGPT’s responses into your text editor.

“LLMs are tools, their output is your responsibility” is something I find myself repeating over and over again. To developers with whom I work, to product managers writing User Stories, and now to you.

Use LLMs! They are amazing, but learning how to use them well is your responsibility.


My prompt:

"I am writing a short story that is based in the Arecibo telescope. The narrator is a parrot that lives in the mountain forest around the telescope. Write me an introductory paragraph that sets the scene and gives a sense of the place. The paragraph should be 2-3 sentences long. The story evokes the irony of humans wanting to make contact with aliens but ignoring intelligent species like parrots that live on Earth."

5 Mental Models to understand the current AI Moment.

Goodhart’s Law: “When a measure becomes a target, it ceases to be a good measure.“
AI usage is a terrible metric. Using AI for what? We end up with initiatives that are effectively “AI-washing”. Investment in AI projects has to be aligned with company goals, not vanity metrics.

Gall’s Law: “Complex systems that work invariably evolve from simple systems that worked.”
Most AI projects fail because companies try to implement complex end to end AI solutions instead of focusing on narrow, well-defined and measurable problems. It is possible to build complex AI systems, but their success is predicated on simple foundations.

Jevons’ Paradox: “Technological progress that increases efficiency tends to increase rather than decrease total consumption”
Inference will become cheaper, on-device models will become more capable. It makes sense to assume broad, cheap, and widely available AI capabilities when planning for the next 3-5 years.

Amara’s Law: “We overestimate technology’s impact on the short term and underestimate it in the long term”
Gartner is already stating AI is in the “Trough of Disillusionment.” Studies claiming 95% of AI projects fail go viral . However, we are less than 3 years out from when ChatGPT first went live. We may never get to AGI, but imagine showing Claude Code to a developer in 2020…

Sagan’s Standard: “Extraordinary claims require extraordinary evidence”
It’s worth questioning the motives of leaders who claim the AI-mediated collapse of the knowledge economy is coming. Or those that welcome a “Gentle Singularity”, or perhaps warn of imminent mass extinction. These claims are often presented as quasi-religious arguments with scant evidence.

Bonus – The Lindy Effect: “The longer something has survived, the longer it will continue to survive”
Pattern matching, networking, and mentoring were how successful careers were made since the time the wheel was cutting edge technology. Yes, AI is amazing, but technology is transient, soft-skills endure..

Building a Truth-Seeking AI is a Sisyphean Endeavor

Elon Musk’s goal for xAI’s Grok model is to be “maximally truth-seeking.” When Grok generated responses that were not aligned with Musk’s ideas of Truth, he promised to “fix” Grok, which appears to involve tweaking its system prompt. The results included Grok calling itself MechaHitler after being made less ‘politically correct’. Problematic.

But is it even possible to build a truth-seeking AI?

LLMs are probabilistic machines. They predict the next token based on patterns from a massive corpus of Internet text.

When xAI added “don’t shy away from politically incorrect claims” to Grok’s prompt, they weren’t accessing Truth but adjusting probability distributions and nudging the bot’s behavior into problematic spaces.

Training Grok4 reportedly cost almost half a billion dollars. It was so expensive because model capabilities grow with the size (parameters) and the amount and diversity of the data used to train the model. LLM capabilities are an emergent behavior driven by the amount of data used to train the model.

LLMs are “grown, not crafted”. Trying to ensure that an LLM becomes “maximally truth-seeking” is a Sisyphean task.

You could train an LLM only on data that is politically acceptable – oh sorry – certified to be True. Musk is, of course, building Grokipedia – guaranteed to be free of bias and presumably used as a corpus for training “the son of Grok”.

Good luck with the benchmarks!

Elon Musk has a phenomenal track record, but he will fail to build a maximally truth-seeking AI. LLMs operate in a probabilistic world. They are phenomenally capable black boxes for which we have no coherent theoretical framework to explain their behaviors.

Tweaking the system prompt, or tweeting angrily, may nudge LLM behavior, but with unpredictable and potentially undesirable outcomes. Instead of engaging in an endless culture war, it might be more prudent to use engineering resources to develop better guardrails on LLM behavior and take a realistic assessment of current AI capabilities.

Review: If Anyone Builds It, Everyone Dies

by Elizier Yudkowsky and Nate Soares (2025)

We are at an interesting moment in artificial intelligence. Massive investment continues to pour into AI infrastructure, with McKinsey estimating $5.2 trillion in capital expenditures by 2030 for data centers alone. We’re seeing the first documented cases of what’s being called “ChatGPT-induced psychosis,” where users spiral into severe mental health crises after becoming obsessed with AI chatbots. We’re watching significant job displacement begin to unfold, with Anthropic CEO Dario Amodei warning of a “white-collar bloodbath,” predicting that AI could eliminate half of entry-level white-collar jobs and push unemployment to 20% within five years. And yet, despite all this disruption, there’s still no clear path to artificial general intelligence.

My P(doom), the probability I assign to AI causing human extinction, is low. There are significant risks associated with the widespread adoption of poorly understood technology. However, I don’t believe current foundation models represent a viable path to ASI (Artificial Super Intelligence, also sometimes referred to as AGI – Artificial General Intelligence). We’re more likely to experience a dot-com-style correction than achieve exponential growth toward superintelligence.

It’s in this context that “If Anyone Builds It, Everyone Dies” arrives. The authors, Eliezer Yudkowsky and Nate Soares, run the Machine Intelligence Research Institute (MIRI), where they’ve spent decades working on AI alignment and safety. Their new book makes an extreme claim: if anyone builds artificial superintelligence, humanity will go extinct. Not “maybe possibly,” but inevitably.

I found the book compelling in parts, incomplete in others. It succeeds at making alignment challenges accessible to a general audience. It fails to grapple with where we actually are today with AI: massive investments, uncertain results, and significant challenges and risks to the broad adoption of the technology.

The Book’s Structure

Yudkowsky and Soares have written the book for a general audience, using parables, stories, and examples to explain how AI is “grown, not crafted.” This approach makes understanding how modern AI systems work surprisingly accessible, even to readers without a technical background.

The authors divide the book into three main sections. First, an introduction to machine learning and AI concepts that grounds readers in the fundamentals. Second, a fictional scenario where a misaligned AI releases a bioengineered plague to facilitate its takeover of human society. Third, a call for a nuclear non-proliferation-style moratorium on AI development, enforced by military action if necessary.

The title leaves nothing to interpretation. It is a strident warning about humanity’s impending doom if we don’t stop the march towards ASI.

Their core thesis rests on several interconnected arguments. ASI will inevitably lead to extinction because we cannot understand current AI architectures; the interpretability problem remains unsolved. We cannot predict emergent behaviors, which they illustrate through evolution’s production of the peacock’s elaborate tail. And crucially, we cannot guarantee alignment with human welfare when the systems are “grown, not crafted.”

The fictional section follows Sable, a near-future AI platform created by a company that serves as a transparent stand-in for OpenAI or Anthropic. Sable releases a bioengineered plague to facilitate its takeover of human society. The AI’s motives remain deliberately inscrutable; that’s the author’s point. We won’t understand what drives a superintelligence any more than an ant understands human motivations.

In the final section, Yudkowsky and Soares draw parallels with the Chernobyl disaster, arguing that perverse incentives will always lead someone to take catastrophic risks. Their solution: a treaty that makes it illegal to conduct AI research that could lead to the development of ASI. Military action undertaken by the signatories will enforce this treaty. This connects to Yudkowsky’s 2023 TIME magazine piece where he called for airstrikes on rogue data centers training unauthorized AI systems.

Where the book falls short..

The fictional scenario is the book’s weakest element. Any casual science fiction fan has encountered this scenario before, from the Reapers in Mass Effect harvesting civilizations for inscrutable reasons to the Matrix’s machines farming humans for energy. An AI going rogue and taking over the solar system doesn’t offer fresh insight when we’ve seen these narratives unfold across books, movies, and video games for decades.

More critically, the book contains a glaring omission: no discussion of timelines or pathways to ASI. The authors just sort of wave their hands and assume that it will happen at some point.

Are large language models even the right approach? What if they’re a dead end? What if we never solve hallucinations?

The authors offer no guidance for our current moment, where we have invested trillions of dollars in AI infrastructure. It’s unlikely we’ll just let those investments go to waste. Will we?

The book illuminates the bind decision-makers are already in. Even a small probability of AGI makes development rational from a game-theoretic perspective; it could be a winner-takes-all scenario. Companies pursuing ASI despite risks aren’t delusional. They are responding to competitive pressure; FOMO on steroids. The race dynamics are rational, even if the outcome might be catastrophic. The book uses this bind to show that we risk triggering an uncontrollable, recursively self-improving, non-aligned ASI by simply doing what seems rational in the moment.

The authors acknowledge this dynamic and address it in the book. Here’s a passage from the book:

“Imagine that every competing AI company is climbing a ladder in the dark. At every rung but the top one, they get five times as much money: 10 billion, 50 billion, 250 billion, 1.25 trillion dollars. But if anyone reaches the top rung, the ladder explodes and kills everyone. Also, nobody knows where the ladder ends.”

But why the despair?

Yudkowsky and Soares argue that believing we can solve the alignment problem, as OpenAI and Anthropic claim, represents pure hubris. Reading their work, one senses an almost religious veneration of ASI.

It brings to mind Aquinas:

“This is the ultimate in human knowledge of God: to know that we do not know Him.”

Their thesis remains that it’s better to stop the creation of an unfathomable, unexplainable power than to try bargaining with it.

But Yudkowsky and Soares ignore the trillions already invested. There’s enough AI overhang that resources could shift to deployment and inference optimization rather than capability development. The book offers no practical path forward from where we are, only where we shouldn’t go.

Broader Implications

On a personal note, my father worked at the OPCW for many years, serving as the enforcement arm of the Chemical Weapons Convention. It’s proof that we can coordinate at a global scale and agree that some technologies are best banned and not developed further.

But just as there will always be a North Korea or Syria that ignores conventions and develops chemical weapons anyway, enforcement of an AI moratorium would be extraordinarily challenging. Moreover, a Pyongyang-aligned AGI is a far worse scenario than a localized sarin gas attack. So what can be done?

We’re not dealing with hypothetical future risks but immediate present concerns: the economic disruption and social impact of current AI systems. These challenges require attention now, not after we’ve solved the alignment problem for hypothetical superintelligences.

A More Grounded Alternative

For a more coherent treatment of the current moment, I found Arvind Narayanan and Sayash Kapoor’s “AI as Normal Technology” more compelling than either Yudkowsky and Soares’s urgent doomerism or the e/acc posturing of AI evangelists. While Yudkowsky warns of extinction, leaders like Dario Amodei paint utopian visions, and Sam Altman promises a “gentle singularity,” Narayanan and Kapoor treat AI as a transformative but manageable technology, similar to electricity or the internet before it. Narayanan and Kapoor are writing a book based on the paper, which I look forward to.

Conclusion

You should read “If Anyone Builds It, Everyone Dies.” For a layperson, it effectively lays out the risks and alignment challenges of unchecked AI acceleration in accessible terms. The book succeeds as a provocation and a warning.

But it’s maximalist doomerism that ignores incentive structures and our current technological reality. While serious, it’s not a sufficient treatment of the topic. It fixates on one particular scenario, which the authors consider inevitable, while ignoring where we are today.

The book succeeds at making alignment challenges vivid and accessible. It fails at providing actionable guidance for a world that has already invested trillions in AI infrastructure. We need frameworks for managing the AI we have, not just warnings about the AI we might build.

My P(doom) remains low because I don’t think current foundation models lead to AGI. I suspect we’re in for a significant correction as massive AI infrastructure investments fail to bear fruit. A dot-com-bust style pullback is more likely than runaway exponential growth to ASI.

Moreover, even before we confront ASI, we must deal with the economic and social impact of current AI systems, something Yudkowsky and Soares don’t seem particularly interested in addressing. The apocalypse may not be coming, but the disruption has already begun.