Nine years in, and I still think the most interesting problems live at the intersection of a sharp product idea and an infrastructure that wasn't quite built for it. I've worked across that gap long enough to know which battles are worth having with a data model, and when to just fix the schema.

My background started in Creative Media & Game Technology at Rotterdam University of Applied Sciences, which meant learning to think about the person holding the screen before thinking about the code behind it. That instinct stuck. It's why I care about the 200ms that separates a dashboard that feels alive from one that feels sluggish, not just whether it technically works.

Some of the work I'm most proud of has no margin for error baked into the brief. Live dashboards for major cultural events, real-time data systems for large international clients, infrastructure that had to hold up under genuine load with genuine consequences. The through-line isn't the industry or the client size, it's that the stakes were real, and the systems had to be too.