Software developer · Lomé & remote
Service 04 — Training & team upskilling
Level up your team, don't replace it
Short, hands-on sessions built on your own code rather than a sample project. Your developers leave with habits they can apply the next morning — and with someone to ask in the weeks that follow.
- On your repositories, not a toy project
- 2 to 5 days
- On site in Lomé or remote
- 4-8
- developers per group, so everyone gets hands-on time
- 60%
- of the time spent writing code, not watching slides
- 1 month
- of follow-up included after the last session
They trusted me
Your challenges
Your team ships, but the code is degrading
- 01
Everyone codes their own way
No shared conventions: code review turns into a debate about taste and nobody arbitrates.
- 02
There are no tests
The team knows there should be, but doesn't know which ones to write or where to start on an existing codebase.
- 03
A new technology arrives
You move to Vue 3, to Docker or to a layered architecture, and the team learns in production.
- 04
The knowledge sits with one person
One developer carries the critical parts alone, and their departure would stop the product.
Programmes
What I train on
Laravel & Symfony
Structuring an application as it grows: layering, dependency injection, queues, efficient queries, tests that actually help.
Vue 3, React & TypeScript
Composition, state management, strict typing, and the design mistakes that cost dearly in maintenance six months later.
Docker, CI/CD & releasing
Moving from a manual, dreaded release to an automated chain the team triggers without stress.
Architecture & quality
Application layering, hexagonal architecture, useful code review, and documenting decisions so choices outlive departures.
How it runs
How a training engagement works
Before · half a day
Scoping
I read your code and talk with the technical lead. The programme is built on what your team actually does, not on a generic syllabus.
During · 2 to 5 days
Sessions
Around 60% hands-on, on your own repositories: we refactor real code, write real tests, fix real problems. Written material handed over at the end.
After · one month
Follow-up
Code reviews and open questions for the following month. That's when habits take hold — or fade away.
What you get
What remains after the last session
Written material
Written from your own examples, reusable for onboarding the next joiners.
Refactored code
Exercises run on your repositories: what is produced during the training ships to production.
Team conventions
Written together and adopted collectively, so code review stops being a debate about taste.
A debrief for management
What the team now masters, what still needs consolidating, and what I recommend for the coming months.
Why work with me
Three commitments I keep on every engagement
- 01
You talk to the person writing the code
No salesperson, no middleman, no junior swapped onto your project after signature. Whoever scopes the work is whoever delivers it.
- 02
You stay the owner
Code, infrastructure, accounts, documentation: everything sits with you. You can change provider without starting over.
- 03
I say no when I should
If an off-the-shelf tool or three days of advice solves your problem better than custom development, I'll tell you — even when it costs me the engagement.
Frequently asked
What people ask before we start
How many participants at most?
Eight. Beyond that the hands-on part loses its point: I can no longer check in with each person during the exercises.
Is the training really run on our code?
Yes, that's the principle. I read your repositories before the session and build the exercises on them. A sample project doesn't produce the same habits.
On site or remote?
Both. On site in Lomé, or remotely in half-day sessions to keep attention up.
What does the month of follow-up cover?
Code reviews on your pull requests and an open channel for questions. It is included, with no hourly billing.
Tell me about your team
Their level, their stack, what is blocking today. I'll answer within 48 hours with a programme and a duration.
Get in touch