The Latency of Physical Things

The heat in this Gbagada workstation is doing its best to melt my focus, and the news about the Strait of Hormuz isn't helping the vibe. It is easy to look at headlines about naval escorts and think it’s just another "world out there" problem. But for those of us trying to ship products from Nigeria, physical latency is just as real as a 500ms ping on a poorly optimized API.

Hardware is the New Software Bottleneck

Every time a major shipping route gets shaky, I start thinking about the cost of MacBooks in Computer Village or the price of solar inverters for a setup in Jos. We spend so much time optimizing our React components and worrying about tree-shaking, but we forget that our entire livelihood depends on physical hardware that has to cross oceans.

If the US Navy is out there escorting ships because of threats in the Strait, that is a direct signal that my next server upgrade or the Raspberry Pi I need for a side project is going to cost more. It’s "Sapa" on a global scale. We’re already battling an exchange rate that makes you want to scream into a pillow; we don't need the actual supply chain to "no gree for anybody" either.

From Onitsha to the World

I remember talking to a guy in a chaotic bus park in Owerri who was trying to move spare parts he’d imported. He didn't care about the high-level politics; he just cared that his tracker showed his container was sitting idle.

As developers, we often feel insulated because our "output" is just bits and bytes moving through fiber optic cables. But the reality is that the "how" of our execution depends on the tools we can afford. When shipping gets complicated, the local tech market feels the squeeze immediately. Small business owners in Onitsha or tech bros in Akure all feel the same pinch when the cost of logistics spikes.

Resilience is the Only Stack That Matters

The news about missing troops in Morocco and hospitalizations in the US just adds to the feeling that the world is currently a buggy beta release. But if being a dev in Nigeria has taught me anything, it’s how to build for resilience.

We write code that handles intermittent internet, we build apps that work offline, and we figure out how to source hardware when the main channels are blocked. Whether it's navigating a messy codebase or a messy global trade route, the mindset is the same: find the workaround.

I’m currently looking at a project that requires some specific sensors. Seeing these headlines makes me want to pull the trigger on the purchase today rather than tomorrow. In this ecosystem, waiting is a luxury we usually can’t afford.

The world might be acting up, but the grind doesn't pause. I’ve got a bug in my auth flow that needs more attention than the news cycle anyway. Back to the terminal.