Fall Genealogy Tasks

 

AI Graphic

The weather hasn't yet cooled and I'm not complaining but it is officially fall.

Before I get back to writing my next and final (hooray!) family genealogy book on our Great British lines I decided I had to practice what I preach and take care of some pressing tech tasks that I have put off for way too long. The first was really bothering me as it was boring and there are so many more interesting things to do in genealogy then preserve photos.

Long ago, in 2002, a world that was radically different then today, my cell phone saved all of my photos to a desktop program called Picassa that Google later purchased. I used that product until 2018 when Google rolled it into Google Photos. That's when my problems began.

When Picassa ceased to exist it lost some of my photos, years 2002, 2007, 2010, and 2019. I wasn't worried about 2002 & 2007 as my kids were still in school and I was still scrapbooking so I have those photos. I digitized the scrapbooks so we were good. 2010 & 2019, not so much. Sure, other family members probably have some of the photos but I always was the main photographer so much of that is lost. I know, it could be a lot worse but still, not happy about it.

The next issue was with the rollover, some of my photos were doubled and even tripled. New photos were created from group shots - just the heads of whatever the tech decided to select. Then it began creating memory albums. Now that doesn't sound bad but it became a problem because it used up space and Google, tying all their products together, kept reminding me I needed to purchase additional space from them or I could no longer have a functioning email.

Occassionally, I'd go into photos and delete some of the duplicates and albums but they just would pop back up. On my to-do list was to remove ALL of my Google photos, store them in Dropbox, and back them up to a standalone hard drive. BORING. but. necessary.

For Valentine's Day, one of my kids gave me a picture frame where you can store and see changing photos. This gave me the impetus to get the photos out of Google. Next week I'll print the detailed directions on how you can do that fairly quickly and easily, meaning not saving one photo at a time which I initially was doing.

I also realized that I needed to synch my Ancestry.com tree as it's been awhile since I did that. I no longer use RootsMagic and since I last synched, I got a new desktop so I didn't have Family Tree Maker downloaded to it. Now FTM has come out with their update (in May 2025 but it's called 2024, go figure). I somehow missed the promotions but they have one remaining, half price for current license members so I took advantage of it ($40 instead of $80). I decided if I was going to save Dropbox to the stand alone drive I might was well include my Ancestry tree since I've just blogged about how I was working at updating it. Yes, it's still a work in progress but I'd rather save what I have as I'll never be done with it.

Next up was to delete everything on my stand alone drive as it was all old and not relevant so I turned it back to factory settings. Took hours!

Meanwhile, one of our adult kids had their credit card stolen and the thieves, being really stupid - (Jose Lopez - I am calling you stupid!) bought items in their own name and then had it sent to our kids' address. (Now you see why I am calling Jose stupid - really, does he want to get caught? Don't even need a forensic genealogist for that one.)

Jose or whoever was the original thief, was fairly smart at the beginning. Only purchased from stores the kid always uses so for the first two weeks the scam wasn't noticed. Then, boldness hit and the thief began using it for large sums at stores never used by the kid. By the time it was noticed thousands of dollars of items had been purchased but thankfully, some get to be returned to the companies since they arrived at the kid's house. (Jose, did you think you were then going to be a porch pirate, too?) Kid called the credit card company for a dispute and the police to file a report in case Jose was local and was going to be paying a home visit. Cop informed us that a local woman got taken for $499,000 the previous week because they also stole her social security number and took out loans. What a nightmare!

That made me realize it was time for me to update some of my own financial practices.

1. You may have some items on recurring charges. We've decided to use a separate card for those because it's a major pain to have to contact those vendors to change an account if your card is shut down.
2. Since the card was stolen locally (we know this for reasons I'm not disclosing so the guilty can get their due, too bad, Jose, that bed you bought won't get you a good night's sleep in jail because it's already been returned) we decided to use one card just for local purchases. It's a card with a good reputation to notice fraud quickly so we won't have to dispute lots of charges when (not if) it get's compromised.
3. We'll use another reputable card for online only purchases.

If you're thinking, that's a back up for a back up and yes it is, just like we do to save our genealogy data. This led me to realize it's been awhile since I updated my passwords so I spent time doing that as well.

