I am focused on growing as a software engineer at TomTom, especially around backend systems, distributed-system tradeoffs, and how production software changes shape as it scales.
Most of my attention is going into making complex systems easier to reason about: naming the moving parts, tracing the handoffs, and separating what the system produces from how the system behaves while producing it. I am learning that a good problem statement is not paperwork. It is a compression tool.
I am also rebuilding this site around a steadier learning-in-public practice. The shape is simple: short notes while ideas are still rough, reading logs for the technical backbone, and longer essays when something has settled enough to be useful.
Outside work, I am trying to keep the pace quiet and repeatable: work, read, write a little, learn Dutch, and leave enough space for the life around the work. Nothing dramatic. Just careful reps.