I need to make a change to how I show up here.
For the last year or so, I’ve been in your inbox almost every day covering AI. That was not a gimmick. It made sense for the moment we were in. A new model would ship in the morning. A new capability would show up by lunch. By the afternoon, the practical answer to “what can I build with this?” had changed.
During that period, keeping up really mattered.
I think that period is changing. The models are here. The agents are here. The harnesses are here. Execution is getting cheaper by the month. A prototype, a draft, an analysis, a small internal tool, all of that is easier to create than it was a year ago.
But that has made one thing more obvious to me, not less: the hard part is understanding what to build, why it matters, and how to use these tools well enough that they change your work.
I don’t think daily AI news is the best way to build that kind of fluency anymore. It can help you know what launched. It cannot, by itself, help you get good.
And I want this Substack to help you get good.
So I’m changing the cadence.
Three anchor pieces a week
Starting now, I’m going to build this around three serious pieces each week.
The first is the deep dive. I’ll take the most important AI story or development of the week and go underneath the headline: what happened, what changed, what people are missing, and what it means for the work you’re actually doing.
The second is the build. This is the one I’m most excited about. Each week I want to give you something practical enough to take to your own machine. Not a “hello world” demo. A real build. The kind of guide where you understand the tool better because you have actually made something with it.
The third is the executive briefing. For paid executive subscribers, I’m going to keep sharpening the weekly read on where to invest, what leaders need to understand, what is noise, and what decisions are worth making now.
That is the new default: fewer pieces, more depth, more work that is worth keeping.
What this looks like first
I want to be concrete about the first few weeks, because otherwise this can sound like a nice editorial promise.
I’m working on a full Codex guide that goes well past the feature list. I want to show where it works, where it breaks, and what it feels like to build with it in real workflows day after day.
I’m also building a token burn dashboard you can run yourself. If you are using APIs and can’t see where the money is going, this will put a working answer on your machine.
And I’m writing a deep dive on Claude 4.8: what actually changed, what the benchmarks don’t capture, and what it means for the things you are shipping right now.
That is the standard I want to hold myself to.
Two other changes
I’m also standing up a Slack workspace for paid subscribers.
The reason is simple: a lot of the best conversations around this work happen in replies and DMs, and then they disappear. I want a place where serious builders can find each other, where I can surface useful things faster than a weekly article allows, and where you can ask for help on a Tuesday afternoon instead of waiting for the next post.
If you’re a paid subscriber, you’ll get an invite this week.
And I am not disappearing from news.
If something drops that changes how you should work, I’ll cover it. A major model release, a new capability, a shift that changes the practical answer to “what should I do this week.” Those will still get their own coverage.
The bar is just higher. If it matters, you’ll hear from me. If it’s interesting but not urgent, I’ll save it for the deeper work. That also means fewer emails from me, which I know some of you have asked for. I’ve heard that.
What I’m trying to build here
The gap I keep coming back to is the gap between “I’ve heard of that tool” and “I can build with that tool.”
I think that gap is going to matter a lot in 2026. For careers. For companies. For anyone trying to lead, learn, build, or make good decisions while the ground keeps moving.
Most people are going to keep skimming. They’ll read the launch post, save the thread, watch the demo, and feel like they’re keeping up.
But keeping up is not the same as building fluency. Sometimes it is just watching other people build.
I don’t want that for this audience. I want this to be the place where you come to understand what matters, practice it, and leave with something you can actually use.
I can’t do the practice for you. But I can make the work clearer. I can give you better guides, better judgment, better builds, and a stronger place to talk through the hard parts with other people doing the same thing.
That is what I’m committing to now.
Fewer emails. Higher bar. More depth. More work you can carry into your own projects, teams, and career.
I’m grateful you’re here. I’m especially grateful to everyone who has stuck with the daily pace, replied, challenged me, asked for more depth, and pushed this into something better.
Let’s build.
Nate
