The newsletter
What shipped.What is hype.One thing worth your Saturday.
That is the whole newsletter. One email a week across AI, coding, writing, images and Web3, written by me rather than generated and sent unread. It is free, it is meant to be useful on its own, and most people who read it will never book a call.
- Weekly · unsubscribe in one click
- Free
- Written by one person, not a model
- [PLACEHOLDER: real subscriber count] subscribers so far
The format
Three things, every week.
Not a link dump. The same three slots each issue, so you know within five seconds whether this one is worth your time.
One
What shipped
The releases that changed what you can actually build this week: a model, a tool, an API, a pricing change. Links go to the thing itself, not to a thread about the thing. If it is a paper with no shipping product behind it, it belongs in the next slot.
Two
What is hype
One launch everybody posted about that does less than the demo suggested. This is the slot that takes the time, and the one most newsletters skip, because a verdict costs you something and a link does not. Sometimes I get it wrong, and then the next issue says so.
Three
One thing worth your Saturday
A single thing to build, read or try, sized to one morning. One, not ten. A list of twenty links is a list you will not open, and I would rather you finished one thing than bookmarked nineteen.
The five areas it covers
- AI: models, agents and the tooling around them, judged on whether they hold up on a real project rather than in a launch video.
- Coding: specification-driven building for people who do not write production code, which is the thing I actually do all week.
- Writing: drafting, editing and publishing pipelines, including the one that ships 15+ articles a day behind my own work.
- Images: generation and design tooling, from the same angle: what it genuinely replaces, and what it does not.
- Web3: covered when something real happens in it, which is not every week.
What it is not: exhaustive. Five areas and one email means things get left out on purpose, and anything that needs two thousand words gets written up separately rather than compressed into a bullet.
A sample issue
What a typical issue looks like.
Illustrative, not a back issue. The structure is fixed; the contents are whatever the week actually produced.
01
The one line at the top
What changed this week, in a sentence. It is there so you can decide in five seconds whether to read the rest, including the weeks where the honest answer is that not much changed.
02
Shipped
Three to five releases, each with what it does and who it is for. No screenshots of the announcement, no reaction quotes.
03
Hype check
One launch, and the specific thing it does not do. Where I have tried it on real work, I say what broke; where I have only read about it, I say that instead.
04
Worth your Saturday
The single build, read or experiment I would spend a morning on, with the brief I would use to start it, because the brief is most of the work.
05
What I am building
A short note on whatever I am shipping that week, including the parts that broke. Six products in, most of the useful detail is in the parts that broke.
If you would rather read one before you subscribe, [PLACEHOLDER: link to a public archive of past issues, or say there is not one yet].
Fit
Who it is for.
The list is small and I would rather it stayed accurate than got big.
- Founders and operators who are not technical, and are tired of being told that is a permanent condition.
- Product people who want a shorter path from a decision to something running.
- Anyone using these tools daily who wants a second opinion from somebody shipping with them rather than selling them.
- People who would rather read one honest paragraph about a limitation than five about a launch.
Be honest with yourself
Who should not subscribe.
If you want daily AI news, this is the wrong list. It is weekly, it is deliberately incomplete, and it will miss things you read about elsewhere three days earlier.
If you are after prompt packs, growth hacks or a shortcut that removes the thinking, we will only annoy each other. The method here is writing a proper brief before you build, which is more work up front, not less.
And if you already ship software comfortably with a team of engineers, most of this will be things you know. The articles are the better use of your time, and they are free too.
The small print
What you are agreeing to.
The same wording as the checkbox on the form, in one place where you can read it without a tick box next to it.
- Weekly · unsubscribe in one click
- I agree to receive the newsletter by email and I have read the privacy policy. You can unsubscribe at any time.
- No spam, no list sales, no third-party sharing. Stored in the EU.
- Demo only: no backend is connected yet, nothing is stored or sent.
That last line is the current state, not a disclaimer. Until the signup backend is connected, the form checks your address in your browser and then forgets it: nothing is stored, and no email is sent. When that changes it will be double opt-in, so you confirm by email before anything arrives.
Before you subscribe
Three fair questions.
Is this not just another AI newsletter?
I am not technical. Will any of it make sense?
What happens to my email address?
One email a week
Start with the next issue.
It is free, it takes one click to leave, and most people who read it will never book a call. If you do eventually want the paid version of this (the consulting or a course), it will still be here.
P.S. If you are undecided, read the sample structure above and skip it if the answer is no. I would rather have a short list that opens every email than a long one that does not.