01 / Technology
Technology is most interesting when it changes what people can do.
I spend a lot of time at the intersection of software engineering, architecture, data, cloud and AI. I like understanding the system as a whole, but I also like diving into the details when something is worth understanding.
The questions I find interesting are rarely just technical. How do you move from an idea to something that actually works? How do you modernize without losing what already works? How do you introduce new technology without turning it into another layer of complexity?
The helicopter view
I naturally start with the helicopter view. I want to see the landscape, dependencies, direction and forces that shape the system. Then, when something catches my attention, I dive in.
For me, architecture is not about drawing boxes. It is about understanding how the boxes, people, data and decisions interact.
Technology adoption
Adopting a technology is usually easier than adopting a new way of working.
The interesting part of technology transformation is therefore not only the technology. It is the interaction between architecture, people, skills, habits, incentives and leadership.
AI in the engineering cockpit
What happens when your engineering team gets a team of agents?
I am interested in what happens when AI agents become part of the engineering team — not as a replacement for engineers, but as a new kind of collaborator: exploring codebases, proposing solutions, writing code, testing ideas and accelerating the path from question to working software.
The interesting question is not “Can AI write code?” It clearly can. The interesting question is: “How should we design the way humans and agents work together?”