Blog
Notes from building Stoicsoft. Tools, processes, and the occasional rant about software that wastes your time.
Showing 51–59 of 59 · Page 6 of 6
engineering· May 5, 2026· 6 min readHow to CI-Validate Your CLAUDE.md Across Every Repo
CLAUDE.md drifts silently across repos. A 30-line bash CI check catches it before policy gets quietly deleted.
engineering· May 5, 2026· 6 min readThe Five-Field Template That Stops Billing Tickets From Escalating
Billing escalations don't escalate because of the original error — they escalate because of the response gap. A structured template that closes the gap.
engineering· May 5, 2026· 7 min readModel and Cost Controls Belong in Your AI IDE's Defaults, Not Buried in Settings
Sensible defaults for tier-by-task, session ceilings, and visible cost meters turn AI tools from runaway-spend risks into predictable line items.
engineering· May 5, 2026· 6 min readContext Reset Patterns for Long AI Coding Sessions
Long AI sessions drift. The fix isn't a bigger context window — it's three explicit reset patterns and a habit of curation.
engineering· May 5, 2026· 6 min readWhy Short Diagnostic Commands Beat Long AI Explanations
Five-second commands beat 200-word advisory blocks for the first turn of any debugging conversation. The principle and what it means for AI assistants.
engineering· May 5, 2026· 7 min readWhy Billing Transparency Is the Hidden Trust Lever in Every SaaS
Billing escalations don't escalate because of the original error — they escalate because of the response gap. Here's the structured fix.
engineering· May 4, 2026· 9 min readWhy Your Infrastructure Setup Order Matters (And How to Get It Right)
Identity → substrate → services → integrations. A four-stage mental model for setting up infra in the right order, every time.
engineering· May 4, 2026· 8 min readThe Underrated DevOps Practice: Preflight Scripts That Prevent Regressions
Most teams discover preflight checks the same way: an outage. Here's the pattern, why it's so cheap, and what to put in yours.
Decision-annotated terminal sessions: the rationale layer async handoffs are missing
Plain command history tells you what happened in a terminal session. It does not tell you why. For remote teams handing work across timezones, the rationale layer is the part that decides whether tomorrow's engineer reproduces the fix or relitigates it from scratch.