Skip to content
Published on

Three Thousand Kilometers: What the Monarch Butterfly Teaches Developers About Legacy

🇰🇷KO🇺🇸EN🇯🇵JA
Split View
Authors

Remembering a Place You've Never Been

Every autumn, hundreds of millions of Monarch butterflies (Danaus plexippus) begin flying south from Canada and the northern United States. Their destination is a specific stand of Oyamel fir trees in Michoacán, Mexico — approximately 4,500 kilometers away.

The distance is not the astonishing part. The astonishing part is this: not a single one of these butterflies has ever been there before.

The monarch lives four to six weeks. But butterflies born in late summer enter a special biological state called diapause — reproductive arrest, combined with intensive fat accumulation — and live eight to nine months instead. This "super generation" completes the autumn migration to Mexico. In spring, they begin flying north again, laying eggs along the way before dying. Their offspring continue north. A third generation. A fourth. By autumn, this fourth generation finds its way back to the same Oyamel forest in Mexico that their great-great-grandparents left.

A place they have never been. A place their great-great-grandmothers once departed from.

How They Know: The Science of Inherited Navigation

Lincoln Brower spent his career from the 1960s until his death in 2014 documenting monarch migration. He established that this is not simple instinct but a sophisticated navigational system.

The Reppert Lab at the University of Massachusetts revealed that monarchs use two compasses simultaneously. The first is a sun compass — monarchs compute direction from the sun's position integrated with the time of day. Remarkably, this sun compass is coupled to a circadian biological clock located in the antennae themselves.

The second is magnetic navigation. A 2021 study found magnetic receptors in monarch antennae, confirming that Earth's magnetic field serves as an additional navigational reference.

But these two mechanisms still don't fully explain how a butterfly navigates to a specific forest on a specific mountain range it has never seen. There is something else — something science has not yet fully characterized. Knowledge transmitted across generations in ways we do not yet understand.

Michael Polanyi: We Know More Than We Can Tell

The Hungarian-British philosopher Michael Polanyi wrote in his 1958 Personal Knowledge: "We can know more than we can tell."

He called this tacit knowledge — the kind of knowing that resists explicit articulation. How to ride a bicycle. How to recognize a face. The intuition of an experienced physician who senses something is wrong before any diagnostic test confirms it. These are genuine forms of knowledge, but they cannot be fully verbalized.

The monarch's navigational knowledge is tacit knowledge at its most extreme. It is encoded in DNA, in neural architecture, in systems we don't yet understand. The butterfly cannot explain what it knows. But it flies 4,500 kilometers to exactly the right forest.

Developers carry tacit knowledge too. Why this architecture will cause problems in three years. Why this API design will confuse users even though it looks reasonable on paper. Why this PR, technically correct, will become technical debt. These intuitions came from somewhere — from the code written by developers before you, from the architectures that succeeded and failed before you arrived, from the accumulated experience of a community you are part of.

Mariposas Monarca: The Souls That Return

In Spanish, the monarch butterfly is the mariposa monarca. For indigenous communities near the Oyamel forests of Michoacán, these butterflies have long been considered sacred. Traditional belief holds that the souls of the dead return in early November — during Día de los Muertos, the Day of the Dead — in the form of monarch butterflies.

"El viaje es la recompensa" — the journey is the reward. This Spanish expression, connected to the cultural significance of the monarch migration, captures something true: it is not only the destination that matters, but the journey itself. The spectacle of hundreds of millions of butterflies coloring the sky is itself a purpose, not merely a means to an end.

In Japanese, 渡り鳥 (wataridori) means migratory bird — but the word carries a cultural weight that reflects the deep Japanese appreciation for seasonal journeys. The bird that leaves in autumn and returns in spring; the migration as a living expression of time's rhythm. This same appreciation for cyclic movement, for the beauty of returning, extends to the monarch butterfly and its remarkable journey.

You Are a Butterfly: The Multigenerational Codebase

Now the most important connection.

Think about the codebase you work in. Someone who came before you started it. Some architectural decisions have reasons that are now obscure. Some variable names are perfectly apt if you know the context and baffling if you don't. Some legacy code looks strange today but was the right choice given constraints that no longer exist and have not been documented.

