About
How I work
A pragmatic approach: understand the need, choose the simplest solution that will last, then verify it.
01 / Approach
Overview
My guiding principle is simple: delivering useful software is not enough; it also needs to remain understandable and adaptable. I focus on clarifying the need, breaking problems down, making technical decisions explicit and writing code a team can review, test and evolve.
My experience spans different challenges: checkout experience and conversion in e-commerce, data centralisation in business applications, and event-driven processing in demanding industrial environments. These contexts taught me to fit the solution to the problem instead of forcing a technology into it.
I prioritise reliability, readability and tangible value for users. Tests, code reviews, API contracts and separation of concerns are not finishing touches; they are part of the design.
02 / About
My work values
Reliable software starts with clear decisions, small iterations and validation before delivery.
Reliability
What ships has to run unattended: I would rather ship a simple, verified solution than an elegant, fragile one.
Code quality
Code is read and picked up far more often than it is written: readability, naming and tests are part of the delivery.
Useful products
The goal is not a technical showcase but the time the tool saves the people who use it.
Next step
Have a project in mind?
Let’s discuss the context, constraints and expected outcome.