As a software developer, “legacy” is usually not a compliment.
Legacy code is the code you inherit. It is the code nobody wants to touch because it is old, fragile, confusing, undocumented, or full of decisions that made sense at the time but are hard to understand years later. In my day job, I try not to create legacy code. I try to build things that are maintainable, understandable, and useful for the people who come after me.
But outside of code, legacy means something very different.
When I work on family history, I am not trying to avoid legacy. I am trying to develop it.
That idea is what led me to create patrickgraham.net, a genealogy and family history site that I am calling Developing Legacy. It is a place for me to collect the stories, records, photos, newspaper clippings, and historical context I have found while researching my own family. Some of these stories are already known within the family. Some were hidden in old records. Some were scattered across newspaper archives, census pages, land documents, and handwritten notes. I wanted a place where those discoveries could become easier to read, easier to share, and easier to preserve.
Why make a separate site for family history?
A family tree is useful, but it is not the whole story.
A tree can tell you that one person was the child of another. It can show dates, places, marriages, and generations. But it does not always explain what someone’s life was like. It does not tell you why they moved, what work they did, what hardship they faced, what risks they took, or what small details made them human.
That is the part of genealogy that keeps pulling me in.
I do not just want a chart of names and dates. I want to understand the people behind them. I want to know what was happening in the world around them. I want to connect the records to the stories. I want my relatives to be able to click a link and see, in plain language, why a discovery matters.
That is hard to do when the information lives in scattered places: genealogy websites, PDF downloads, screenshots, newspaper archive links, notes in a folder, or conversations with family members. So I decided to start building a dedicated home for it.
The irony of “developing legacy”
The name Developing Legacy started as a developer joke, but it stuck because it describes the project better than I expected.
In software, “developing legacy code” sounds like a warning sign. It suggests that today’s decisions may become tomorrow’s maintenance burden.
In family history, developing legacy is the goal.
It means taking fragile pieces of the past and making them more visible. It means turning disconnected facts into stories. It means preserving context before it disappears. It means making sure that people who might otherwise become only a name in a database are remembered as real people with lives, choices, relationships, and stories worth telling.
So yes, when I write code, I try not to create legacy code.
But when I research my family, I am absolutely trying to develop a legacy.
Making research easier to share
One of my biggest motivations for the site is simple: I want to make my research easier to share with family.
When I find an old newspaper article, I can send someone a link, but that link alone often does not explain much. The article might be behind an archive interface. It might have OCR mistakes. It might require context about who is mentioned, how they are related, or why the event matters.
I want patrickgraham.net to give those discoveries a better landing place.
Instead of sending a relative a raw archive link and saying, “Look what I found,” I want to send a page that says:
- Here is the article.
- Here is who it is about.
- Here is how we are connected to that person.
- Here is what was happening in their life at the time.
- Here is why I think this record matters.
That is a much better experience for someone who is curious but not deep in the research with me.
Building tools around the stories
Because I am a developer, I also cannot help thinking about the tools I wish existed around family history storytelling.
I want the site to be more than a collection of static pages. Over time, I would like to build small interactive components that help explain relationships and context. For example, when I write about an ancestor, I would love to show a small React component that visually explains how I am connected to that person.
Something like:
Patrick Graham → parent → grandparent → great-grandparent → ancestor in the story
That kind of relationship path can make a story easier to follow, especially for relatives who may not know exactly where someone fits in the tree.
I can also imagine components that show timelines, maps, family branches, source citations, or clusters of related newspaper articles. Not giant genealogy software. Not a replacement for the major family tree platforms. Just focused tools that make individual stories easier to understand.
The goal is not to turn family history into an app for the sake of building an app. The goal is to use the web to make the research more approachable.
From records to stories
A lot of genealogy research starts with records: birth certificates, death certificates, census pages, military files, land records, court documents, obituaries, and newspaper clippings.
Those records are important, but they are often just fragments. The interesting work is connecting them.
A census record may show where someone lived. A newspaper article may reveal what was happening in that town. A death certificate may name a parent. A land record may explain a move. A family story may fill in the emotional truth that official records never captured.
When those pieces come together, a person starts to come into focus.
That is what I want Developing Legacy to do. I want it to be a place where the fragments become readable stories. I want to preserve the sources, but I also want to explain them. I want the research to be useful to future me, interesting to relatives today, and hopefully meaningful to someone years from now who goes looking for the same people.
A personal project with a long timeline
I do not expect this site to ever be “finished.”
That is part of the appeal.
There will always be another record to find, another story to write, another connection to explain, another branch of the tree to understand. Some posts may be polished narratives. Some may be research notes. Some may be experiments with ways to visualize family connections. Some may simply be a place to preserve an old article before I forget where I found it.
In software terms, maybe this is one project where I am okay with a long tail of maintenance.
Because this kind of legacy is worth maintaining.
What comes next
My next step is to keep building out the site and slowly move more of my research into a format that other people can actually enjoy.
That means writing stories, organizing sources, linking to old newspaper articles, and experimenting with small web components that make family relationships easier to understand. It also means finding the right balance between being accurate, being readable, and not letting perfection prevent me from publishing.
Family history can sit in folders forever if you let it. I would rather share it as I go.
That is what Developing Legacy is about: taking the pieces of the past that I have been lucky enough to find and turning them into something that can be read, shared, and remembered.
In code, legacy is often something you inherit by accident.
In family history, legacy is something you build on purpose.