My Why, My How, My What

This note is a provisional snapshot of what sets me in motion, how I like to work, and the concrete forms I care about without wanting to become too rigidly attached to them.

My Why#

My main drive is to be useful.

I need what I build to genuinely make life easier for concrete people. I do not simply want to produce an object, a piece of software, or a company: I want what I do to answer a real problem, improve a situation, clarify a use case, remove friction, or make someone’s daily life simpler.

This why is also tied to learning. I need my work to feed my curiosity, to help me understand systems, professions, use cases, constraints, and to help me grow intellectually. For me, working is not only about executing: it is also about learning to see reality more clearly.

There is also a strong moral and human dimension. I want to build something that remains aligned with my values: respect for people, fairness in the sharing of value, and the creation of a framework that respects the intention, energy, and dignity of those who contribute to it.

Economic success is necessary, but it is not an isolated end in itself. It is what allows the project to last. The deeper objective is to create a viable structure that allows these values to take shape in reality.

My How#

My way of working relies on a structured, concrete approach that pays close attention to systems.

I like to start from reality: the use cases, the people concerned, the material constraints, the available data, the blockers, and the effects produced. Before looking for a solution, I need to understand the problem in its context.

I work better through learning and dialogue. I need to test my ideas against the field, to exchange with others, to clarify things progressively, and to reveal the right structure of the problem before building the answer.

My how could be summarized like this: understand the real system around a problem, structure what we observe, then progressively build a useful solution with the people concerned.

My What#

I am drawn to subjects where software can make a concrete use case simpler, more robust, or more human.

Some territories particularly resonate with me: software engineering, sport, professional tools, and systems that help concrete people work better or live a practice more fully.

But I am not attached to one single product. The what can change. It may take the form of a tool for restaurant owners, an app for athletes, a platform for engineers, or something else entirely.

What matters is that the what remains in service of the why: being useful, learning, building with care, and creating a viable structure that respects people.

In summary#

The what gives the project a visible form. The how gives it a way of working. But the why is what allows us to remain faithful to ourselves when the form changes.

I want to build useful things that are economically viable, respectful of people, and strong enough to last without betraying what brought them into being.