Hello, and what this is for
Why I built a site instead of posting in threads, and what you can expect to find here.
Mexico City
Backend engineer. I make messy systems boring.
Backend engineer with 10+ years building marketplaces, e-commerce, fintech and logistics platforms. I write about APIs, migrations that don't wake you up at 3am, and the unglamorous parts of scaling.
Why I built a site instead of posting in threads, and what you can expect to find here.
Swapping the delivery layer under a live notification system for ~90M users, without dropping a message or sending any twice.
The fastest way to ruin a backend-for-frontend is to treat it as a pass-through. The value was never in the forwarding.
This site. A statically exported Next.js blog with a Go CLI for authoring.
Every page is a file on a CDN — no database, no API, no runtime secrets. The interesting constraint was keeping it that way: embeds are click-to-load, tweets are stored as data instead of scripts, and a small Go binary validates frontmatter before anything reaches main.
FCM → Braze migration and end-to-end experimentation for a marketplace with ~90M buyers.
Replacing the delivery layer under a live notification system without dropping messages or double-sending them. Most of the work was in the seams: idempotency, backfills, and a shadow-write period long enough to trust the numbers.