Fable 5 is back. My terminal still hands me the junior.
Fable 5 returned on 1 July — but Claude Code still defaults to Opus 4.8. A senior partner in one window, a junior developer in the other. Know which one you're talking to.
Remco Livain
The best dental leads don't come through the dentist. Distributors keep missing that.
I've built consumer-facing brands on top of B2B dental products for one of the industry's largest producers. The mechanic — patient demand that doesn't originate with the practitioner — is the most defensible growth move European dental distributors aren't making.
I made the page beautiful before the site had traffic. That's the right order.
Proof-of-concept-first design: build a genuinely good experience before the analytics and monetisation plumbing — and use click-to-load facades to dodge privacy debt.
I switched off a dozen campaigns this week. Off had to mean off.
Event-tied campaigns have a shelf life. Cutting a whole cohort cleanly — pause not delete, consistent naming, an eye on the learning phase — is its own discipline.
I let AI reorganise my whole workspace. The dangerous moment was a find-and-replace.
Handing a sweeping reorg to an AI works when an approval gate sits in front of the irreversible steps — like a blanket find-and-replace that nearly inverted a privacy guard.
Yesterday's ad spend kept landing on today. Two bugs were wearing one costume.
A dashboard that's reliably off by a day isn't rounding. It's a timezone day-boundary problem — plus a self-heal that invented an estimate and showed it as a booked fact.
Fake testimonials are a liability now. I deleted mine and the rating went down.
Invented testimonials are a legal exposure and a conversion problem. I swapped them for real reviews — and lowered an inflated rating to match reality.
I designed an app in Claude before building it. Claude Code shipped it in a day.
My first time using Claude Design to plan and prototype an app before handing it to Claude Code. A cross-channel client reporting tool, designed and built in under a day — and what it means for my use of Lovable.
I merged four sales channels into one number. Then I proved it was right.
Building a unified multi-channel revenue dashboard took an afternoon. Reconciling it against the source of truth took the rest of the day — and that's the part that matters.
I taught my assistant to prep my week. The hard part was making it stop starting over.
A daily routine that prepares for upcoming commitments sounds simple — until it regenerates a different draft every morning. The fix came from API design: idempotency.