Engineering

This is the core of what I do - building systems that actually hold up under pressure. You'll find stories here about architecting for scale, designing systems that are operable, maintainable, and fast, and navigating the trade-offs between speed and stability. It's the kind of work that happens after the MVP: where infrastructure, latency, observability, and team velocity start to matter.

The Bug Was the System

The Bug Was the System

We fixed the tools. We cleaned up the code. But something still felt off. Everyone was doing their job, but velocity kept slipping. I couldn’t shake the feeling that what we were fixing wasn’t the thing that was broken.

Flutter Is Taking Over

Flutter Is Taking Over

I started out writing native code and believed in it fully. But Flutter has evolved into something rare - a truly cross-platform system that doesn't feel like a compromise. In 2025, it's earning its spot as a real default.

Why We Made Copilot Mandatory (and Would Do It Again)

Why We Made Copilot Mandatory (and Would Do It Again)

Everyone said "just try it," so we did. Then we made it non-optional. Not because we love AI, but because we hate wasting smart people’s time on dumb stuff.

Best Fruit is Forbidden

Best Fruit is Forbidden

The idea of rewriting everything from scratch is tempting clean code, faster builds, fresh tech. But clean slates come with real costs. Here's a more honest take on why backend rewrites feel right, but often aren't.

Node.js vs Golang: A Practical Deep Dive

Node.js vs Golang: A Practical Deep Dive

Go or Node? One is ergonomic, the other is a performance beast. After 8 years of building products in both, here's what scales, what breaks, and when to switch.

Smart Polling in Flutter: Build It Once, Run It Right

Smart Polling in Flutter: Build It Once, Run It Right

Most polling in Flutter is wasteful. This post shares a production-ready Dart class that handles lifecycle, timeouts, and smart intervals no spaghetti timers.