Six Months In: Building a Thinking Partner · 4 parts · October 2026
Post 1 of 4
I Wanted a Thinking Partner, Not a Tool
My business had gotten stale. When I came back to building this year, AI was the thing that made me want to dream about it again.
Post 2 of 4
Ambition vs Reality: Five Things I Pictured, and What They Became
When I set out to make Claude a thinking partner, I wrote down what I was picturing. I'm glad I did. Reading those notes back six months later is the best recor…
Post 3 of 4
Claude Doesn't Learn. Your Notes Do.
A thinking partner has to remember you. So the question I most wanted answered was simple. Is Claude getting better at working with me?
Post 4 of 4
What a Thinking Partner Is Made Of
I set out to make Claude the perfect thinking partner. I spent a spring sprint testing nearly everything it can do, then three quieter months while the first ve…
What I Learned Building With Claude · 12 parts · June 2026
Post 1 of 12
Verify Everything: How I Stopped Claude (and Myself) From Lying to Me
There's a moment that happens almost every day when you build software with an AI. It tells you the work is done. The bug is fixed. The feature is live. It says…
Post 2 of 12
Don't Ship the Demo: Resilience Before Features
There's a version of every app that works perfectly. The happy path. One user, good network, no edge cases, data well within expected limits. You demo it to a c…
Post 3 of 12
The Four-Reviewer Gauntlet: Reviewing AI Code Before It Ships
Here is a thing that will happen to you if you build software with AI long enough: you will ship a bug that a ten-minute code review would have caught. The buil…
Post 4 of 12
What Building AI Apps Taught Me About Base44
Every platform has a gap between what it promises and what it actually does. The gap is usually small and usually undocumented. You find it by walking into it, …
Post 5 of 12
The Wix Gotchas Nobody Documents
Every platform has its paper cuts. Most platforms document theirs, eventually. Wix CLI — the framework for building apps that install into Wix sites — has a set…
Post 6 of 12
Making AI-Built UI That Doesn't Look AI-Built
There's a tell. If you've used enough AI-generated interfaces you start to recognise it: the cards all have the same radius, the font is a system serif that nob…
Post 7 of 12
Giving an AI a Memory: Building a Second Brain
Every AI session starts the same way by default: from nothing. The model has no idea what you built yesterday, what was left half-finished at midnight, what the…
Post 8 of 12
Telling the Truth in Product Copy
There's a moment when you're building a product page or a marketplace listing and you need a social proof stat. Something to put under the logo. "Trusted by X u…
Post 9 of 12
Docs as You Go: Why I Make Claude Write the README First
There's a specific kind of regret that comes from opening a repo you built three months ago and finding a single-line README that says "coming soon." The code i…
Post 10 of 12
Suggest, Don't Surprise: How I Delegate to AI Without Losing the Wheel
There's a version of AI-assisted work where the assistant just handles things. You describe a goal, it executes, you review the result. Fast, frictionless, and …
Post 11 of 12
The Pivots: Six Months of Strategy I Got Wrong Before I Got It Right
Most posts in this series are about specific, learnable behaviours. Write the docs first. Verify before you claim. Build error handling before the demo feature.…
Post 12 of 12
The Meta-Lesson: Compounding Knowledge Instead of Repeating Mistakes
Every post in this series exists because of one habit: when something went wrong, or right, or surprised me in some way that mattered — I wrote it down.