Same message, different outcome: determinism in event-driven architecture
Why does the same message produce different outcomes in an event-driven system? The hidden inputs that break determinism — and four moves to win it back.
Blog
My hands-on development journal: PHP and Laravel, Go, JavaScript and TypeScript, developer tools and career. Architecture writing lives in Engineering. (Page 3/17)
Why does the same message produce different outcomes in an event-driven system? The hidden inputs that break determinism — and four moves to win it back.
Writing a Go CLI is half the work; versioning it, cross-compiling it and distributing it so others can install it effortlessly is the other half.
A role gap closed by individual sacrifice becomes invisible — and an invisible fault never gets fixed. Drawing a boundary, from three desks.
Process isn't a virtue — it's a coordination tax you pay. When it should be added, why it never gets removed, and how it looks from three different desks.
Companies don't fail at going fast or going slow — they fail at matching the speed to the decision. A reversibility frame, and three desks to view it from.
What separates company types isn't headcount but where decisions are made and how much reasoning gets written down. Four axes, three desks.
TypeScript's compiler ported to Go: why Go, why a fast feedback loop matters so much to developers, and what the move teaches a polyglot.
Architecture decisions rot in the code. One architecture.json lets archlint enforce Go, TypeScript and Python boundaries in CI on every commit, no model.
I added a deterministic flaky-test filter to CommitBrief: it catches hard-coded sleeps and unseeded randomness at commit time, with no model.
Two new commands: summary briefs a change and its history, and remote pr reviews a PR from the terminal, leaving comments before the human does.
Vibe coding made shipping easier, but what someone without systems knowledge ships isn't what a senior steering the AI ships. Three levels.