The person
behind the code.

From small tools to complete products.

I’m a self-taught developer with a deep interest in building applications that make life easier. What started as a personal hobby (experimenting with tools, automating little tasks and creating handy apps in my spare time) steadily became something more serious.

Over the years I built projects in different shapes and sizes, mostly because something felt more complicated than it needed to be. Eventually I realised that many of those tools didn’t only solve my own problems. They could help other people too. That’s where LetMeCodeThat came from.

I also spent years in applied research after a PhD at KU Leuven, translating vague industrial problems into tools people could actually use. That background still shapes how I work: understand the problem, build a usable first version, learn from real use, then improve.

How working together feels.

You don’t need a finished technical specification. You need to be able to explain the problem, the workaround, the idea, or the process that keeps wasting time. I turn that into software decisions, then into working software.

The loop stays direct. You get answers straight from the person writing the code, not through a chain of handoffs where details get lost.