Services

Three ways this usually works

I take on web, mobile and systems work where correctness matters more than shipping speed. Most engagements look like one of these.

01
Build it from nothing
You have a product and nothing built yet. I design the data model, the API surface, the client and the deployment path, then build and ship them. You end up with something your own team can maintain, not something only I understand.
Best when the domain is complex and getting the model wrong early would be expensive.
02
Fix what's already running
Something is already live, and it is slow, fragile, or frightening to deploy. I work inside the constraint that it has to keep running. On the Zimdoc EMR that meant 92ms down to 30ms with no rewrite, and a pipeline that took deploys from three minutes to fifteen seconds.
Best when a rewrite has been suggested and you suspect it's the wrong answer.
03
Join the team
You need another senior engineer for a defined stretch, on any layer of the stack. I match your conventions and review process. I don't introduce my own preferences into a codebase other people have to live with after I go.
Best when you have the direction and need the capacity.

What you can hold me to

Replies within one business day
Including the replies that say no. You'll never be left wondering whether I saw your message.
Real time zone overlap
WAT (UTC+1). A full working day with the UK and Europe, roughly four hours with the US East Coast.
Estimates that hold, or change loudly
If something slips, you hear it when I find out, not at the deadline.

Where I am, and when

I work remotely from Lagos, Nigeria. There is no office to visit, so here is the thing that actually matters: when our working days overlap.

Core hours 09:00 – 18:00 WAT, Monday to Friday · WAT (UTC+1)

The more specific you are about what worries you, the more useful my first reply will be. Not sure yet? The FAQ covers most of it.