The reason I created this blog

There’s a particular frustration that arrives when you’ve built something that works perfectly and nobody uses it.

I’ve felt it three or four times now, shipping a feature with clean architecture, solid test coverage, and a deploy that went off without a hitch, only to watch analytics show near-zero engagement. The code was fine. The thing was wrong.

That gap, between what engineers optimize for and what people actually need, is where design lives. And I’ve come to think it’s the more interesting problem.

What shifted

I started keeping notes on every time I saw a technically correct solution that felt wrong in use. After a year I had two dozen examples. They all had the same shape: someone (often me) had solved a problem without asking whether it was the right problem to solve.

Design isn’t just aesthetics. At its core it’s a discipline for asking better questions before writing a single line of code, or a single pixel.

What I’m building toward

I’m applying to Master’s programs in HCI and cognitive science in France. The language gap is real, I’m learning French in parallel, but the intellectual direction feels right. The intersection of cognition, systems, and how people make sense of things is where I want to spend the next decade.

This site is part of the process: a place to think in public, document the work, and show (not just tell) that the shift is genuine.