I approach each project with a simple conviction: a good developer doesn't just write code, they understand the business they serve.

15 years of experience have taught me that half the work happens before the keyboard, in understanding the need and framing the solution. The rest is execution discipline.

Framing before code: Before writing a single line, I make sure I've understood the business problem, identified the real users, and made the structural technical choices. This phase saves my clients from funding features that serve no purpose.

Iterative delivery: I break projects into short milestones to provide visibility, adjust along the way, and validate choices step by step rather than delivering everything at the end.

Maintainable code: My clients are not locked in: I document, I test, and I leave behind code another developer can pick up. No magic, no hidden technical debt.

I use AI heavily in both design and development, with the mindset of a tech lead managing a team of juniors. I frame the need, I review, I make the architectural calls. That means faster delivery without compromising on maintainability, because in the end, I'm the one accountable for the result, not the machine.

Self-taught at first, I later trained at an engineering school in Limoges (3iL). I've been based in Toulouse since 2011, working either remotely or on-site depending on the need.

When I'm not coding, I teach (~1,500 hours delivered in higher education since 2019), and I'm an active member of AFUP Toulouse, the local PHP developer community.