Dr. Neil's Notes
Software > Development > Being Early
The Cost of Being Right Too Soon
Introduction
There is a particular kind of frustration that comes from being right about something the world is not yet ready to hear. It is not the frustration of being wrong. Wrong is easy to understand and easy to fix. Being right too soon is stranger. You can see the destination clearly. You can explain why it matters. You can build the thing. Then you wait, sometimes for years, while the world catches up.
This has happened to me more than once. The experience taught me more about technology, timing, and people than any success ever did.
The Pattern
Looking back across nearly forty years of building software, a pattern repeats. A technology appears that is genuinely useful, clearly pointing in a direction the world will eventually go. A small group of people see it, understand it, and start building around it. The world shrugs.
Then, years later, sometimes a decade or more later, the world suddenly decides this was always a good idea. The timing is rarely about the idea itself. It is about the infrastructure, the trust, the ecosystem, and the willingness of people to change behaviour.
Being early is not the same as being wrong. It feels similar, especially in the short term, but the distinction matters enormously.
What Early Costs
Being early is expensive. The cost is not always financial, though it often is. It is the cost of explaining yourself to people who cannot see what you see. It is the cost of building products for markets that do not yet exist. It is the cost of maintaining conviction when the evidence around you is ambiguous or actively discouraging.
There is also a subtler cost: opportunity. While you are ahead of the curve on one thing, you are not working on something the world is already ready for. The choice to be early is also, often without realising it, a choice to forego the easier path.
None of this means being early is a mistake. Some of the most important work I have ever done was work where the timing was off. The ideas survived, adapted, and eventually arrived at the right moment. But it is worth being honest about what early costs, so that when it happens, you can make the choice with clarity.
The Upside
For all its costs, being early carries real advantages. The people who work on a problem when it is still difficult and undefined learn things that no amount of later study can replicate. When the world does catch up, those people carry knowledge and intuition that cannot be quickly acquired. They have made the mistakes already. They know where the edges are.
The early work also shapes the eventual outcome. The ideas, architectures, and approaches developed in that early period tend to persist, often more than the original builders realise. The platforms, patterns, and products that define a technology's maturity almost always have roots in work done years before the mainstream noticed.
Being early, at its best, is not a penalty. It is a form of investment with a long and uncertain payoff.
Part of the Being Early series.