Skip to content
About / esc to close

About

The long version, for anyone who asked.

At StartButton Africa, I worked on event-driven systems supporting payment workflows across 15+ African markets. My work involved asynchronous processing, retries, idempotency, external integrations, and reconciliation: the engineering challenges of keeping distributed workflows reliable when real-world systems don't behave as expected.

Previously, I led frontend engineering at PadiePay, building web, administrative, and mobile applications, and worked across backend services and cloud infrastructure at Senta Finance. At Breezelearn, I connected production APIs to Python ML services supporting more than 250,000 inference requests daily at under 400 ms.

My experience spans React, React Native, Next.js, TypeScript, Node.js, Java, Go, Python, PostgreSQL, Redis, event-driven architectures, AWS, Kubernetes, and Terraform. I've worked across the application and infrastructure layers, from the interface a user interacts with to the services, data stores, and deployment pipelines behind it.

The industry changes. The underlying engineering challenges often don't: maintaining data integrity, designing clear service boundaries, handling partial failure, improving performance, and making complex systems easier to operate.

Alongside my engineering work, I build CodeScape, a tool for exploring codebases as interactive cities, and RelayMQ, a lightweight, local-first message broker written in Rust, with built-in observability and a live view of every message's lifecycle. I also create Engineering Judgment, where I share practical lessons about technical decisions, trade-offs, systems thinking, and what it takes to build software that works in the real world.

I studied civil engineering at Rivers State University before pursuing computer science at the University of East London.

I'm interested in solving hard engineering problems wherever they appear: product engineering, platform infrastructure, distributed systems, developer tools, and AI systems.

I care about building software that works, not just when everything goes right, but when things get complicated.