Why I Built a Pokémon Game on Top of Kubernetes The thing that broke me was watching a junior dev stare at kubectl get pods -A output for 45 seconds, completely lost. Not because they weren’t smart — they just had no mental model for what a cluster is. Every dashboard I tried to hand … Read more
The Problem: Your CI Pipeline Takes 12 Minutes to Build a 2GB Image A 2GB image that takes 12 minutes to build on every push isn’t just annoying — it’s a compounding tax on your entire team. Every feature branch, every hotfix, every “just a one-liner” commit burns 12 minutes of CI time. Multiply that … Read more
The Problem: Plain QR Codes Look Terrible on Marketing Materials The thing that caught me off guard was how violently designers react when you hand them a standard QR code. Black squares on white. No personality. They’ll drop it into a brochure and immediately ask if they can “make it look like something.” The functional … Read more
The Problem That Started This The requirement landed in a Notion doc three weeks before sprint planning: customers needed to configure custom parts — think L-shaped brackets, enclosures with variable wall thickness, mounting plates with parametric hole patterns — directly inside our SaaS dashboard. No file uploads, no “download and open in Blender”, no installer … Read more
The Problem That Made Me Care About This I was staring at an AWS bill — $4,200/month on EBS volumes for a single Elasticsearch cluster — and couldn’t figure out where it was going. The indexed documents were large but not that large. After a week of digging with the _cat/indices API and some segment-level … Read more
Why I Keep Reaching for Durable Functions (And Where People Get Lost) The thing that pushed me toward Durable Functions wasn’t some architectural epiphany — it was a cron job graveyard. I had a payment retry workflow split across three Azure Functions, a storage table acting as a makeshift state machine, and a timer trigger … Read more
The Problem: Game Logic That Fights Your Code The cutscene example is one I keep coming back to because it’s so brutally mundane — yet it exposes the exact fracture between how programmers think about game logic and how we’re forced to implement it. You want to express: walk to door, wait 2 seconds, open … Read more
What Actually Happened to Canonical’s Infrastructure The attack surface Canonical operates is genuinely unusual — ubuntu.com isn’t just a homepage, it’s load-bearing infrastructure for millions of automated processes running 24/7. Every apt update, every CI runner pulling fresh package indexes, every snap daemon phoning home on a timer, every PPA pipeline in Launchpad — they … Read more
The Console Is Lying to You (By Omission) The thing that breaks your focus isn’t the bug — it’s spending four minutes scrolling through console noise trying to find the bug. A real Next.js app with Segment analytics, Intercom’s chat widget, and a lazy-loaded Google Maps SDK will dump somewhere between 150 and 300 console … Read more
The Problem That Made Me Actually Care About Storage Engines Write latency went from 2ms to 400ms in about 90 seconds. No deployment had happened. No traffic spike. The cluster metrics looked fine — CPU at 40%, heap usage normal, no GC pressure. My first instinct was to blame the query pattern, so I spent … Read more