Last task I haven't completed but is equally important, albeit BORING, is saving many of my emails. Lots of them contain genealogical info and I want to make sure the info is saved to the correct ancestor's file in Dropbox. That's my next project and by then, well, it'll probably be time to redo the cycle.

With the colder weather u perhaps coming next week this is a gentle reminder, dear reader, to take a look at your items to do and start plugging away at them.

Book Review: Genealogy in Reverse: Finding the Living by Cheri Hudson Passey

 

Available through Genealogical .com

Have you ever wondered how genealogical researchers who work to repatriate deceased military remains make connections with descendants? Do your messages to DNA matches sometimes go unanswered? Or perhaps you’re hoping to discover who in the family has great-great-grandpa’s Bible. If so, Cheri Hudson Passey’s new book, Genealogy in Reverse: Finding the Living – A Practical Guide for All Genealogists, may be of interest.

This compact volume introduces readers to strategies for locating living relatives. Drawing on her long experience in the field of repatriation research, Passey shares methods for moving beyond records of the dead and into the equally challenging task of connecting with their descendants. While much of genealogy focuses on the past, she reminds us that success often depends on bridging the gap between past and present.

The book also touches on the sensitive issue of privacy and provides advice on how to reach out respectfully to family members who may be reluctant to talk. Passey’s suggestions for phrasing messages and making cold calls will be especially helpful for researchers who find that first step intimidating.

Genealogy often emphasizes discovering those who came before us, but as Passey reminds us, connections with the living can be just as vital. Genealogy in Reverse may not answer every question, yet it provides a starting point for anyone curious about expanding their research beyond the traditional paper trail. For readers who have struggled to make contact with DNA matches or distant cousins, this slim guide may inspire new approaches worth trying. Available from Genealogical.com as an eBook or paperback.

How to Clean Your Ancestry Tree Without Paying for Pro Tools Part 3

AI Generated

For the past two weeks I’ve been blogging about Ancestry.com’s Pro Tools. You can read about my experience here and here.

Today, I’m going to show you how to clean your Ancestry tree without paying for Pro Tools. It’s super easy and honestly, I wish I’d thought of this years ago.

Start by picking a free or low-cost software program. Family Tree Maker and RootsMagic both sync directly with Ancestry. RootsMagic Essentials is free, but large trees can slow it down (I blogged about that here). If you don’t need access to your photos or documents and just want to focus on fixing errors, you can also download your tree as a GEDCOM and import it into Legacy Family Tree, which is what I did.

I kept things simple. I didn’t need media files for the check up, I just wanted to identify structural problems in my tree.

Here’s how to do it:

1. On Ancestry, go to your tree.
2. Click Tree Settings under Trees > Create & Manage Trees.
3. Scroll down and select Export Tree.
4. Once complete, download the file to your computer (it usually lands in your Downloads folder or OneDrive).
5. Open your genealogy software and import the GEDCOM.
6. Run the problem checker.

If you run into trouble with the software, you can literally ask ChatGPT (aka Geni!) for help. That’s how I found this entire workaround.

Once your tree is loaded, use the software’s built-in tools to flag potential problems. In Legacy, I went to Tools > Potential Problems. I set criteria to mirror the kinds of problems flagged by Ancestry’s Pro Tools, things like parents being too young, children born after a parent’s death, and so on.

One downside: Legacy doesn’t flag individuals with no sources, which was one of the main issues Pro Tools surfaced. But what Legacy did reveal was surprising and far more accurate.

Here’s the report I got from Legacy (the error types flagged by Ancestry are in red):

Let that sink in: 940 total errors, almost all of which are legitimate and actionable. Of that, there was only 55 errors that Ancestry claimed was 301 and they didn't identify these people! I plan on cleaning up all of the errors Legacy found as having two individuals over age 110 years is a problem Ancestry should have discovered. And the individuals with no sex given? That is a continual flaw in Ancestry's system when you are adding new individuals.

Unlike Ancestry’s Tree Checker, which falsely flagged over 10,000+ records in my tree, Legacy gave me a clean, accurate list I could work with. I now have the names and the issues. I’m going through them one by one and making the corrections directly in my Ancestry tree, since that’s still my primary working tree. I’ll continue syncing it with Family Tree Maker.

And if I get another $7 Pro Tools offer in the future? Sure, I might try it again just to check whether they’ve cleaned up the bugs. But I’ll cancel it right after. Because let’s be honest:

