Software architecture, AI-first engineering, ADRs, domain-driven and event-driven design, databases, CI/CD — and how I actually build, day to day, with AI in the loop. Long-form when it earns it; short notes when it doesn't.
No free managed tier will email your list the moment you publish — that's the feature kept behind the paywall. So I didn't rent it. This site's newsletter is three small pieces I already run for free: a static form, a serverless function that holds the API key, and a CI job that broadcasts on publish.
Read the postAn implicit decision left unenforced becomes 40 services split 60/40 between two incompatible identifier shapes. Here's the standard I wrote to close the door — and why ULID won.
Why every state-changing event in the Ghasi suite goes through a transactional outbox instead of a direct publish — and what that costs.
Time and randomness are infrastructure. When every service rolls its own clock port, you get six file paths and three interface names for one concern. The fix is one platform port — and the testability it unlocks.
Most platforms bolt AI onto a non-AI core. Treating it as foundational architecture — a single governed gateway, provenance on every artifact — changes what you can promise.
When I publish on architecture, AI engineering, or the systems I'm building, you'll be the first to know.