Hello
Code focus
Day to day
Below is what a project contains when it is mine end to end. The order shifts, but the shape does not: write down what done means, turn that into tests, then build until they pass.
01/03
Before anything is designed, the requirement gets written down as use cases: who acts, what they expect, and what counts as done. Most of what goes wrong later is a sentence nobody wrote here.
The use cases become test cases while the product is still an idea. Verification and validation stay separate on purpose — one asks whether it was built right, the other whether it was the right thing to build.
Then the design and the build: data model, services, the boundaries between them. The tests from step two go into CI alongside the code, so every commit re-answers the question the use cases asked.
What I can help you with
Next.js or Angular in front, Spring Boot, Django, Flask or AdonisJS behind, Postgres underneath. The stack follows the problem, not habit — what does not change is that both ends agree before either one ships.
One Flutter codebase, both stores. Built for the networks your users actually have — offline states and slow connections handled, not assumed away.
Karate DSL on the API layer, Playwright in the browser, running in GitHub Actions behind static analysis gates. Every scenario traces back to a requirement, so coverage means something to the business and not only to the report.
Off screen
I play shooting guard, working off the ball to give whoever is running the offence somewhere to go. I follow the Warriors, and most of what I have learned from watching Stephen Curry happens before he ever touches the ball.
Being where the ball will be, not where it is.
The Last of Us, Uncharted, God of War Ragnarök, It Takes Two — played on an Asus V16. The ones I go back to are the ones where nothing is filler and every system is there to serve the story.
Polish is the last ten percent that makes the other ninety believable.
I am building a multiplayer third-person shooter in Unity 6. Netcode, lag compensation, keeping every player's copy of the world in step the same problems as any distributed system, except here they are felt in milliseconds.
Multiplayer is a distributed system with an audience watching.
I play piano and sing tenor. Mozart, Handel and Haydn for the structure; Franck Mpola and Gaspard Mbole for what Cameroonian composers are doing with it.
A wrong note is audible instantly. Most bugs are not — the discipline is the same.
How I got here
Pategou-Consulting: an AI-assisted legal research tool and a set of Spring Boot chatbots. Also the first time quality was my job as well — an API test framework taken past 85% coverage.
InnovLab TSA, won with a freight platform: AdonisJS and PostGIS behind live GPS tracking for 500 concurrent shipments, Redis in front of the database, deploys automated on GitHub Actions.
A legacy monolith rebuilt as a modular one on Spring Modulith and Java 21, with 44 Karate scenarios mapped one to one onto requirements and quality gates standing between a commit and production.