Well, it's been a week. Amend that: not only was it a week, but it was a week when I wasn't even a stay-at-home #NotAtRootsTech participant.
There are a few reasons for that. To start with, the past week has been rough. Along with a co-instructor, I've begun a new, four-part genealogy class in person—something I've long felt the need to do. Doing stuff in person takes time, effort, travel, and other logistics. No wonder people prefer the convenience of Zooming in—but I firmly believe we miss something in the bargain.
Add to that, with beautiful spring weather comes a long-awaited construction project for our home, held at bay during the rainy weather last month. Only problem: those convenient virtual meetings used to conduct genealogy society business during the week also find a way to share the hammering, sawing, and drilling occurring outside my now-demolished living room wall. If I knew this was going to be the week the demo actually happened, perhaps I would have made this my week to travel to RootsTech in person.
Not to worry; I can always go back and watch the recordings. Sure, I'll miss out on the great sales exploding out of the exhibit hall, even for those #NotAtRootsTech. But perhaps some time later in the year will be more peaceful—or at least conducive to watching reruns of RootsTech sessions.
Who am I kidding here? Truth be told, what I was doing in my "spare" time was hyper-fixating on my latest project: examining all those Rainey DNA matches to see who their matches might have been, and whether those shared matches might tie me in to the other branches of Thomas Firth Rainey's family tree.
And I think, after several iterations of that process—did I mention the word "tedious"?—I may have found one new connection. I'll keep at it next week, as well. But it's encouraging to find a match which may well lead me to other connections to my third great-grandfather in this Rainey line. I need some wiggle room to explore his possible extended family.

