The slow
accumulation
of taste.
Twelve years of being slightly less wrong about software, every year.
B. Nkrumah
Twelve years ago I wrote my first line of PHP in a computer lab at KNUST. The internet was slower, the deadlines were softer, and I was wrong about almost everything. I have spent every year since being slightly less wrong, which is the best thing I can say about a career in software.
Today I build agile, reliable, enterprise applications — mostly on the LAMP stack, mostly on Laravel, mostly for teams that need a system to stay up at 2am while someone else's pager handles the noise. I have worked as a senior engineer at financial institutions in Ghana, a clinical research centre building LLM-backed healthcare tools, and a US-based company where the engineering bar — PHPStan level 9, mutation testing, 85% coverage — reset my standards permanently.
I am not a framework evangelist. I pick boring technology when boring technology is right. I pick the new thing when the problem demands it. The system's uptime is the review score that matters.
What I do
I design and build backend systems — OAuth2/OIDC identity providers, double-entry accounting engines, REST APIs, queue workers, multi-tenant SaaS platforms, and the infrastructure underneath them. My specialty is the gap between "works on my machine" and "works at 2am under load."
I write PHP and Laravel primarily, with MySQL, Redis, and a Linux terminal always nearby. I have built financial systems for rural banks and credit unions, integrated Temenos T24 core banking APIs, shipped LLM-backed clinical decision support tools, and built RAG pipelines with Python and FastAPI. The AI-augmented development loop — short sprint, rigorous review — is now core to how I work.
Timeline
The best systems are boring.
Boring means nothing caught fire.