Build the Software We Would Want to Use
At Double Helix Software, we believe great software starts with understanding the problem—not with choosing the technology.
That principle has shaped Stemma™ from the beginning.
Genealogy researchers work with enormous amounts of interconnected information: people, families, relationships, dates, places, sources, DNA matches, research questions, historical records, and sometimes family trees containing hundreds of thousands of individuals.
The challenge is not simply storing that information.
The challenge is helping people understand it.
Our approach is to build software that brings those pieces together, reduces unnecessary complexity, and gives researchers better ways to see the relationships hidden within their data.
Solve Real Problems
Many software projects begin with a list of features.
We prefer to begin with a problem.
What is the researcher trying to accomplish?
Where does the existing process become difficult?
What information is already available that the software could use more effectively?
What repetitive work can be eliminated?
What connection might be obvious to a computer but difficult for a person to recognize?
These questions guide the way we design our products.
Stemma™ itself grew from real-world genealogy research. The original idea was not simply to create another family-tree program. It was to bring together the tools researchers were already using separately and allow those tools to work directly with the information contained in the family tree.
That same philosophy continues to guide development today.
Powerful Without Being Complicated
Powerful software often becomes complicated software.
We don’t believe that has to be the case.
Genealogy and genetic genealogy are already complex subjects. Researchers may be analyzing multiple generations, competing relationships, incomplete records, conflicting evidence, DNA inheritance patterns, and thousands of potential family connections.
The software should help manage that complexity—not add to it.
Our goal is to make advanced capabilities available without requiring the user to understand everything happening behind the scenes.
That does not mean removing sophisticated tools.
It means designing those tools so they remain understandable.
A new researcher should be able to begin using the system without being overwhelmed, while an experienced genealogist should still have access to the depth and flexibility required for serious research.
The Family Tree Is More Than a Chart
Traditional genealogy software often treats the family tree primarily as a way to display ancestors and descendants.
We see it differently.
A family tree is a large interconnected dataset.
Every individual may connect to parents, children, spouses, partners, siblings, locations, historical events, records, sources, research notes, DNA inheritance patterns, and other people throughout the tree.
Those relationships contain information.
When software understands those connections, the family tree becomes more than something to display.
It becomes something that can be analyzed.
That idea is fundamental to Stemma™.
Rather than treating specialized genealogy tools as separate applications, we design them to work directly with the family tree whenever possible.
The researcher should not have to repeatedly move information from one tool to another when the information already exists.
Let the Data Work Together
Genealogy research often takes place across many disconnected systems.
A researcher may maintain a family tree in one program, analyze DNA results with another tool, keep notes somewhere else, search historical databases online, and use spreadsheets or external utilities for specialized research.
Each tool may be useful individually.
The problem is that the information frequently cannot work together.
Double Helix Software focuses on integration.
When information is already present in the research environment, our goal is to allow other tools to make use of it.
A relationship recorded in the family tree should be available to relationship-analysis tools.
Gender and ancestry information can help identify possible DNA inheritance paths.
Dates and locations can help identify inconsistencies.
Repeated ancestors can reveal pedigree collapse or endogamy.
Large datasets can expose patterns that would be difficult or impossible to identify manually.
The more effectively the information works together, the more useful the entire research environment becomes.
Visualize the Connections
Some information is easier to understand when you can see it.
Genealogy is particularly well suited to visualization because relationships themselves are part of the information.
A researcher may understand that two people are related but still struggle to visualize exactly how those relationships intersect across multiple generations.
Color, grouping, relationship paths, DNA inheritance lines, tree layouts, and other visual tools can turn complicated genealogical structures into something immediately understandable.
We consider visualization an analytical tool—not merely decoration.
When appropriate, Stemma™ uses the structure of the family tree itself to help researchers recognize patterns, identify relationships, and discover areas that deserve further investigation.
Designed Around the Researcher
Software developers naturally think about databases, APIs, algorithms, servers, and architecture.
Users generally don’t.
They think about what they are trying to accomplish.
That distinction matters.
We try to design features around the researcher’s workflow rather than exposing the internal structure of the software.
A task that requires several complicated operations internally should not necessarily require several complicated steps from the user.
Whenever possible, the complexity belongs inside the software.
The interface should concentrate on the research.
Listen, Learn, Improve
Software rarely becomes great because someone designed everything perfectly the first time.
It improves because people use it.
Real users encounter situations developers never anticipated. They work with unusually large trees, unusual family structures, incomplete historical records, unusual DNA relationships, and research methodologies that expose both opportunities and weaknesses in the software.
We consider that feedback an important part of development.
When researchers tell us that something is difficult, confusing, missing, or could work better, we want to understand why.
Sometimes the answer is a small interface change.
Sometimes it becomes an entirely new capability.
The goal is not simply to add more features.
The goal is to make the software more useful.
Build for Serious Data
Family-history research can represent years or even decades of work.
For some researchers, the information contained in their tree may represent work gathered across multiple generations of their family.
That deserves to be treated seriously.
Our development decisions emphasize data integrity, reliability, maintainability, and the ability to work with large amounts of genealogical information.
We also recognize that genealogy does not always fit neatly into simple structures.
Families are complicated.
Records are incomplete.
Names change.
Relationships vary.
Dates may be uncertain.
Historical terminology differs from modern terminology.
Good genealogy software must be able to represent that complexity rather than forcing every family into an artificial ideal.
Technology Should Enable Research
We use technology because of what it allows the researcher to accomplish.
Not because the technology itself is fashionable.
New technologies can create tremendous opportunities, but they are useful only when they solve a real problem.
Our goal is to apply software architecture, data analysis, visualization, automation, and other technologies where they genuinely improve genealogy research.
Sometimes the best solution is sophisticated.
Sometimes it is remarkably simple.
The important question is whether it helps.
Build for Today. Design for Tomorrow.
Stemma continues to evolve.
Genealogy research methods will change.
DNA databases and analysis techniques will change.
New historical resources will become available.
Researchers will discover new questions they want their software to answer.
We therefore design with the expectation that the system will continue growing.
That means thinking beyond the feature being developed today and considering how it may connect with the capabilities that come tomorrow.
A strong platform should not simply solve today’s problems.
It should provide a foundation for solving problems we have not encountered yet.
Software Built Around Connections
The name Double Helix Software reflects an important part of what we do, but DNA is only one kind of connection.
People connect to families.
Families connect across generations.
Individuals connect to places and historical events.
Records connect evidence to people.
DNA connects relatives who may never have known each other existed.
And software can connect all of that information in ways that make those relationships easier to understand.
That is the kind of software we want to build.
Understand the problem. Connect the information. Give people better tools to discover the answer.