Writing
Longer arguments, worked through properly.
Where the newsletter is what happened this week, these are the pieces I keep sending people. Everything here is something I argued badly in a call first and then wrote down properly.
- 3 pieces
- Updated weekly
Coding4 min
The four ways AI coding goes wrong
Bad output from a coding agent is not random. It fails in four recognisable ways, each one caused by a specific thing missing from your brief, and each one fixable before it costs you an afternoon.
Product4 min
Being non-technical stopped being the disadvantage
For four years I ran a company I could not build. I thought that was the thing holding me back. It turned out to be four years of training in the one skill that now decides whether software gets shipped.
Coding5 min
Stop writing prompts. Write the brief.
The reason AI coding tools produce throwaway output for non-technical founders is not the model. It is that a prompt and a specification are different documents, and only one of them survives contact with something that executes literally.
No comments, no newsletter gate, no interstitial. If a piece is useful, send it to someone.
Next
The weekly version of all this.
One email a week on what is actually working: what shipped, what is hype, and the one thing worth your Saturday morning. Written by me, not generated and sent unread.