If Ancestry really wants our trees to be accurate, they should provide these tools for free.

We are already paying for the data, the DNA, the platform and in many cases, contributing our own hard-earned research. Charging extra for a tree-checking feature (that doesn’t even work right) feels like asking users to fix the foundation of the house they already paid to build.

So, skip the upsell. Use free software. Clean your tree with confidence. And let’s keep our standards higher than their price tags.

When Ancestry.com’s Pro Tools Fail: A Professional Genealogist’s Experience with Ancestry’s Tree Checker Part 2

AI Generated

Last week, I shared my experience with most of Ancestry.com's Pro Tools—an add-on offered for $10/month (I got in for $7 with a promotional email). You can read about those features here. Today, I’ll dive into the tool that motivated me to subscribe in the first place: Tree Checker.

If you’ve noticed the new Tree Checker score on your Ancestry tree, you might be curious. Mine showed a 9.1—“Excellent.” That aligns with my belief that my tree is about 90–95% accurate. But let’s be honest: no one has a 100% accurate tree. Without DNA confirmation for every line, there will always be an element of uncertainty. Still, I’m committed to removing the detritus that’s accumulated over years of brick wall chipping, FAN Club research, and lineage society applications.

Back in 1990, I started my tree with 50 people, using a TI-89 cartridge program. By 1995, I was entering data into FamilySearch’s .paf format. When Ancestry came along, I uploaded my work to what’s now the ubiquitous .gedcom. My skills, and my tree, have grown significantly since then. I’ve cleaned up my Swedish, Croatian, French, German, Swiss, and Dutch branches. What remains is my largest line: Great Britain. Before writing my next book, I knew it was time to clean that section.

I regularly back up my Ancestry tree to other programs (Family Tree Maker, Legacy, RootsMagic), all of which offer tree-checking tools. But because Ancestry is my primary research platform, I’ve been hesitant to clean externally and re-sync. So I was hopeful that Tree Checker would finally give me an effective cleanup solution within Ancestry.

Here’s what happened.

Tree Checker: Expectations vs. Reality

When I launched Tree Checker from the dashboard, I was greeted with a gut-punch: 14,000+ possible errors.

The majority were labeled “People with no sources.” I immediately knew what was going on. In Ancestry’s early days, there wasn’t a “web link” option. I got around that by uploading source PDFs to the Gallery or by placing citations in the timeline. Unfortunately, Tree Checker ignores those, unless it’s housed as an official Ancestry “source,” it’s invisible to the system.

But that still left other problem categories:

• Possible Duplicates
• People with Only Tree Sources
• Other Possible Errors

I’ll add here that one of the most helpful “error types” isn’t even under Tree Checker, it’s found under Pro Filters > Family Lines > People Without Relationships. These are individuals floating without connections, often leftovers from attempts to delete a line. I had about 2,000 of these and quickly removed them.

People with Only Tree Sources was next. These were added from others' trees, unsourced. That’s an easy fix, either delete them or attach a hint. Done.

Possible Duplicates looked daunting at nearly 2,000, but the number was misleading. Triplicates and higher were counted separately, and after filtering, I had fewer than 1,000 to review. Some were legitimate merges (e.g., marriage records auto-adding a new spouse). Others were not duplicates at all: families who reused names after a child died, or multiple “Johann” Harbaughs with different middle names. I worked through them in two days.

The Glitches Begin

After carefully resolving every duplicate, I noticed something troubling: they didn’t disappear from the error list. No matter what I tried, refreshing, logging out, rebooting, clearing cache, Tree Checker continued to show errors I had already corrected. I even tried deleting and re-adding a person. No dice.

Still hoping for results, I moved on to “Other Possible Errors” and found myself stunned.

Ancestry itself was causing many of the flagged issues. For instance, if a child was born in 1937 and enumerated in the 1940 census, Tree Checker would flag it as “Resident listed before birth date.” The kicker? That census record was automatically added by Ancestry in the timeline for 1935. To clear the error, I had to delete 1935's entry FOR EVERY ONE born between 1936-1940.

Swedish church records were another problem. Ancestry indexes these by range (e.g., 1723–1728). If a child was born in 1724, Tree Checker flagged the 1723 record as occurring before birth. Completely illogical and a huge waste of my time to clean up!

Some new error flags also made no sense:

