My AWS Bill is doing parkour again

I woke up this morning to a cold breeze here in Jos that made me want to stay under the duvet forever, but the headlines coming out of the Strait of Hormuz and China were enough of a caffeine kick. People think because I spend my day staring at VS Code or debating API architectures, I’m insulated from whatever is happening in the Middle East or some factory in China. I wish.

Every time a boat gets blocked or a factory goes up in flames halfway across the world, my runway gets a little shorter. It's the invisible tax on being a developer in Nigeria.

The USD ghost in the machine

When the Strait of Hormuz gets tense, oil prices act like they are on a trampoline. For us, that doesn’t just mean the price of fueling a Gen is going up—it means the Naira is about to catch a cold. And when the Naira sneezes, my tech stack gets pneumonia.

I’m currently looking at my billing dashboard for a side project hosted on AWS. It’s billed in dollars. My domain renewals? Dollars. My GitHub Pro and Vercel hobby plan? All dollars. When global markets panic over shipping lanes, the exchange rate volatility makes budgeting for a startup feel like trying to nail jelly to a wall. You go to bed thinking you’ve optimized your spend, and you wake up to a 15% "geopolitical surcharge" because the currency devalued overnight.

It makes you think twice about "serverless" everything. Suddenly, the idea of hosting on a local box or finding a provider that doesn't charge in USD feels less like a retro hobby and more like a survival move.

Shipping delays and the hardware hustle

Then there’s the news about the fireworks factory explosion in China. It sounds tragic, but from a builder's perspective, it’s a reminder of how fragile our supply chains are. Whether you are a hardware guy in Aba trying to source components or just a dev in Gbagada waiting for a replacement MacBook screen, these disruptions are a headache.

I have a friend in Onitsha who’s been trying to bring in some IoT sensors for a smart-metering project. Between the shipping lane drama and manufacturing hiccups, his "three-week delivery" is now entering its third month. You can't "agile" your way out of a physical shipping container being stuck or a factory being leveled. It stalls innovation. It kills the momentum of the "No gree for anybody" mindset we try to maintain.

Optimization is the only way out

So, what do we do? We can't fix the Strait of Hormuz from a workstation in Nigeria. But we can change how we build. I’m spending my afternoon today auditing our dependencies and seeing what we can prune. If the world is going to be this volatile, our software needs to be lean.

I’m talking about aggressive caching to save on egress costs and maybe finally moving that one cron job off a paid tier into something more sustainable. We’re in an era where "efficiency" isn't just about clean code—it's about financial resilience.

Building tech here is already a high-stakes game. Adding global instability to the mix just means we have to be smarter than the guys building in San Francisco. They have the luxury of burning VC cash on inefficient queries. We don't. We have to code like every millisecond costs us a liter of fuel.

Time to get back to the terminal. These bugs won't fix themselves, and the servers aren't getting any cheaper.