Six years without blogging. It was time to return.

The last time I published an article here was in 2020. In computing terms, that feels like another era.

I never really decided to stop blogging. Day-to-day work simply took up more and more room, topics piled up somewhere in the back of my mind, and drafts never made it past the draft stage. Still, I missed writing.

This blog has always helped me put things into perspective. Taking a problem I encountered during the day, understanding what happened and then trying to explain it simply is often the best way to check that I truly understood it.

So, here I am again 🙂

Six very busy years

Since my last article, I have been fortunate enough to do many things — and to work at a very different scale.

For six years, I served as Technical Director at Ketchapp (Ubisoft). My scope covered the construction and evolution of both the company’s technical organisation and its technology infrastructure.

I designed the entire technology stack and developed a suite of internal software and platforms: Monetchapp, Marketchapp, Portal, MayoSDK and Pivotchapp. Each one addressed a concrete Ketchapp need and, together, they gradually became an important part of its technical ecosystem.

What makes me particularly proud is that these tools eventually went beyond their original context. Initially designed for Ketchapp, they were later shared and made available across Ubisoft. Seeing solutions created for one team’s problems become useful to a much larger organisation remains a rather special experience.

Building the technology — and the teams

Technology was only part of the work.

I built and structured the SDK, Web, Data Engineering and Quality Control teams. This meant defining their responsibilities, working methods and the way they collaborated with the rest of the company.

I also recruited around ten people and managed an international team split between France and Ukraine. That forces you to grow far beyond code: organisation, communication, coordination, trust and the ability to keep everyone aligned despite the distance.

Over those six years, I had the opportunity to work across the entire lifecycle of building a technical organisation: architecture, stack development, team creation, recruitment, management and organisational growth.

That period alone has already given me quite a few articles to write.

Meanwhile, our profession changed

Software development in 2026 is not quite the same as it was in 2020. .NET continued to evolve, cloud computing and automation became even more prominent, and artificial intelligence entered our daily work at an impressive speed.

I use it, experiment with it and still have many questions. What it genuinely accelerates, what it makes more complicated, and how it changes the way we learn, design and review code: there is a great deal to explore beyond spectacular demos and marketing promises.

That is probably another reason why I want to return to this blog now. I need a place to step back, document what I try and share what actually works.

Picking up the thread

I am not going to promise one article every week. I know how that kind of promise ends.

I will simply try to share more of my day-to-day work: .NET and C#, architecture, AI, tools, team challenges, decisions that worked well — and probably a few failed experiments, because those are often the most interesting ones.

After six years of silence, many things have changed. But the desire to understand, build and share is still here.

The blog is back. And I missed it.