|

I care about the craft of building software more than the speed. Not because velocity doesn't matter — it does — but because the systems we build outlive the sprints we run. I want the things I make to still make sense a year from now.

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 infrastructure that millions of people depend on, platforms connecting engineers across a continent that's often an afterthought in product decisions. 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.

I build things that I hope are worth building.