For the love of continuity

We love disruption. It has real power, and it is good for competition and for growth. But disruption has a balancing partner that gets far less attention, and I think it is the more interesting one to study: continuity.

Continuity is not just preserving the good parts while you swap out the poor ones. It is anticipating the shapes reality might take tomorrow, and weaving a fabric today that is elastic enough to wrap around those shapes when they arrive.

That fabric is where all of us, people, teams, and organizations, attach our time and our effort. We connect systems, we learn and master skills, we become professionals and then we teach, we make plans. Continuity is what makes any of that worth doing. How do you study, invest, or build for tomorrow if you have no idea what tomorrow looks like?

Ruby on Rails is continuity made visible. The framework that is performant, scalable, and developer-centric today could not have been designed in a day or a year. It had to move through cycle after cycle of hype, frustration, and disruption, with group after group discovering better solutions, all while the fabric held: the conventions, the primitives, the things you could still rely on.

In 2026, that fabric feels fragile. The obvious reason is AI. And the most useful question to ask about anything you build right now is not only what it will disrupt, but what it will help continue, and what can keep going after it.

For me, the answer is three things: organizations, communities, and open source. Each one is a kind of fabric, and each is being tested right now. So I am going to take them one at a time, one letter each, starting with the next one.

Hop on, my developer friends.