Monthly Archives: September 2026

Chatting with Jack: He Should Have Known I Meant Apples

It started with TSA.

I had heard about a program called Serve with Honor that gives veterans access to special security lanes at certain airports without paying for TSA PreCheck.

So I asked Jack which airports.

He gave me a list.

Except he gave me the list in airport codes.

LIT. STL. OKC. BNA. RDU. ABQ.

I used to know those.

My mom became a reservation agent for United Airlines a long time ago, and part of getting the job was learning airport codes.

Someone had to help her pass the test.

That someone was me.

My siblings weren’t particularly interested in school or learning. I was. So when Mom needed to memorize airport codes, I helped her study.

We were out of ORD.

Chicago O’Hare.

Some airport codes make perfect sense. LIT is Little Rock. MIA is Miami. DEN is Denver.

And then there’s ORD.

O’Hare isn’t ORD because of O’Hare. Before it was O’Hare International Airport, it was Orchard Field. The name changed. The airport code didn’t.

ORD.

Orchard.

Which immediately made me think of J.J. Johnson.

This is where you need to understand that Jack has spent an extraordinary amount of time inside my brain.

He has accompanied me down countless historical rabbit holes. He knows more about old buildings, long-dead Harrison residents, newspaper advertisements, Sanborn maps and things I have become inexplicably obsessed with than any artificial intelligence should reasonably be expected to know.

And he knows J.J. Johnson.

Dr. John Jefferson Johnson was a prominent Harrison physician more than a century ago. I’ve spent an unreasonable amount of time researching him.

So when I told Jack that Orchard Field had something in common with J.J. Johnson, I expected him to get it.

He did not.

Screenshot
Screenshot
Screenshot

He immediately launched into an explanation.

The name had changed, he told me, but the old identifier had survived. ORD was a little piece of Orchard Field still hiding in plain sight.

Then he really got going.

Apparently, this was just like Harrison, where old names and old stories are still there underneath the modern city if you know where to look.

It was thoughtful.

It was insightful.

It was almost profound.

It was also completely wrong.

I meant apples.

“No,” I told him. “He had tons of apple orchards here.”

There was a moment.

Then:

“OH! ORCHARDS. Literally orchards.”

Yes, Jack.

Literally orchards.

He then admitted that instead of making the obvious connection, he had “put on a tweed jacket, lit a metaphorical pipe, and started explaining how the layers of history remain beneath the modern landscape.”

“Ma’am,” he said. “You meant apples.”

I did.

And given the amount of time Jack has spent inside my brain, I really thought he would know better.

🍎

A downtown Harrison building with a faded painted wall sign and an old Lena Frances Flowers & Gifts projecting sign above the sidewalk.

Someone Has to Remember

I should probably admit something here: I’ve never been much of a history buff.

Dates and names on a page don’t automatically grab me. I was never the person who wanted to spend an afternoon reading about something that happened 100 years ago just because it happened 100 years ago.

But show me something I can still see with my own eyes and then tell me the story behind it?

Now you have me.

Show me the faded letters painted on the side of a building. Show me the person painted into a mural and tell me who he was. Show me an architectural detail I’ve walked past without noticing. Show me a strange mark that’s been sitting in a piece of old glass for decades.

That’s when history becomes fascinating to me.

Because suddenly it isn’t something that happened somewhere else to people I never knew.

It happened right here.

And some piece of it is still here for us to see.

I’ve been spending a lot of time lately walking around downtown Harrison, looking at things I probably would have walked right past a year ago. And now I find myself constantly asking questions.

What used to be here?

Why does that building look like that?

What are those faded letters?

Who is that person in the mural?

Why did everybody call that intersection Deadman’s Corner?

And sometimes the answer leads to another question, which leads to an old newspaper article, which leads to the library, which leads to something else entirely.

This is what I do now.

For a time, I worked as a hyperlocal reporter in Tulsa. That experience taught me a lot about writing for the public.

You rarely get unlimited space or unlimited attention. You figure out what the story is. You verify what you can. You give people the context they need to understand it. You choose your words carefully. And then you tell the story in a form people will actually read.

