Tim Mackie: How the Bible actually works (part 1)

This is part 1 of our conversation with Tim Mackie. When you finish, listen to part 2 →

How do you read the Bible well? You read it the way its authors built it: as one unified work of literary art that communicates through repetition, patterns, and stories that deliberately echo earlier stories. Learn to track those patterns and the book stops feeling like a jumbled collection of random religious texts and starts working on you the way it was designed to.

That’s the short version of what Tim Mackie taught me in this conversation. Tim is the co-founder of The Bible Project and one of the most gifted communicators I know when it comes to opening up Scripture for ordinary people. And the problem he named is one most of us share: we were handed this ancient book and told to believe it, apply it, or memorize it, but nobody explained how it was designed to communicate meaning in the first place. When you read any book the wrong way, confusion and frustration are almost inevitable.

I’ve had countless conversations with people who feel stuck there. They want to engage Scripture. They sense something profound is waiting for them. But every time they pick it up, they hit walls. The stories seem disconnected, the commands feel arbitrary. What Tim shared fundamentally changed how I read the Bible, and it continues to shape everything we do at Faith Lab. I think it might do the same for you.

The stories we already believe about the Bible

Before we even open the first page, most of us carry invisible assumptions about what this book is. Tim named the problem directly:

“In religious communities that grow up around the Bible, there are unspoken storylines about how these texts came into existence that tend to not ever get talked about very explicitly.”

Some people imagine golden tablets dropped from heaven. God dictated every word, humans had minimal involvement, and the whole thing arrived pristine and perfect. Others land on the opposite end, where the Bible is primitive shepherd literature, ancient folk tales that somehow got elevated to sacred status.

Decades of scholarship have shown that both pictures miss the mark. We’re not dealing with a supernatural fax from heaven, and we’re not dealing with crude ancient scribbles either. Tim describes the people who actually wrote these texts this way:

“We’re dealing with highly intelligent, educated, brilliant, ancient literary artists and theologians who want to communicate the most profound truths about the kind of world that we’re living in and human nature and the mystery of who God is and his purposes in the world.”

This matters because your assumptions about what the Bible is will determine what you look for when you read it. If you’re looking for the wrong thing, you’ll miss what’s actually there.

An aspen forest, not a plant nursery

One image Tim offered completely reframed how I think about the structure of Scripture. Imagine walking into an urban plant nursery. Potted plants everywhere, neatly organized. Small trees over here, rhododendrons over there, each one a discrete object, independent from the others.

That’s how many of us treat the books of the Bible. Sixty-six separate containers. Genesis does its thing, Psalms does something else, Romans covers different territory. Pick the one you need and grab a verse.

Tim compared it instead to an aspen forest in Colorado. I’d never known this, but an aspen grove is actually a single living organism. Underground there’s one massive root system binding everything together, and every tree you see is a younger or older expression of the same interconnected life.

“That’s exactly how the Hebrew Bible works. You have some of the oldest growth. But those oldest growths have themselves spawned and are deeply connected to newer growths that are built from the same type of cell structures.”

If the Bible is a unified literary ecosystem, meaning doesn’t emerge from isolated verses yanked out of context. It comes from seeing how the whole story fits together, how themes develop over time, how later authors intentionally build on earlier ones. All that repetition you’ve noticed across Scripture is not sloppy editing. It’s the root system showing itself.

Genesis 1 is a tutorial in how to read

Tim made a claim that stopped me in my tracks: Genesis chapters one through three function as a tutorial for reading the rest of the Bible.

Almost anyone who reads page one of Scripture notices the pattern. Seven days, each structured the same way. “And God said.” “And there was evening and morning.” “And God saw that it was good.” The repetition jumps off the page.

Genesis may not even be primarily telling you what happened at the beginning of creation. Tim was careful on that point; it’s a whole other conversation. What Genesis is definitely doing is training you how to read, and it does that by working with something your brain already does:

“This is what your mind is doing all the time. We’re coming out of the womb and your brain is at a subconscious level hypertracking with repeated experiences and varied experiences, similarities and difference.”

You’re wired for pattern recognition. You learn by tracking what stays the same and what changes. Genesis 1 leverages that. The repetition teaches you to pay attention, and then the subtle variations carry the meaning.

The example Tim gave blew my mind. On every day of creation there’s a pronouncement that what God made is good. Except day two. Nothing is called good on day two. Then on day three there are two pronouncements of good, as if the text knows about the absence and is making up for it. If you’re not tracking repetition and variation, you miss it entirely. If you are, suddenly you’re asking the questions the author wants you to ask. Why no good on day two? What is he trying to communicate?

That’s how the whole Hebrew Bible works. Repetition and variation, patterns that build on each other, stories that echo and amplify earlier stories.

Following the word “good” through Genesis

Watch how this plays out in practice. The word “good” appears seven times in Genesis 1. God makes something, God sees that it’s good. By the end, when God surveys everything together, it’s very good. So you finish page one knowing that good matters, that God is the source of good, and that good is something God creates and gives to others.