• “Birth/Death dates span more than 10 years” with only one sourced date. What?
• "Significant age difference between spouses" um, 2 years!
• “Marriage occurred after spouse’s death” when no death date was even given. See the above screenshot proving the error was false.

And here’s the real kicker: even when I corrected the problems, they remained in the count. Over the next three days, my “error total” would inexplicably rise despite spending hours cleaning.

Note that it says there are 2 possible duplicates but none show.

People with only tree sources shows 1 but none are provided.

Under all possible errors the counter states 201 but there is only 1 error showing and it is not an error when you go to that page.

This reminded me of a long ago problem Ancestry had with what was called "Ghost Hints." You can read my how-to-fix blog about it here. I tried that again but it appears that Ancestry has tightened up security and my fix it no longer worked.

As a genealogist, I dug into the data. I exported the report, analyzed the stats, and discovered something stunning:

75% of the Tree Checker results were false positives. That’s not a helpful tool -that’s noise! Seeing it graphically made me realize I had been sold a product that doesn't work:

To top it off, this also distorts your overall Tree Checker “score.” I now wonder what my real rating would be if the tool actually worked. With the changes that took, my score reached a 9.4.

The Final Straw

I then turned to the “No Sources” filter and began manually fixing issues from A–Be, X, Y, and Z. That’s when I hit the wall. Even attaching suggested Ancestry hints they no longer removed individuals from the list. Not user error, this was a flat-out malfunction.

That’s when I noticed the word Beta scattered throughout Pro Tools. Beta testing, by definition, is the final phase before a product goes public. Users test real-world functionality and provide feedback. But here’s the problem:

Ancestry released an untested tool to the public and then charged for it.

If you charge admission before the dress rehearsal is done, that’s not Beta testing. That’s profiteering.

But that's not all! Ancestry then sent me an email with their data about the changes I made to my tree:

What does 300% more duplicates found even mean?! We know I had no duplicates and most of those that they believed were duplicates were not. 84% fewer issues discovered? Does that mean my tree still has 16% undiscovered issues? If so, how would I ever find them when Pro Tools can't identify them and the counter doesn't work?

Where Do We Go From Here?

I’m not just disappointed, I’m concerned. It’s clear Ancestry recognizes the problem of flawed user trees. But their solution shouldn’t be charging extra for a broken product.

And now, they’ve rolled out something even more baffling, a $5,000/year “cohort club” promising professional coaching, a few DNA kits, and discounted branded merchandise. (Want a denim jacket? You can buy one at a discount.) Click the link as I'm not making this up. There VIP service, you get a working phone number if you have a problem. Pardon me, but I always thought that's what a legitimate business offered TO ALL OF THEIR CUSTOMERS for free.

In a recent webinar, the presenter said she came up with the idea of genealogy coaching. That’s interesting, since I’ve offered coaching on my website for over a decade at a fraction of the price. I believe everyone should have access to their heritage, not just those who can afford a luxury tier. I was also appalled to hear that professional genealogists charge tens of thousands of dollars a year. No, just no!

I use Ancestry daily and plan to continue. But I’ve cancelled my Pro Tools subscription.

Next week, I’ll share how I cleaned up my tree without shelling out extra cash.

When Ancestry.com’s Pro Tools Fail: A Professional Genealogist’s Experience with Ancestry’s Tree Checker Part 1

 

AI Generated

As a long-time Ancestry.com user, I decided to give their new Pro Tools a spin during the July 4th weekend. With a family member recovering from surgery, I wasn’t traveling, and I had trimmed my client and presentation load to be more available at home. So, for the introductory $7.00 fee, I figured—why not?

Today's blog, and the two that follow, details what happened next: a real-world walkthrough of what Pro Tools offers and whether it’s worth the extra cost above your regular Ancestry subscription.

After payment—seamless, of course, since Ancestry has mastered the art of parting you from your money—I waited around two hours for the tools to appear. No email alert, just a dashboard update with Pro Tools shortcuts quietly waiting for me.

I expected a guide or orientation video. Nope. Clicking “More Pro Tools” brought up the feature list shown below. So let’s walk through each one:

Networks
This is basically a built-in FAN Club tracker. You can add people to your tree who aren’t related but interacted with your ancestors—neighbors, witnesses, etc. I wish this existed back when I was wrestling with my Duer brick wall. Back then, I added these people manually and unlinked them to avoid false connections. Networks would have saved a lot of time.