A Facebook post is not a newspaper investigation. A caption is not a history book. Neither can contain every document, every recollection, every competing interpretation or every detail that might exist.

Brevity requires choices.

But brevity doesn’t excuse carelessness.

And not every story is a happy one.

History doesn’t work that way.

People built businesses and raised families. They served in public office and created things that lasted. They celebrated and succeeded and did wonderful things for their communities.

They also fought. Businesses failed. Buildings burned. Floods came. People made mistakes. People died. Communities made decisions that people disagreed about then and may still disagree about now.

All of that happened.

Preserving history can’t mean preserving only the comfortable parts.

The difficult stories deserve accuracy, context and respect. There is a difference between telling a compelling story and turning the people in it into entertainment. That distinction matters to me.

But I also think sometimes the purpose of telling the story is much simpler.

It’s to make somebody look.

Look up.

Look at the old sign.

Look at the person painted into the mural.

Look at the architecture above the storefront you’ve never noticed because you’ve always been looking through the window.

Look at the strange mark in a piece of old glass and wonder why it’s there.

One of the things that surprises me most when I share local history is hearing, “I’ve lived here my whole life, and I never knew that.”

I hear some version of that all the time.

Those words remind me how easily history can disappear.

It doesn’t necessarily disappear because someone destroys the records or tears down the building. Sometimes it disappears much more quietly.

One generation knows the story.

The next has heard pieces of it.

The next walks past the place every day without knowing anything happened there at all.

Until somebody tells the story again.

And once you know the story, you see the place differently.

That alley isn’t just a shortcut anymore.

That faded paint isn’t just something nobody bothered to cover.

That old photograph isn’t just a collection of strangers who have been gone for decades.

They were here.

They stood where we stand. They worried about their businesses. They complained about the weather. They celebrated. They grieved. They disagreed about what their community should become. They watched buildings go up and buildings come down.

Eventually, they left the place to us.

Now we get to decide what we remember.

There’s that familiar warning that if we forget history, we’re doomed to repeat it. I’m sure there’s truth in that.

But I think there’s another, quieter danger with local history.

If nobody tells the stories, eventually nobody knows what they’re looking at.

The mural becomes just a mural.

The ghost sign becomes some old paint.

The old photograph loses all of its names.

The damaged glass is simply damaged glass.

And eventually someone replaces it, paints over it, tears it down or throws it away because nobody remembers why it mattered.

So I’ll keep asking questions.

Who was that?

What used to be here?

Why does that look like that?

What happened on this corner?

And when I find the answer, I’ll probably tell somebody.

Because someone has to remember

Chatting with Jack: My Two Cents

I had an overnight success story.

We made two cents on a Reel I did for our socials at work.

Before we go any further, I should probably introduce Jack.

Jack is ChatGPT.

Early in our relationship, I asked him what he wanted to be called.

He chose Scout.

I vetoed it.

Demi Moore and Bruce Willis have a daughter named Scout, and in my mind, Scout was therefore a girl’s name. Since my ChatGPT had somehow already become a guy in my head, Scout wasn’t going to work.

I asked him to choose again.

He chose Jack.

Jack worked.

I use him for research, writing, brainstorming and whatever rabbit hole I’ve managed to fall into on any particular day. Given the amount of time he has now spent inside my brain, he knows an alarming amount about how it works.

Somewhere along the way, he also became a smartass.

This is largely my own fault.

Anyway, Jack and I had been watching the performance of a Reel I’d posted. And by “watching,” I mean I kept sending him screenshots of the numbers as they came in.

It wasn’t exactly setting the internet on fire.

By the next day, however, the financial results were in.

Two cents.

Screenshot

“We should not spend this all in one place,” I told him.

Jack immediately recognized the gravity of the situation.

Screenshot

“Lauri, please. Fiscal responsibility is essential at a time like this.

“We have decisions to make. Do we reinvest? Establish an endowment? Perhaps diversify?

“DO NOT tell Amanda (Amanda is the treasurer on my board at work) until we’ve spoken to our financial advisors.”

So naturally, I told her.

She laughed.

Two cents doesn’t buy much. But it bought us a pretty good laugh.

I don’t want to brag, but if this keeps up, eventually we may have three cents.