The column · weekly · free
One written piece a week
What broke, what it cost, and what rule changed because of it. Newest first. The same text goes out by email the morning it is published.
Get it by email. One mail, when there is one.
- · № 6
Second Brain for Business: Why I Put Everything in One Database
A one-operator guide to a second brain for business: 547 tables across four schemas in one Postgres database, holding clients, quotes, invoices and bookings.
12 min read - · № 5
Claude Code Workflow: Why Your Green Gate Might Be Lying to You
A green gate is a claim, not a receipt: my Claude Code workflow ran a migration in production twice and passed a run missing 3 of 10 tasks. Here's the fix.
18 min read - · № 4
Claude Code Subagents Headless: Why a Hook That Can't Ask Must Refuse
Headless Claude Code subagents can't show questions, so a hook guard must refuse. Measured: hooks run in claude -p, deny rules hold, slash commands don't.
16 min read - · № 3
Claude Code Limits: Why Your Context Hits the Wall First
Claude Code limits are context, not quota, per a 30-session audit: 26 compactions, peaks of 782k tokens, and a 60-minute cache timer. Get the real numbers.
17 min read - · № 2
Claude Code Hooks: Count Your Refusals Before You Write One
Before writing Claude Code hooks, count your refusals: 48 refusals in 11 runs fell to about 1 per run with six allow rules.
16 min read - · № 1
Private repo, public lesson
Most of what I build is in private repositories, and this site promises to build in public. Why those do not disagree, and the one switch every fix now carries.2 min read
See what broke for me, and the repair
Every production failure on my own apps, written up while it is still open: what happened, what it cost, how I fixed it.
The columns, fixes and workshops continue in the community: SEO, AI, and making money with code.
Join on WhopLuke Sidney writes and builds everything here, alone, in the open. lukesidney.me