What Lagos Taught Me About Software

Lagos doesn't let you be theoretical for long. Everything here is immediate — the traffic, the noise, the pace at which things break and get fixed and break again. Growing up here taught me that solutions have to work now, not in ideal conditions.

I think about this every time I'm building something. The user on the other end of my software might have 2G internet, a phone from four years ago, and three seconds of patience before they close the tab. That's not a hypothetical. That's a Tuesday.

So I build lighter. I obsess over load times. I think about what the experience feels like when the network drops mid-request. I try to make error states feel like a helpful hand, not a wall. None of this came from a course. It came from watching people try to use things and fail, and feeling personally responsible for that failure.

There's a lot of energy in the tech scene here right now — people building real things for real problems, not chasing what's trending in San Francisco. I find that grounding. It keeps the work honest.

Lagos will humble you fast if you get arrogant about what you've made. I'm grateful for that. It keeps me building things that actually work, for people who actually need them.