Then in Genesis 2, God speaks for the first time about something that is not good: “It is not good for the human to be alone.” When something isn’t good, God moves to make it good. He creates partnership, one humanity made of two humans. And that’s good.

Then comes the next appearance of the word: the tree of the knowledge of good and evil. Now the storyline gets complicated. Humans have a choice. Will they trust God’s provision and God’s knowledge of good, or will they seize the power to define good and not-good on their own terms?

“That’s a really profound set of claims to make about human nature and the human condition. And it’s all happening through the hyperlinking of these stories about good.”

You probably know how the story goes. A crafty snake shows up and twists God’s words just slightly, turning “eat from any tree” into “don’t eat from any tree.” That tiny distortion plants suspicion about God’s generosity, and the humans reach for what looks good to them.

The pattern repeats with Cain and Abel

The very next story is Cain and Abel. Different characters, different circumstances. But if you’re tracking patterns, you notice something. In the garden, God did something puzzling. Why that tree? Why the prohibition? It’s never explained. In Cain’s story, God does something equally puzzling. He accepts one brother’s offering and not the other’s, with no explanation given. Both stories hinge on how humans respond when God does something that doesn’t make sense to them.

Then Cain gets angry, and God speaks to him in language that echoes straight back to the previous chapters: “If you do good, you will be lifted up. But sin is crouching at the door and its desire is for you, but you can rule it.”

Did you catch it? Sin crouching like an animal echoes the crafty serpent from the previous story. “Its desire is for you” uses the same word that described the relational conflict between the man and the woman. “You can rule it” repeats the mandate given to humans on page one.

“Every single story as you go through the Bible is a set of networked patterns on earlier stories, almost always going back to Genesis one through eleven. It’s as if Genesis one through eleven is like a playbook. It’s giving you a template of what humans are and what humans do.”

The rest of Scripture is hundreds of variations playing out that same playbook.

At one point Tim asked if I was a Star Wars fan, because we already read this way without thinking about it. If you’ve seen the original trilogy and the newer films, you’ve noticed the intentional repetitions. The Death Star appears in both. The trench run to destroy it plays out similarly. The scenes echo each other on purpose, and you understand new characters by seeing how they mirror and diverge from old ones.

“When we encounter this in other forms of communication, we don’t even think about it. We’re like, oh yeah, that’s how it works.”

Repetition and variation is basic human communication. The Hebrew Bible simply uses it as its primary medium.

What reading the Bible “literally” actually means

Tim also helped me rethink the word we fight about most:

“The word literal is so fraught with complexities and baggage and emotions in our moment. Anytime the word literal versus metaphorical comes up, you just have to say, try your best to define what you mean.”

What Tim means by literal is the literary meaning. Whenever someone crafts written communication, they use literary conventions: words, paragraphs, repetition, structure. They mean something by what they write, and they want readers to understand it. The literal meaning is the meaning the author wanted to convey.

In modern conversations we’ve collapsed “meaning” into “identifying what historically happened.” But events don’t carry inherent meaning on their own. Tim’s example was deliberately mundane:

“I don’t know the meaning of what brushing my teeth meant this morning. I don’t know the meaning of why I’m at my in-laws for Thanksgiving.”

Meaning emerges when we craft a story about events, when we see how they connect and interpret their significance. The biblical authors weren’t trying to give us video camera footage. They were giving faithful representations of their history, arranged and shaped to communicate meaning.

“Chronology is not the utmost value. They’re constantly rearranging events. And they don’t even hide it.”

That doesn’t make the texts flawed or deceptive. A different culture represented history differently, and we have to learn to read these texts on their own terms.

Once you see all this, something shifts. The Bible was never designed to hand you a rule for every situation or a set of facts to memorize. It’s a story that shapes wisdom through pattern and repetition, an invitation to slow down, pay attention, and let the text form you over time. That might sound less certain, less immediate, less practical. But I’ve found it’s more honest about what Scripture is and how it works. And when I stopped forcing the Bible to be something it was never meant to be, I finally started hearing what it’s been saying all along.

Common questions

Who is Tim Mackie and what is The Bible Project?

The Bible Project is a nonprofit organization that creates free videos, podcasts, and resources to help people experience the Bible as a unified story leading to Jesus. Tim Mackie is a co-founder who holds a PhD in Hebrew Bible and spent years as a professor before dedicating himself to making academic biblical scholarship accessible to everyone.

Does reading the Bible as literature mean it isn’t true?

No. Recognizing the Bible as sophisticated literature says nothing about whether its claims are true. It means we need to understand how ancient authors communicated before we can grasp what they were claiming, and truth and literary artistry often go hand in hand.

How do I start noticing these patterns myself?

Read larger sections rather than isolated verses, and when you notice a repeated word or phrase, pay attention. Ask where else you’ve seen it, what’s similar, and what’s different. Reading with curiosity rather than hunting for quick applications opens up the text in surprising ways.

What if I was taught to read the Bible differently my whole life?

Many of us were. Shifting your approach doesn’t mean abandoning faith; it often deepens it. Tim’s framework takes Scripture more seriously on its own terms instead of forcing it into categories that don’t fit.