The Summer of My Genealogical Discontent, Lesson 4 – Confidence

AI Image

This is a continuing in my series on mistakes I made as a beginning genealogist. If you missed the earlier lessons, you can read about my trust issues with online trees, family lore, and source saving habits here, here, and here.

Let’s talk about confidence—or more accurately, the lack of it.

My first family tree was on paper. In 1983, my husband bought a TI-84 computer and a family tree cartridge. It allowed basic data entry but had one glaring flaw: no printer. And with no real internet access at the time, there was no way to share the tree beyond showing someone the screen.

By 1995, I’d discovered FamilySearch.org and quickly entered my 50 or so known family members into their online tree. Then came RootsWeb, and I uploaded my FamilySearch .paf file there. The tech was improving—and so were my skills—but confidence? That was still lagging behind.

I loved experimenting with new tools, but reliable records online were scarce, local training was hit-or-miss, and no one was talking about things like the Genealogical Proof Standard. Source citations? Not really a thing yet. DNA testing for genealogy didn’t exist. And AI—well, that sounded like science fiction.

In hindsight, I’m grateful the tools rolled out gradually. It allowed my learning to grow alongside the technology, making the whole experience feel manageable, even exciting.

Still, I was the new kid on the block. At local library presentations, I was often the youngest person in the room.

I wish I could say the older attendees embraced my enthusiasm, but… not so much. I was mostly ignored, and at times, subtly reminded that I lacked their decades of experience—which, let’s be honest, wasn’t inaccurate.

By the early 2000s, Ancestry.com had entered the scene, and I converted my old .paf file into a .gedcom and uploaded it. And almost immediately, I ran into resistance.

A DAR woman messaged me—clipped, curt, and in all caps—insisting I had made an error and must correct it IMMEDIATELY.

Embarrassed, I complied. I removed the ancestor in question and replied that my tree had been “corrected.”

But about a year later, I revisited that line after new records came online—probate records, in fact. And guess what? My original hunch had been right. So I added the ancestor back.

Not long after, the same woman messaged again, demanding I remove the name. This time, I had proof—and I told her so.

No response. Until a year later, when she messaged me once more, threatening to report me to Ancestry for ignoring her third “polite request.”

This time, I stood my ground. I reminded her that I had previously provided documentation and warned that if she contacted me again, I would be reporting her for harassment.

She didn’t write back.

Now, I’m no longer the youngest in the room. I’m one of the “old genealogists”—and I try hard not to repeat the mistakes made by those who once made me feel small. That’s part of why I’ve written this series: to let beginners know that we’ve all been there.

No one gets everything right. Not at the beginning, not even later. But we get better. We grow through doing, through missteps, through asking questions, and through helping each other.

Confidence in genealogy doesn’t come from having all the answers—it comes from being willing to keep learning. And I hope I never stop.

The Summer of My Discontent: How I Survived My Genealogy Growing Pains…and What I Wish I’d Known Sooner

AI Image

The Summer of My Discontent, Lesson 1: Trust, But Verify

Every genealogist has a learning curve. Mine just happened to feel like a full-blown heatwave. And since we’re in the middle of one right now, I thought it was the perfect time to reflect on my early genealogy practices—many of which were, well, a little light on rigor.

In those early days, I stumbled (frequently), chased the wrong ancestors, trusted shaky online trees, and fell for records that weren’t what they seemed. I call this season of trial and error The Summer of My Discontent—a nod to my distant cousin Shakespeare and my own scorching missteps.

This series is an honest look back at the mistakes that taught me the most. I’ll share the traps I fell into, how I dug myself out, and, most importantly, how you can avoid getting burned on your own journey. Whether you’re just starting or already a little singed, I hope you’ll find humor, relief, and a few practical takeaways here.

Let’s turn discontent into discovery.


Lesson One: Don’t Trust, Verify

One of my earliest mistakes? Trusting other people’s research without verifying it.

That’s a bold statement, I know. Does that mean we should never trust anyone’s work? Absolutely not. But we should check it out—verify the source, analyze the findings, and make sure the evidence stands up. Only then can we safely incorporate it.

Back then, I assumed everyone else knew more than I did—so they had to be right. Spoiler: they weren’t. That realization hit me around 2:00 a.m. one Saturday morning in 1996 after I’d wasted eight hours chasing someone else’s fantasy line. Lesson learned.

I had just taken my first genealogy class in 1995, held at the local LDS church and led by a familiar face—our neighborhood pizza shop owner from Third Base Pizza (because after third base, you’re home). No, I’m not making that up.

Online research was in its infancy (remember those AOL CD giveaways at Kmart?), and the course focused on using the internet to record research. FamilySearch.org was ahead of the curve. Their online presence was growing, and the church encouraged us to use their software—Personal Ancestral File, or .paf. One enthusiastic presenter claimed he’d found 10,000 relatives using it. I had maybe 50 entered into a TI-84 computer program stored on cassette. I was in awe.

One winter Friday, with the kids in bed, I decided to do some “research.” By that, I meant: browse other people’s trees and copy their information into mine. I called it my Insta-Tree—click, match, done.

Unfortunately, no one had emphasized the importance of verifying these matches. So around 10:00 p.m., using dial-up (because no one would call that late anyway), I stumbled upon a promising lead on my husband’s Samuelson line. The tree stretched back way in time. I was thrilled. He kissed me goodnight, and I promised I’d head to bed once I reached the end of the line.

At 2:00 a.m., I reached it.

His distant ancestor, according to the tree, was none other than Thor—yes, the Norse god of thunder, complete with hammer and wife Sif. I stared in disbelief. Maybe it was just a man named Thor? Nope. The tree listed Asgard as his residence. I nearly cried.

Why would someone post that? Maybe they truly believed it. Maybe they were trolling gullible researchers like me. Either way, I realized it would take longer to undo the damage than it did to blindly click “add.”

I’m not proud of this—but I left it in my tree until January 2025. For nearly 30 years. Why? It was on my to-do list but never a priority. Plus, it served as a reminder not to trust unverified work. I finally removed it when I wrote my Swedish ancestor book and committed to scrubbing my online tree of anything unproven. I’ve since done the same for my Croatia, France, Germany, and Switzerland branches, and I’ll continue when I begin my Great Britain book this fall.

That night, exhausted, I crawled into bed. My husband stirred and asked if I’d found anything interesting. “Yeah,” I said, “you descend from the god Thor.” He grunted, rolled over, and said, “Nice.”

“No,” I thought. “Not nice at all.”

The next morning, he remembered I’d said something “interesting,” but not what it was. When I reminded him, he laughed—and still insists to this day that he’s a direct descendant of Thor. Second lesson learned: do not share your research with family until you know it’s correct. Because they will only remember the stuff you wish they’d forget.


Next week, I’ll share Lesson Two from my genealogy learning curve. Spoiler: it involves trusting a family member’s stories. Stay tuned.