For a long time I thought I worked in technology.
Now I'm not so sure.
I've spent most of my career building cloud platforms, designing data models and trying to make engineering teams a little less dependent on guesswork.
I still enjoy that work.
But somewhere along the way I realised I was not actually interested in technology for its own sake.
I was interested in what it allowed organisations to do.
Technology isn't valuable because it's modern.
It's valuable because it changes the decisions people are able to make.
A data platform isn't the product.
The product is the meeting where people stop arguing about whether the number is right and start deciding what to do about it.
The same is true of almost everything we build.
Observability isn't about dashboards. It's about reducing uncertainty.
Automation isn't about removing manual work. It's about giving people time to think.
Architecture isn't about elegance. It's about making future decisions easier.
I've noticed that the engineers who stay motivated over long careers often make the same transition.
Early on they optimise technology.
Later they optimise organisations.
The technology never stops mattering.
It just stops being the destination.
When I look back at the projects I'm proudest of, I rarely think about the architecture first.
I think about the conversations that changed because the architecture existed.
The stakeholder who finally trusted the numbers.
The engineer who became confident enough to make decisions independently.
The executive who stopped asking whether the data was right and started asking what it meant.
Those are the bits I remember.
Technology was the mechanism.
Not the outcome.
That's why I still enjoy building platforms.
I just don't think platforms are what I've really been building.