WooCommerce checkout race conditions: what broke, and what we fixed
A production checkout bug only triggered on peak load—once we forced idempotency, the incident stopped recurring.
Read moreJournal
Notes on agentic development.
How to turn AI into real shipping speed: audits, workflows, modernization, and the tactics that hold up in production.
More writing: Ironcrest Software blog and 815 Media blog.
Checkout bugs that hide in cache and permissions are the real threat
The fastest reliability wins came from three failures: checkout races, headless ISR stale caches, and multisite role ghosts.
Read moreIf there’s no reversible decision record, it’s not AI for regulated work
We shipped guardrails first: audit trails, reversible decisions, and kill-switches—because regulated workflows punish “magic.”
Read more“It worked in staging” fails when WooCommerce checkout isn’t idempotent
We hit phantom order attempts because checkout wasn’t idempotent under retries—staging hid the race condition.
Read moreTreat llms.txt like an API contract or you’ll ship outages
We watched answer engines hallucinate because llms.txt drifted; the fix wasn’t “better prompts,” it was versioned contracts.
Read moreIf you can’t disable it instantly, it’s not an AI feature
A kill-switch isn’t paranoia—it’s the difference between a safe rollout and a compliance incident you can’t explain.
Read more