I served every client in a single morning, and somewhere around the third one I realised I hadn't opened a browser. The speed wasn't the point — it was what I could see when the walls between my data sources came down.
I retrofitted 45 files in one commit — every insight on the site got a standfirst and a pull quote in minutes. That's what happens when your content lives in the same repository as your code.
Instructions tell the system what to do. Characters make the wrong thing impossible. Why I stopped writing rules for AI and started installing people instead — and why the obvious candidates all failed.
The prompts don't improve. The corrections do. Eight months of catching the system when it drifts — on voice, on meaning, on honesty — is why the output sounds like a specific person wrote it.
A rule without a face is an instruction. An instruction can be ignored. Why naming principles after characters — Joe Gargery, Robert Maxwell, Marco Pierre White — produces something that lasts longer than a policy document.
Cursor, Windsurf, Lovable — the debate about which IDE is best misses the point entirely. The interface that matters is the terminal. A Telford web developer on why dashboards are friction cosplaying as security.
I treated commits like save points for years. Moving to atomic commits so Claude Code could read the history changed how I run the business.
I built a 4,978-line context file for Claude Code. It collapsed. Then I built a 500-page wiki. That drowned. Three failures taught me an architecture I couldn't have designed from scratch.
Claude Code builds whatever you ask for. That's the problem. Getting it to reach for what already exists — and stay there — took four months, fourteen templates, and one very deliberate refactor.
Claude Code executes. Claude.ai reasons. But unless you close the gap between them, the left hand can't see what the right hand is doing. A Telford web developer on why your tools need a corpus callosum.