All Articles
Using Claude's Reflect Monthly Review to Tune a Solo Dev Rhythm
How to read Claude's new Reflect monthly review as a planning tool for the month ahead rather than a report card, grounded in the day-to-day rhythm of solo development.
When a Connector Starts Slowing Down at Night: A Health-Aware Circuit Breaker for Solo Automation
Seeing connector errors and latency is only half the job — the other half is deciding when to route around them. This is my implementation of a circuit breaker that opens on error rate and p95, with runnable Python and notes on wiring it into nightly jobs.
Claude Credit Card Declined: How to Fix Payment and Billing Errors
Getting your credit card declined when subscribing to Claude Pro or Max? This guide covers every common cause—international transaction blocks, billing address mismatches, Stripe restrictions—and gives you clear steps to fix it.
Claude Card Declined: A Complete Troubleshooting Guide for Pro, Max, and API Users
When Claude tells you 'Your card was declined,' the cause is rarely obvious from the error text alone. This guide separates the three layers where a decline actually happens — your issuing bank, Stripe's fraud engine, and Anthropic's account state — and walks you through fixes plus fallback payment methods that almost always get the charge through.
A connector failed for two nights and I never noticed — instrumenting my solo setup after observability went to public beta
The week connector observability hit public beta, I realized my one-person operation had no view into errors or latency. Here is how I wrapped my MCP connector calls in a thin meter and started reviewing it weekly.
When Instructions Fade in Long Conversations: Measuring Adherence and Pulling It Back
System-prompt instructions quietly lose their grip as a conversation grows. This piece turns that drift into a number you can track, then fixes it with prompt structure and mid-conversation re-anchoring, backed by runnable code and measured results.
Claude in Chrome Went GA and I Stopped Babysitting the Tab — Where Background Notifications and Handoff Actually Help
Claude in Chrome's general availability adds background notifications, draft handoff, and better failover. As someone who hands browser work to it daily in solo development, here's what to notify on, what to leave running, and the settings I actually changed.
Three Ways to Start with Claude — Browser, Desktop, and Mobile, and How to Use Each
A clear walkthrough for getting started with Claude on the browser, desktop app, and iPhone/Android — plus how to combine all three so your day flows smoothly. Written from the perspective of a solo app developer who lives across all three.
Pointing Claude Design at Your Codebase: Closing the Design-to-Implementation Loop Solo
The June 17 update lets Claude Design start from your local codebase, so generated assets reflect your existing components. Here is how I wire code-grounded generation into maintaining four sites' UI alone as an indie developer.
When a Long-Running Agent's Context Quietly Decays — Budgeting and Compaction
An agent that runs all night gets sloppier by morning. The cause is dilution from accumulated context. Here is how to treat context as a budget, measure its decay, and keep it healthy with compaction — with working code and field notes.
Three Days of Running Claude Fable 5 Side by Side with Opus 4.8 — Settling My Model Split Before June 15
I ran Claude Fable 5 alongside Opus 4.8 on the same iOS maintenance tasks during the free introduction window. Where the new model clearly pulls ahead, where it does not, and how I split the two before the June 15 billing change.
This Week at Claude Lab: Failures Without Error Messages, and the Guardrails That Catch Them
Editor's notes on five new posts: stale temp-file contamination, .bak files swept up by git add -A, PreToolUse screening hooks, and two Android dialog-flow redesigns.