Connections
For a long time, I thought my job was building websites.
Then I realized that, in most cases, the website was only one of the destinations.
The interesting part was everything that happened before.
A spreadsheet maintained by the people who know the products.
An image library.
A plugin that synchronizes data.
A QR code attached to a sample.
A page that updates automatically.
An informational popup.
A PDF.
A map.
Each element has a specific role.
None of them tries to do everything.
My work is almost always about building connections between these tools while allowing each of them to keep doing what it does best.
That’s why I often rely on very simple technologies.
CSV files.
APIs.
QR codes.
Shared files.
Not because they’re the newest.
Because they provide a common language that different systems can all understand.
Over time, I realized that innovation doesn’t necessarily come from adding new tools.
More often, it comes from allowing existing ones to work together.
That’s probably why I still think of systems as orchestras.
Every instrument has its own voice.
Music begins when they start listening to one another.
Bridges are often more important than the tools they connect.