You are flying a migration path that earlier generations of butterflies established.

And someone will come after you. They will see your code. Your decisions, your solutions, your bugs, your comments — all of it becomes part of the navigational system for the next generation of developers working in your codebase.

You may be working on a project you will never see completed. That is not a tragedy. It is the nature of all meaningful work. The cathedral builders of medieval Europe knew they would not live to see the spires finished. The mathematicians who established the foundations of computer science never saw the internet. What they built became the migration path for those who came later.

The Super Generation: Choosing to Carry More

Monarch super-generation butterflies don't just live longer. They live differently. Reproductive drive is suppressed. Fat reserves are prioritized. Their biology reorganizes around the mission of distance.

Developer communities have their own super generations. The maintainers who steward open-source libraries that millions depend on. The people who write technical blog posts explaining what they just spent three months learning. The conference speakers who crystallize community knowledge into transmissible form. The mentors who invest deliberate time in someone else's growth. These people are not optimizing for personal productivity — they are carrying the migration path forward for everyone who comes next.

Becoming part of this is not a sacrifice. It is a different kind of reward.

Five Practices for Building Multigenerational Developer Knowledge

1. Record why, not just what (Architecture Decision Records)

The most valuable documentation is the documentation of reasoning, not implementation. Architecture Decision Records (ADRs) are a practice of leaving letters to your future colleagues: "We chose Y over X because, at the time, we faced constraint Z." One such record can save a future developer hours of archaeology — and prevent a well-meaning future refactor from destroying a decision that solved a real problem.

2. Write code as letters to the future

When you comment, explain intention — not mechanics. When you name a variable or function, think about the developer who will read it without you present to explain. Good code is good communication across time. The reader is real. Write to them.

3. Contribute to open source as legacy-building

Every open-source contribution is participation in a multigenerational migration. A bug fix, a documentation improvement, a new test case — these accumulate into ecosystems. You are contributing to something you will not complete. That is not a reason to withhold contribution; it is the very definition of what open source is.

4. Convert tacit knowledge to explicit knowledge

The things senior developers describe as "just feeling right" — code smell, architectural smell, the intuition that a performance issue is ahead — practice explaining these. Write them down imperfectly. Share them incompletely. The attempt to articulate tacit knowledge is itself the practice that makes it more shareable. Polanyi knew that tacit knowledge could never be fully explicit. But it can be more explicit than it currently is.

5. Treat onboarding as migration-path maintenance

A new team member arriving is a new butterfly joining the migration. Help them find the path. Documentation, pair programming, code tours, architecture walkthroughs — these investments build the navigational system that every future developer will rely on. Good onboarding is not just kindness. It is the mechanism by which institutional knowledge propagates across generations.

What the Butterfly Teaches

The monarch butterfly cannot explain where it is going or why. But it flies 4,500 kilometers to exactly the right forest, navigating by the sun and the earth's magnetic field, guided by something encoded in its very being by generations of butterflies it never met.

We developers carry the same kind of knowledge. Intuitions about what will age well, what will break under pressure, what will confuse the users who come later — these intuitions come from the developers who came before us. From code they left. From posts they wrote. From talks they gave. From systems they built that we now maintain.

We are somewhere in the middle of a multigenerational journey. The butterflies before us made the path. The butterflies after us will extend it.

The code you write today, the knowledge you share, the documentation you leave — these become someone else's compass.

Fly.

References

  • Brower, L. P. (1996). Monarch butterfly orientation: missing pieces of a magnificent puzzle. Journal of Experimental Biology, 199(1), 93–103.
  • Reppert, S. M., Gegear, R. J., & Merlin, C. (2010). Navigational mechanisms of migrating monarch butterflies. Trends in Neurosciences, 33(9), 399–406.
  • Guerra, P. A., Gegear, R. J., & Reppert, S. M. (2014). A magnetic compass aids monarch butterfly migration. Nature Communications, 5, 4164.
  • Polanyi, M. (1958). Personal Knowledge: Towards a Post-Critical Philosophy. University of Chicago Press.
  • Humble, J., & Farley, D. (2010). Continuous Delivery. Addison-Wesley.
Discuss on Twitter • View on GitHub