Once upon a time, I was sitting in a physical chemistry class when an organic chemistry professor from down the hall gave us a passionate talk about research. He spoke with real conviction—about the thrill of discovery, the value of joining a lab, the energy of contributing something new to the field.
And I remember thinking: nah.
It wasn’t cynicism… maybe a little cynicism, but I did admire his passion. Something in me just didn’t respond to the idea of chasing the next breakthrough. What I wanted instead was to explore the vast world of the known—because most of science was still very much unknown to me.
That realization hit me hardest while walking through the science library at the same university. Wandering those rows of shelves felt like going on a strange treasure hunt—or maybe like finding map after map to not-yet-fully-realized insights. I remember picking up a book on molecular structures of sugars and being completely absorbed—there were so many different forms, each mapped and named and classified. That was just one tiny sliver of one corner of chemistry.
Everywhere I looked, there were papers, books, and journals filled with painstaking, brilliant work—some of it generations old—largely untouched. Not because it had failed. But because no one had picked it up again. It struck me that the history of science is full of shifts like this—where major insights get buried under new trends until someone comes along and sees them differently or connects one discovery to another. Maybe they see the potential in a decade-old finding that was just waiting for someone to pick it up again.
Take galaxies, for example. Before Edwin Hubble—the man, not the telescope—we didn’t even know they existed. The Milky Way was the entire universe. There were blurry lights in the sky on the edge of what we could see, yet we didn’t understand what they were. The data was sitting there. The telescopes were improving. But it took a shift in perspective to see it.
That shift was only possible because of the earlier work of Henrietta Swan Leavitt, who discovered a way to measure distances using the brightness patterns of certain stars—Cepheid variables. Hubble applied her method to those distant smudges of light and proved they were whole systems of stars, significantly farther away than we ever imagined. And suddenly, our understanding of the universe—and our place in it—shifted.
All of that—the discovery, the reinterpretation, the change in worldview—was built on stacks. Stacks of observations. Carefully examined and cataloged photographic plates, where each change in a star was meticulously noted. That was the untapped research that led to Hubble’s stunning insights and a whole generation of discovery.
It made me wonder: how many insights have we walked past, simply because they weren’t new?
Oddly enough, that’s how I often feel about software.
There’s a romanticism in tech around greenfield projects—around shipping something new, around chasing the latest framework or over-hyped trend. But I often find myself most drawn to the opposite: the deeply layered, heavily used, frequently misunderstood systems that have been working quietly, and sometimes not so quietly, for years.
No, I’m not itching to dive into the COBOL setup from forty years ago. But I do believe there’s enormous untapped value, insight, and room for innovation in simply learning about the stacks that already exist.
There’s context hidden in the logic. There’s insight buried in the odd decisions—sometimes dated, sometimes brilliant, sometimes both. There’s an opportunity not just to clean up, but to understand. To make the system more maintainable, more flexible, more powerful. To see how a setup can enhance the capabilities of the existing stack—or how a thoughtful refactor can make the entire system significantly more robust. But first, there’s a great deal to learn, to wrap our minds around, to discover.
We talk a lot about technical debt. But we don’t talk enough about unclaimed inheritance—the parts of a system that were carefully built, mostly forgotten, and never truly integrated into our modern workflows. What if supporting legacy code didn’t carry the connotation of eating a celery stick or keeping up with your chores? What if it were a chance to discover the thought processes, the understanding, the context, and the innovative thinking that still power your new features every day?
Every codebase has a history, just like every scientific field. And understanding that history makes you a better engineer—not just more effective, but more insightful. You see the whole system differently. You make better choices because you understand not just what’s broken, but what the ambitions were—what worked, what didn’t, and why.
Treasure doesn’t always look like gold—or blockchain. Sometimes it looks like a dusty book on the top shelf of the science library. Or a half-documented class in a shared module. Or a system no one wants to touch because no one really understands it.
There’s treasure in the stack(s). 😉