Principles I Build By

1. Build with Context, Not Just Code

Great software isn't just functional, it's rooted in how real people live, work, and make decisions. I build systems that reflect context: the regulatory rules of finance, the nuance of user experience in emerging markets, or the latency tolerances of global infrastructure. Good engineering starts with good listening.

2. Simplicity Scales

I prioritize clear interfaces, decoupled services, and well-observed systems. Whether it's building money movement workflows or AI-driven backends, I believe in simplicity not cleverness since it what enables reliability, collaboration, and long-term growth.

3. Learn in Public, Iterate in Motion

From publishing experiments to testing ideas with users and collaborators, I learn by building out loud. I use AI tools like Cursor and GitHub Copilot, not to skip thinking, but to accelerate it. I believe feedback loops, not perfection.

4. Lead by Unblocking, Not Controlling

As a lead, I make the team faster by removing friction: clearing ambiguity, streamlining processes, or writing the unglamorous but necessary glue code. Leadership is less about directing and more about building momentum others can plug into.

5. Stay Useful, Stay Curious

From my first test automation frameworks in East Africa to fintech services in the U.S., I've followed one north star: be useful to others. Whether it's a teammate, a product, or a whole community, the point of all is to enable something greater than the code.