About
I've been building Vue.js and Nuxt applications since 2011. Over time, I realized that failing projects rarely lack good developers. They lack clear decisions, owned by the team and built to last. So I learned to do both : build and structure. Not one or the other.
What I do (and what I don't do)
I join teams to build Vue.js and Nuxt applications. I work on building, not bugfix or migration.
And when technical decisions become complex or structural, I bring an experienced perspective to clarify, arbitrate, and document.
What I do:
- Vue.js / Nuxt development in active construction
- Structuring and evolving frontend architectures
- Decision support for high-impact technical choices
- Pragmatic AI integration when relevant
What I don't do:
- Pure bugfix or migration without associated construction
- Project management or operational delivery
- Arbitrary decisions disconnected from real context
Why this approach
I've spent enough time in teams to know that the most costly problems are not always technical.
They are often decision-related:
- unclear choices
- implicit trade-offs
- directions never really assumed
Over time, debt is no longer just technical.
It becomes a decision debt.
That's where I step in.
How I work
I work with teams, not in their place.
I ask questions that are sometimes avoided:
- Why this option?
- Why now?
- What are we willing to sacrifice?
I prioritize:
- clarity over sophistication
- collective understanding over individual complexity
- readable architectures rather than brilliant ones on paper
My goal is not to make the system "perfect".
It is to make it understandable, maintainable, and consciously owned.
About AI
AI is everywhere in technical discussions today.
Very few projects derive real value from it.
I intervene to:
- distinguish opportunity from trend
- frame the risks (costs, dependencies, quality)
- decide if AI is relevant, where it is, and where it isn't
I don't sell promises.
I sell lucidity.
If you're considering working with me
We're probably aligned if:
- You're building a Vue.js or Nuxt application and want a senior dev who thinks long term
- Your frontend architecture is becoming difficult to evolve
- Structural technical decisions need to be clarified or arbitrated
- You want an external, experienced, and independent perspective
If you're looking for someone who builds AND structures, not just one or the other, then the discussion is worth having.
I also organize Vue Montreal, the Vue.js meetup in Montreal, and attend Vue.js international conferences regularly like VueConf US and Vue Amsterdam.
Vue Montreal
Visit website