The engineering blog
Practical tutorials and notes on mobile, backend, and the craft of building software that lasts.
I built an open-source app that's a menu of screens — each one hides a real performance or memory bug, or looks broken but is healthy by design. A hands-on lab for reading Flutter DevTools frame by frame.
Four States alive when only one is visible. Memory climbing every 400 ms. A red frame on reload. All three look like bugs in DevTools. All three are healthy by design — and knowing that is the senior skill.
Choosing a region isn't a dropdown menu: it commits your latency, your bill, your legal standing, and even which services you can use.
Edge Locations, Local Zones, Wavelength, and Outposts: four ways to push the cloud closer than any region can reach — all the way into your own building.
How AWS spreads its infrastructure across the world, and what kind of failure can take your application down.
Dart has a garbage collector, so how can Flutter leak? When something long-lived holds a reference to a State you thought was gone. Three leaks, one rule, and how to catch them in DevTools.
Typing in a search box stutters. A list lags the moment it opens. Both are jank — but one is your Dart code and the other is the GPU, and DevTools tells them apart. Everything you ship has to fit in 16 milliseconds.
A value updates every 500 ms and a grid of cards does work it didn't need to. The problem isn't the counter — it's where the setState lives. A tour of rebuilds with Flutter DevTools, and what the rebuild counter actually means.
You have a widget that should update, but it just won't. Learn how the StatefulWidget lifecycle works — and why yours sometimes won't rebuild.