Enhanced Shared Matches
The “enhancement” is only one thing: DNA clusters. And only if you've tested through Ancestry. Here's the kicker: MyHeritage offers this for free—even if you didn't test with them but uploaded your DNA there. Ancestry’s version? Sparse and underwhelming. I have no maternal clusters and only 27 paternal ones.

MyHeritage has far more, thanks to their broader global dataset. Winner: MyHeritage.

Smart Filters
Sort your tree by name, birth, or death dates. Sounds great—until you realize it only displays the first 10,000 people. My tree has 70,000+ individuals from years of research and surname studies. So... not helpful. Pass.

Charts and Reports
You get four types: Descendancy, Ahnentafel, Register, and Family Group, with cutesy “tree” headers (Pine, Birch, Oak, Maple). But each slaps the Ancestry logo on top. Legacy and RootsMagic do it better—and they’re free. Another strike.

Tree Mapper
A world map with green highlights where your ancestors lived. Sounds promising, until it confidently tells me my ancestor in Zwol, Overijssel (Netherlands) lived in South Africa. Another resided in Queensland, Jamaica, New York and not in Queensland, Australia where it was flagged. Error after error makes this useless for real research.

Tree Insights
This tool tells you surname meanings, top five surnames, oldest people in your tree, and “notable” outliers—like couples who married at 1 year old. (Spoiler: they didn’t.) It clearly can’t interpret “Abt.” dates, and many errors it finds weren’t flagged by the Tree Checker. Insightful? Yes. Reliable? Meh.

This is getting long, so I’ll save the main course—Tree Checker—for the next post. Spoiler: It’s the only reason I tried Pro Tools at all. And it’s a tale worth telling.

Stay tuned.

Book Review: Your Stripped Bare Guide to Citing & Using History Sources by Elizabeth Shown Mills

 

Genealogical.com

They say you can’t judge a book by its cover but in the case of Elizabeth Shown Mills’s latest, Your Stripped Bare Guide to Citing & Using History Sources (2025), the cover is so charming it almost makes me want to sit down and write a source citation. And that’s saying something, coming from someone who usually dreads the task and full disclosure, often cheats by letting AI do it for her.

You might wonder, after decades of writing about citations, what more could ESM possibly have to say? I own all four editions of her past works, Evidence Explained, along with two editions of Professional Genealogy. Those texts are monumental, hefty, encyclopedic guides designed to help family historians create (and yes, crafting a citation is an art) a source reference for every conceivable research situation. But therein lies the problem; they are so thorough they can overwhelm beginners. Too often, they end up gathering dust and making the bookshelf sag, which is a shame because they hold the keys to accurate, credible, and most importantly, findable research.

I’ll admit, I’ve grown a bit lazy since AI became part of my workflow. For my personal research, I often settle for a quick and dirty Chicago-style citation generated by a chatbot. I’ve noticed some of my editors have relaxed their standards, too. Why? Because tracking down the exact template in Evidence Explained can be a time consuming hunt.

Enter Your Stripped Bare Guide. This is the book I didn’t know I’d been waiting for, clear, concise, and portable. At just 138 pages, it’s a featherweight compared to its predecessors, but it’s packed with practical, ready-to-use information. I liken it to The Elements of Style, a distilled, timeless resource that belongs within arm’s reach of every researcher’s desk.

And timeless it is. Consider how much genealogy has changed since 2007, when the first Evidence Explained was published. Back then, FamilySearch was still shipping microfilm via snail mail to local Family History Centers. AI existed only in movie scripts. Blogging was in its infancy. The very first iPhone had just been released. Now, so much is online (though not everything) and our research methods continue to evolve. I had wondered, when ESM retired, who would carry the citation torch into this ever changing landscape. No worries now! Stripped Bare teaches the core principles so we can confidently adapt to whatever new technology comes next.

Pro tip: read the foreword first, it’s a soothing antidote to any citation anxiety. The opening chapter lays out universal guidelines for any source, followed by “Fundamentals of Documentation,” filled with tips and practical recommendations.

One passage made me laugh out loud; ESM notes that the purpose of citations isn’t to help others find our sources. Gasp! I could picture one of my high school English teachers having an apoplexy. After all, isn’t that what we were always taught? Even now, I carry that belief with me. Stripped Bare challenges that notion, and while some “old school” researchers may bristle, I found it refreshing.

