Defensive programming
Small guards, idempotent paths, and regression tests that can fail for the right reasons.
A small email list for AI workflows, defensive programming, delivery loops, and the practical lessons that make software easier to trust.
~/dispatch
I send notes when there is a real pattern to keep: a test shape, an agent loop, a deployment habit, a team practice, or a small tool that removed friction from the work.
No drip sequence. No generic roundup. Just notes worth sending.
Small guards, idempotent paths, and regression tests that can fail for the right reasons.
Agent prompts, repo rules, and evaluation loops kept close to the code they change.
CI/CD habits, generated contracts, and release paths that help teams keep shipping forward.