justin․searls․co

Dion Lim wrote a pretty good angle on what the market correction will actually do:

The first web cycle burned through dot-com exuberance and left behind Google, Amazon, eBay, and PayPal: the hardy survivors of Web 1.0. The next cycle, driven by social and mobile, burned again in 2008–2009, clearing the underbrush for Facebook, Airbnb, Uber, and the offspring of Y Combinator. Both fires followed the same pattern: excessive growth, sudden correction, then renaissance.

Now, with AI, we are once again surrounded by dry brush.

I think in one of our discussions before our Hot Fix episode, Scott Werner and I used the same analogy—that a recessionary fire will be necessary to clear the overgrowth and make room for companies better-adapted to the post-AI world to innovate—and the author seems to have picked up that metaphor and run with it.

I think the important thing to take away here is that most people hear this and their instinct is to hide. "Well, a fire is coming, I should sit on the sidelines and wait things out." Apart from the foolishness of trying to time the market, this is especially bad advice amid a market wildfire. One of the most actually-useful pieces of advice I've offered founders and investors over the years is the importance of investing through into and through the downturn.

My preferred way to do that is, of course, profitably. However, if you're ever going to tolerate operating at break-even margins or (God forbid) a loss, the best time to do that is when everyone else is cashing out, laying people off, or closing up shop. Hunker down through the cleansing and the act of persevering will generally see a company emerge as a far more resilient operation that finds itself in a far less competitive environment.

I learned this during the Web 2.0 during the Great Recession. Pillar Technology started hiring some of the most talented, most engaged developers in central Ohio and southeast Michigan throughout 2009-2011 when other firms were still hobbled by downsizing. And they paid a premium, too (I nearly doubled my salary to work there!). But when they came out the other end of the recession, they were five times the size, sold into half a dozen verticals, had developed a national profile of clients, and the owner was able to cash out to Accenture for a high-eight figure exit.

When other people get scared, get aggressive.

Breaking Change artwork

v48 - Coil Whine

Breaking Change

Video of this episode is up on YouTube:

I'm experiencing what breathing out of my nose properly feels like for the first time. Everything is new and wondrous and I've never felt so optimistic. This sensation lasted for two days and now I'm used to it and existence is once again pain.

Share your existential musings at podcast@searls.co and I'll nod and sigh along. I might even nod and sigh performatively for you on the show!

Important ground covered in this episode:

Show me them show notes…

I'd do it all again

This is a copy of the Searls of Wisdom newsletter delivered to subscribers on November 25, 2025.

Hello! We're all busy, so I'm going to try my hand at writing less this time. Glance over at your scrollbar now to see how I did. Since we last corresponded:

My good friend Ken took me to the Magic game last night some number of nights ago. It was a great game because we were losing very badly, and then it became very close, and then, right at the end—we won! The classic comeback narrative arc was fulfilled. Sports!

Ken and I at the Magic game

I was reflecting on life the other day, which is a thing I do more often now that I'm firmly in Phase 3 of my evil plan to ride off into the sunset and gradually be forgotten by all of you.

My original plan for this essay would have pulled at the common thread that ties things like game design, derivatives trading, reality shows, and sports betting together. Unfortunately and unsurprisingly, it was taking me too long, and I'm now running out of time in November to give you a recap on what happened in October.

(By the way, don't be surprised if I just send you all a postcard for the December issue. I'm still new at running a monthly newsletter, and I'd prefer not to find out what happens when I fall more than a month behind. Feel free to demand a refund by replying to this message.)

So, anyway, like I said, my actual essay fell apart. Instead, I'm going to share a personal example of how a series of consequential decisions can paradoxically be both productive & rational, while simultaneously being costly & misguided.

I'd do it all again

It all started with one stray piece of unsolicited feedback.

Turns out, there's more to it…

Words and phrases that Codex CLI will use to describe things it did that I will almost always revert:

  • "Belt-and-suspenders"
  • "Fallback"
  • "Backwards compatibility"
  • "Sentinel"
Copied!

The job of a programmer is to manage exactly two things: uncertainty and complexity.

Code is sometimes an asset and sometimes a liability, but itself has no meaning outside the context of those two factors.

Copied!

It's time to work out and I realized I left my gym clothes in the laundry machine overnight and they're still damp. For some reason, I refuse to just wear them because—as opposed to being sweaty—they are now "the wrong kind of wet."

Copied!
Breaking Change artwork

v47 - Turbinately Ill

Breaking Change

Video of this episode is up on YouTube:

Had a little pep in my step this time. Maybe it's because I decided to start recording after 7 AM for once. Maybe it's because I can finally fucking breathe out of my nose holes.

Tell me about what you do while you continue to draw breath at podcast@searls.co.

Things you can read if you're bored:

Show me them show notes…

I've been daily-driving Codex CLI with GPT-5 since release, because OpenAI's "codex" model was—in my experience—bad at coding.

Well, their new "GPT-5.1-Codex-Max" model absolutely smokes any model OpenAI has put out before. Much higher code quality and 2-3 times as fast.

Copied!

On one hand, yes, it's ridiculous I pay $200 a month for ChatGPT Pro. On the other hand, I saved over $800 last month by just letting it crank on scrounging for coupon codes and price matches.

Easily pays for itself if you're creative.

Copied!

First impression of Google Antigravity: this is by far the jankiest VS Code fork I've seen yet.

Should have shipped a CLI with a web product for orchestration.

Copied!

TDD is more important than ever

Lately, I've been reminded of the heady days of my agile youth by how often I've found myself asking, "how will we test this?"

As I've mentioned frequently on podcasts and recent Q&As about AI, an odd paradox has emerged in the software industry:

  1. Developers experienced in agile engineering practices like test-driven development tend to be among the most skeptical of AI code generation, often citing fears that software quality is being thrown out the window
  2. Developers experienced in agile engineering practices like test-driven development tend to be among the most successful at building great software with coding agents, often citing creative techniques enabling agents to verify the correctness of their work

In the late 2000s, I always knew I was talking to a solid programmer if their first question upon being handed a complex task was to ask, "how will we test this?" Agile developers learned back then that literally everything hinged on establishing a fast, reliable, automated way to verify your code fulfilled its intended purpose. Without tests, you can't refactor aggressively, deploy frequently, or delete safely. Over the 2010s, many of us learned patterns and heuristics that allowed us to take shortcuts and tone down our testing zeal in the name of pragmatism and efficiency, but the underlying skill of concocting ways to verify our code never stopped being valuable.

Well, here we are again. In 2025, the only thing that matters when it comes to coding agents like Claude Code and Codex CLI is to ensure they are equipped with the tools they need to independently verify the correctness of their work.

Let's dive in and find out…

Downdetector is down

When half the websites I visited wouldn't load this morning, I figured I'd check downdetector to see if Cloudflare was down, but I couldn't. Because Cloudflare was down.

Distributed systems sound great, but the way the industry rushed to crown a handful of winners like AWS and Cloudflare had the net effect of merely increasing the number of single points of failure in the chain.