In software development, legacy comes with a negative connotation. Legacy software is old. It’s a chore to work with. And to many developers, code doesn’t just age, it rots, requiring regular replacement.

But what if your code has a legacy worth remembering? Like a cryptic easter egg? An end-of-days panic? Or is a cultural touchstone for modern communication?

In today’s Agile world, there’s no point getting sentimental about code. There’s a 50% chance you’ll refactor it within a year. Instead, be sentimental about what it enabled.

You write code to build products. And those products exist to help real people. That’s a legacy you should be proud of!