✦ 0 XP Open to meaningful collaborationsLet's talk ↗
THE STORY SO FAR

A life in
continuous learning.

Not a straight line. A series of questions, people, hard problems, and small breakthroughs. Here are the chapters that shaped the builder—and teacher—I am today.

↗2025 — NOW

Building the bigger picture

Chief Technology Officer · QuickerPay

Leading architecture, mobile and backend engineering, payment infrastructure, and the team practices that make it all work.

⌘2024 — 2025

Learning to see systems clearly

Lead Backend Developer · FaultPilot

Worked on real-time monitoring, database optimization, mentoring, and engineering standards.

◇2024

Deep in the world of payments

Senior Backend Developer · Paysika

Built fintech APIs, referral and rewards systems, transaction search, and reporting features.

+2023 — 2024

Code with real-world consequences

Zeze Health & Eldorado Smart Payment

Contributed to AI-assisted healthcare workflows and payment gateway infrastructure.

▧2020 — 2022

Laying the foundations

Backend Developer · Immobis

Built property and rental services with Django and PostgreSQL, growing my practice in performance and reliability.

✦2019 →

A teacher at heart

Computer Science Educator · GBHS Emana

Teaching programming, algorithms, databases, and digital literacy. Mentoring curious minds and connecting classroom concepts to real software.

⚑2019

The first unlock

ENS Maroua · Computer Science Education

Studied computer science with a minor in mathematics at ENS Maroua, earning the DIPES I teaching qualification.

COMMUNITY / ON STAGE

Sharing beyond the classroom.

Taking the lessons from building software into the Python community.

SPEAKER / PYCON CAMEROON 2026Yaoundé, CameroonDay 1 · Koki · English13:35–14:10 · 35 minutes

From WSGI to ASGI: Modernizing Django

I explored how Django applications can move from traditional request–response handling to real-time updates and async I/O. A live payment-balance example connected the concepts: replace repeated polling with WebSockets, route connections through Django Channels, and deliver committed changes through a shared Redis channel layer.

We compared Daphne and Uvicorn, with a look at Hypercorn and Granian, then worked through the production details: authentication and origin checks, publishing after a database commit, reconnecting and recovering state, rejecting stale updates, and rolling out ASGI while keeping existing HTTP views working.

The takeawayReal-time delivery needs a recovery path. Keep the database authoritative, expect connections to fail, and measure the complete system before claiming a performance improvement.
30 slides · Django, Channels, WebSockets & deployment
NEXT CHAPTER

Still becoming.

The most interesting part of this story hasn't happened yet.