Sign in Subscribe

Topic

Claude Code

A collection of 28 issues

I built a client performance dashboard in a day with Claude Code — the hard part was not calling enquiries revenue

A lead-generation business that takes no payment online. Four APIs disagreed with their own documentation, but the decision that mattered was what to call the biggest number on the page.

My scheduled Claude Code routine failed three weeks running: what agentic workflows need that a written lesson doesn't give them

An AI automation that couldn't unblock itself, scheduled in a context where the one thing it needed was impossible. Why agents must know what their execution environment can do — and why a well-written lesson with no owner changes nothing.

The audit found eleven missing receipts. Nine of them existed.

An automated gap report compared bank lines against an index that only knew one of several folders. The fix wasn't a smarter matcher — it was an index that could prove it saw everything.

OpenAI built a whole browser for the agent. The agent didn't need one.

Claude Cowork just got a built-in browser, seventeen days after OpenAI switched off Atlas. The improvement isn't the browser — it's that there are finally two modes, and knowing which job belongs in which one.

I scheduled a weekly check that could never run.

An automated SEO check that needed a browser on my laptop, scheduled in the cloud. Designing a measurement window that can honestly report nothing was the real work.

Everything returned 200. Four leads still went nowhere.

Three things broke on my own projects this week and not one of them produced an error. Silent failures are the expensive kind — here is what I changed so the systems shout.

The AI slop nobody logs: the 20-page doc that makes its problem your problem.

There's a hidden tax on teams right now: polished AI output that shifts the thinking onto whoever opens it. The real skill was never volume. It's what you cut.

My assistant created the same task three days running. The fix has a name: idempotency.

A tiny automation bug taught the same lesson payment systems learned years ago: the question isn't whether it runs, it's what happens when it runs again.

Four versions of the same email sat in my drafts. This morning, the tool just edited one.

Claude's Gmail connector now updates drafts in place instead of duplicating them. A small fix — and exactly the kind that turns AI tooling from a demo into something you trust daily.

A context window is working memory, not a hard drive. Feel that, and you manage AI differently.

The AI doesn't remember everything you've told it. It has working memory, and it's finite — here's the cheap trick I use to hear it filling up, and the fix when it does.

Work with me →×