|

I care about craft more than velocity. Not because speed doesn't matter — it does — but because the systems we build outlive the urgency that produced them. I've noticed a pattern in the things I find most satisfying to build: they tend to solve the problem in a way that makes the next version of it harder to have.

My work sits at the intersection of infrastructure and product. I'm drawn to the invisible architecture that holds everything together: the pipelines, the contracts between services, the decisions made at 2am that shape what users experience months later. I find that gap interesting.

Outside of code, I think about systems in other forms — language, cities, music. The same principles keep appearing: constraints create clarity, silence carries meaning, and the most important decisions are the ones that feel obvious in retrospect.

I'm from Nairobi. I've spent most of my career building systems where failure has real weight — payment pipelines integrating M-Pesa and Paystack for retail platforms across Kenya, logistics systems tracking deliveries in real time, marketplace infrastructure where trust between strangers is the product. That context shapes you. You stop thinking about code as an abstraction and start thinking about it as something that either holds or breaks in the moment someone needs it.

Some of what I build is software. Some of it is the environment in which other people build — the standards, the processes, the culture of a team. I've found that work quieter and harder to explain, but often more meaningful. The thing matters. But the conditions that make good things possible matter just as much.

I build things that I hope are worth building.