Software engineer · Accra, GH
I build software that keeps working after the demo. My work lives in the gap between a prototype that works once and a system that survives reality.
Currently open to work.
01 / Selected work
Services built to learn what happens after the tutorial ends: workers, retries, tokens and connections that drop.
All code on GitHubCollaborative publishing for careful writers. Contributors suggest line-by-line edits, the owner reviews each proposal in a thread, and nothing merges without approval. Named version snapshots keep the working draft separate from what is published.
Uptime monitoring service. Probes HTTP/TCP endpoints globally and logs health metrics. Developed as a deep dive into background workers and handling long-running tasks.
Standalone authentication service with JWT + refresh token rotation, OAuth2 social login (Google, GitHub), rate limiting, and audit logs. Designed to be drop-in for any project.
WebSocket notification hub with room-based subscriptions, delivery guarantees, and fallback to Server-Sent Events. Handles 10k+ concurrent connections with Redis pub/sub under the hood.
A real-time attendance system that replaces traditional paper based attendance taking, utilising real-time location information to validate presence.
02 / Writing
What I learned building these services, written down while it was still fresh. Mostly things the tutorials skipped.
Why a lean asyncio worker beat reaching for Celery, and what deploying it taught me.
Short-lived access tokens, rotating refresh tokens, and why the old one dies immediately.
Ghost connections after a restart, and the two engine settings that made workers recover.
3 AM sessions, rejected applications, a first deploy that crashed, and why I'm not stopping.
03 / The toolkit
Python first. Everything around it is there to get a service built, tested, shipped and kept alive.
Primary language
Web framework
Relational database
ORM and queries
Caching and queues
Task workers
Containerisation
Reverse proxy
CI and CD
Validation
Migrations
Testing
04 / About
Software Engineer. Python and FastAPI, for now. I tried the UI route for a bit, but moving things around and coloring stuff wasn't all that fun—I realized I care more about the logic under the hood than the buttons on the dashboard.
My work lives in the gap between a prototype that works once and a system that actually survives reality. I’m a firm believer that programming is learned by breaking things, fixing them, and having the grit to stay above the noise.
Outside this, I'm probably making beats, car spotting or watching anime. You can checkout some of my beats here.
05 / Contact
Open to software engineering roles and collaborations. Email is the fastest way to reach me.
Rather see the code first? Find me on GitHub