Understand the real problem
Start with users, constraints, and outcomes. Architecture should serve the problem—not become one.
About me
I’m a software engineer who enjoys finding the calm, clear structure inside a complicated problem—and helping teams build from it.
Currently
Building cloud-native platforms and dependable backend systems in Amsterdam.
My approach
I’ve spent more than fourteen years designing and delivering software, with a focus on .NET applications, distributed systems, APIs, and cloud infrastructure. I like the work where product goals and technical constraints need to be translated into something a team can confidently ship.
My best work is collaborative. I ask questions early, make trade-offs visible, and aim for solutions that are resilient without becoming needlessly clever. Maintainability is a product feature—not a clean-up task for later.
Principles
Start with users, constraints, and outcomes. Architecture should serve the problem—not become one.
Use clear boundaries and simple contracts so a system can evolve without a rewrite every season.
Logs, metrics, traces, failure modes, and deployment paths belong in the design from day one.
Strong teams make reasoning visible through focused documentation, honest reviews, and conversation.
Say hello