Waves #2 — The Ship Is Not the Destination
The technology stack is the ship the product is the destination.
Some developers think the technology stack is the destination.
It isn’t.
The sea was almost motionless that evening.
The surface looked calm, broken only by silhouettes of a few sailboats in the distance.
They seemed suspended between sky and water, waiting for a wind that might arrive or not.
For a moment, everything seemed to pause.
No urgency.
No direction.
Ships exist for movement.
They navigate through — shifting winds, unnoticeable currents, changing conditions.
But a ship is never the destination.
It is only a vessel that carries something across the water.
What matters is what reaches the shore.
In software development, technologies often become our ships.
Laravel. React. Vue. Flask. Django.
We learn them.
We invest in them.
We defend them.
Over time, they become familiar.
Comfortable.
Part of our identity.
But they were never meant to be destinations.
They are vessels.
They help us navigate uncertainty: changing requirements, evolving systems, and unknown constraints.
What matters is not the ship we sail.
What matters is what we deliver.
Maybe the mistake is not in the selected technologies.
But forgetting why we chose it in the first place.
Have you ever mistaken the ship for the destination?