Time is one of the greatest challenges in the world of IT. Unlike other engineering disciplines, what we build in tech often has a short lifespan and demands constant change to retain its value. Most of the projects we work on are short-lived and for many, their only path to survival is a complete rebuild.
But not everything in tech has to be temporary. With thoughtful design, regular maintenance, and continuous refactoring, important systems can last decades.
In our industry, “legacy” is often seen as a dirty word—synonymous with outdated or poorly written code. However building a legacy should be one of our highest aspirations as engineers. Crafting systems, codebases, and even teams that outlast us is one of the most meaningful artifacts we can leave behind.
Drupal is a great example. There are websites built on Drupal that have been running for decades. While time may have eroded its shine, its solid foundations have allowed them to evolve and remain relevant almost 25 years after Drupal’s creation.
In this talk, we’ll explore the principles, patterns, and personal anecdotes that can help you build software designed to last. We'll look at how to create systems that are not only long-lived, but also prepared to evolve—just as Drupal has done since 2001.