From systems to software.

My background is in IT systems, infrastructure, and support. Before I was focused on software development, I was already working with the systems that software depends on: networks, servers, endpoints, cloud services, monitoring, and production environments.

That experience shaped the way I think about technology. I naturally look beyond whether something works and ask what happens when it fails, how it is maintained, and what the people using it actually need.

Working in real IT environments taught me that technical decisions always have consequences. A configuration change can affect an entire customer environment, and a small mistake can become someone else’s problem.

That gave me a practical mindset that I now carry into software development: understand the system, make deliberate changes, and build things that can actually be maintained.

The more I worked with infrastructure, the more interested I became in what was happening behind the systems I was supporting. I wanted to understand how the software itself was designed, not just how to deploy or troubleshoot it.

That eventually led me into software development and HBO Informatica at Avans Hogeschool. Today I spend most of my time working with .NET, C#, TypeScript, React, APIs, databases, and the infrastructure around them.

A large part of my development happens outside the classroom. I build projects to understand technologies properly, test ideas, and solve problems that interest me.

Projects such as OpenCaptive and DentechSync have taught me as much about architecture, deployment, integrations, authentication, observability, and product thinking as they have about writing code.

I am still early in my software career, and I do not want to pretend otherwise. My goal is not to know everything already, but to keep becoming better at turning ideas into reliable software.

I want to become the kind of developer who understands both the code and the environment around it: someone who can build, deploy, troubleshoot, improve, and take responsibility for the systems they create.