I also appreciated the section on citing derivatives. About a decade ago, I found myself in a spirited (and unresolved) debate with another professional genealogist who insisted I was wrong to cite both the original and the derivative. ESM explains my position far more elegantly than I did, which may be why we never reached agreement.

Here’s what I love most, Stripped Bare offers just 14 templates. Yes, that’s the same number found in Evidence Explained, and many of the examples are familiar, but what’s gone is the 555 page sprawl of trying to illustrate every possible source on earth. That level of detail served its purpose once, but it’s no longer necessary for most researchers.

Some might think this is simply a repackaged version of the first three chapters of Evidence Explained. It isn’t. While there’s necessary overlap, after all, the fundamentals don’t change, the material is rewritten in a fresh, approachable way. Most importantly, it keeps evidence analysis front and center, reminding us that citation is not just about formatting, but about thinking critically about our sources.

For intermediate researchers and beyond, I highly recommend Your Stripped Bare Guide to Citing & Using History Sources. It’s available in paperback and eBook from Genealogical.com—and it just might make you want to write your next citation.

The Summer of My Genealogical Discontent, Lesson 8: What I’ve Learned (and Unlearned)

 And just like that, we’ve reached the end of my Summer of Genealogical Discontent—a season spent digging not into records, but into my own past as a researcher. I set out to share the biggest mistakes I made in my early years of genealogy—not to dwell on regret, but to show how growth happens in real time, and to offer encouragement to those just starting out (or maybe starting over).

Let’s take a look back at what I’ve learned—and unlearned—along the way:

Lesson 1: Trust, But Verify
Like many beginners, I started out believing online family trees were gospel. I trusted matches, clicked too quickly, and added generations without verifying. The result? A line that led all the way back to the Norse god Thor. It took me years (and a lot of embarrassment) to clean it up—but it taught me a lesson I never forgot: don't trust a tree you didn’t plant yourself.

Lesson 2: Cousin Trust… or Not
It turns out, family stories can be just as misleading as unsourced online trees. I ignored obvious errors in a cousin’s genealogy book because I wanted to believe the family “knew.” But when someone challenged the name of my second great-grandmother—despite multiple official records proving it—I realized again that evidence must always come first.

Lesson 3: To Save or Not to Save?
I didn’t always save my records. I thought I’d find them again. That thinking cost me time, energy, and two long drives to a FamilySearch affiliate library when a key will I’d once seen was no longer accessible online. Now I save everything—and back it up—because in genealogy, proof is everything.

Lesson 4: Confidence
I lacked confidence early on and let others in the genealogy community make me feel like an outsider. When a DAR member berated me for an “error” (in all caps), I removed the ancestor from my tree. But I was right, and I had the documents to prove it. Over time, I learned to trust my research—and to stand firm when I had the facts.

Lesson 5: The Software Shuffle
Tech has been both a blessing and a burden. I’ve tried nearly every genealogy software platform and been burned more than once by syncing issues, glitches, and disappearing records. The lesson? Diversify your tools. Keep your files backed up and your data portable. Nothing lasts forever, including your favorite software.

Lesson 6: Failing to Join an Organization
For too long, I went it alone. I didn’t know where to turn, didn’t have the money, and assumed no one would care about my obsession with dead people. I was wrong. Once I joined societies and attended conferences, my skills grew exponentially. Genealogy may start as a solo act, but it thrives in community.

Lesson 7: Listening to the Pros (or Not)
When I finally decided to “go pro,” I followed advice that didn’t align with who I was or who I wanted to serve. I was told I had to charge more, take specific courses, and follow a certain path. But that path didn’t fit me—or my clients. Eventually, I stopped listening to people who wanted me to become a different kind of genealogist and started building a business that reflected my values. And I’ve never looked back.

---

Genealogy has always been about more than names and dates for me. It’s about honesty. Resilience. Perspective. It’s about owning the full story—including the mistakes—and realizing that every misstep is part of the journey.

As I wrap up this summer series, I’m looking forward to shifting gears a bit. I recently attended a genealogy conference in an area I have no experience. September brings another conference, more lessons, and no doubt, more stories.

Because in genealogy—and in life—there’s always another chapter. Next week I'll blog a book review - stay tuned!