Module Federation
Five teams, one app, zero shared deploys
A single React monolith was holding five teams hostage to one deploy train. Here is how we broke it into federated micro-frontends without the product falling apart at runtime.
Work
Case studies
Four writeups of real systems work. Three are from a long run on a regulated, high-scale platform, with the employer and product kept deliberately vague. The fourth is infrastructure I own outright, which is the one I can show you end to end. They are written to explain how the problems were reasoned about, not to pad a list.
Production Quality Engineering
Six ways to fail a build before it reaches production
Regulated intake flows where "it works on my machine" isn't a defense. A look at the six testing layers that each catch a different class of bug, and why the two everyone skips are the two that matter.
Reliability & Observability
The frontend isn't done when it renders
Observability, blue-green delivery, and rollback as a first-class idea. The enterprise version I can only describe, and the version running on my own hardware that you can poke at right now.
Reliability & Observability
Running my own infrastructure
A self-hosted stack on Proxmox behind Cloudflare and Caddy, running real services I depend on daily. It's where I keep the operational instincts sharp that contract React work tends to let atrophy.