•5 min read
One API, N Games: Client-Authoritative Event Sourcing for a Unified Game Client
Adding a new board game stopped being a backend project the day the server stopped importing game engines — YINSH proved it in a weekend.
Every post I've published, newest first.
Adding a new board game stopped being a backend project the day the server stopped importing game engines — YINSH proved it in a weekend.
Four weeks took a raw k3s box to 14 Knative functions, FluxCD GitOps, and sub-second cold starts — the layering order that made it work.