Ten notesThree minutes each
The thesis gets tested in public, one short note at a time.
Ten notes, three minutes each. Each one takes a single claim and tries to break it against something that actually happened, which is why a few of them contradict the others.
Nine more, newest first.
Read from the bottom up if you want the argument built in order. Read from the top down if you want to know where it has got to.
- 09July 2026
You can't ship AI you can't afford
Unit economics are a build decision. Almost nobody makes it on purpose.
3 minRead it - 08July 2026
Evals are the new code review
The gate that decides whether what you built is any good moved. Most teams haven't moved with it.
3 minRead it - 07July 2026
Velocity stopped meaning anything
When everyone ships fast, speed stops being the signal. What you chose to build is.
3 minRead it - 06July 2026
Hire for the PM job that exists now
The job stopped being coordination. Screen for the one who can still build.
3 minRead it - 05July 2026
Smiling exhaustion is a system bug
When one person covers what used to take five, burnout isn't a mood. It's a design flaw.
3 minRead it - 04June 2026
The one-person product org, from the inside
What it's actually like to build the whole surface yourself, agents and all.
3 minRead it - 03June 2026
The model was never the constraint
The constraint was never the model. It's knowing what's worth building and whether the output holds up.
3 minRead it - 02May 2026
Engineering is the only function you can see
Eng has the metrics, so eng gets the credit. The judgment about what's worth building stays invisible.
3 minRead it - 01April 2026
The CPTO is a consequence, not a trend
Collapse product and engineering into one seat and you haven't coined a title. You've revealed one.
3 minRead it
The notes argue the pieces. The whitepaper argues the whole thing.
Twenty pages on what changes when building is cheap and judgment is not. One email, and nothing else happens afterwards.