The Deceiver Gets Deceived: What the Bible Doesn’t Say Out Loud

There are moments in Scripture that are easy to read straight past. I have learnt that the Bible doesn’t stop to explain what it’s doing. It simply tells the story and trusts attentive readers to notice the connections.

Jacob’s story is one of those moments.

✦ ✦ ✦

Jacob: The Deceiver Gets Deceived

If you’re unfamiliar with the story, here’s the context.

Jacob is Isaac’s younger son and the twin brother of Esau. Isaac is old and nearly blind, and he intends to give Esau, the firstborn, the family blessing. In that culture, this blessing wasn’t merely sentimental; it carried inheritance, authority and the covenant promise passed down through Abraham’s family.

With his mother Rebekah’s help, Jacob disguises himself as Esau. He puts on Esau’s clothes, covers his arms with goat skins to imitate Esau’s hairiness, and lies to his blind father. Isaac is deceived, and Jacob walks away with a blessing that wasn’t his.

Fast forward a few chapters.

Jacob has fled from home and fallen in love with his cousin Rachel. He agrees to work seven years for her father, Laban, in exchange for her hand in marriage.

The wedding arrives. In line with the culture, the bride is covered.

Morning comes.

Jacob lifts the veil, and discovers he has married Leah, Rachel’s older sister.

Laban had swapped the sisters under the cover of darkness.

The man who deceived his blind father through disguise has now been deceived through disguise himself.

Genesis never pauses to explain the connection.

There is no narrator saying, “This happened because of what Jacob did.”, nor did it happen for this reason, but it really does echo the initial deception.

The story simply moves on.

If you’re reading quickly, you’ll probably miss it.

If you read slowly, however, something begins to emerge.

The deceiver becomes the deceived.

The Bible Often Teaches Through Patterns

Jacob’s wedding isn’t an isolated incident.

After marrying Leah and Rachel, Jacob spends another twenty years working for Laban. During that time, Laban repeatedly changes his wages and manipulates the agreement between them.

The deceiver spends decades living under deception.

Again, Genesis doesn’t interrupt the story to explain the lesson.

It simply lets the pattern unfold.

That’s one of the remarkable features of biblical storytelling.

Rather than constantly explaining itself, the Bible often invites readers to observe, reflect and connect the dots.

It trusts us to slow down.

✦ ✦ ✦

It’s Not Just Jacob

Once you begin noticing this pattern, you start seeing it throughout Scripture.

Take Lot’s daughters in Genesis 19.

After the destruction of Sodom, Lot and his daughters find themselves isolated in a cave. Scripture makes a note that the daughter believed, their family line has reached a dead end, and the they get their father drunk and sleep with him so they can bear children.

It’s one of the Bible’s most uncomfortable passages, a story born out of fear, desperation and brokenness, perhaps.

Their sons become the fathers of two nations: Moab and Ammon.

At first, it seems like the story simply ends there.

But it doesn’t.

Throughout the Old Testament, the Moabites and Ammonites repeatedly appear as enemies of Israel, these are the descendants of the son’s born to Lot and his daughters.

A story that began in brokenness echoes through generations.

Then something extraordinary happens.

Generations later, a Moabite woman named Ruth leaves everything to follow the God of Israel.

She becomes part of the covenant family.

She becomes the great-grandmother of King David.

Ultimately, she becomes an ancestor of Jesus Christ.

The Bible never pauses to tell us why Ruth’s inclusion matters so deeply.

But when you remember where Moab began, her place in Christ’s genealogy becomes astonishing.

God brings covenant belonging from the very place where shame and hostility first entered the story.

The pattern doesn’t get the final word.

Grace does.

◇

David’s Silence

We see another example in David’s family.

In 2 Samuel 13, David’s son Amnon rapes his half-sister Tamar.

David hears what has happened.

The text tells us he is furious.

But he does nothing.

No justice.

No discipline.

No intervention.

For years, the silence remains.

Eventually Tamar’s brother, Absalom, takes matters into his own hands and kills Amnon.

From there, David’s household begins to unravel.

Absalom flees.

Later he returns and leads a rebellion against his own father.

The family fractures, and tragedy follows David for the remainder of his reign.

Again, Scripture never stops to say, “This happened because David failed to address what came before.”

Instead, the consequences unfold through the narrative itself.

The Bible shows us the progression rather than explaining it.

◇

Reading the Bible Slowly Changes Everything

This is one reason people sometimes speak about “generational patterns” when reading the Old Testament.

The emphasis isn’t on superstition or mystical curses.

It’s that unaddressed sin, injustice and brokenness rarely remain contained.

They ripple through families, communities and generations until someone or rather, God working through someone interrupts the cycle.

That’s exactly what makes Ruth’s story so beautiful.

She doesn’t merely become another character in Israel’s history.

She becomes living evidence that God’s grace is capable of rewriting even the darkest beginnings.

◇

Why This Matters

I think many of us have been trained to read the Bible looking for the moral of the story.

We want the key verse.

The practical application.

The neat conclusion.

Those things certainly matter.

But some of Scripture’s richest truths aren’t presented that way.

They’re woven across chapters.

Across books.

Sometimes across centuries.

The biblical authors expected readers to remember earlier stories, recognise recurring themes and notice echoes that reveal God’s purposes over time.

This isn’t about finding hidden codes or forcing connections that aren’t there.

It’s about reading attentively enough to notice what the text has been doing all along.

The Bible wasn’t written to be skimmed.

It was written to be pondered.

◇

Slow Down. Read the Whole Story.

So next time you open your Bible, resist the urge to rush.

Ask:

• What happened before this?

• Where have I seen this pattern before?

• What promise is God developing here?

• How does this story point forward?

• How might it ultimately point to Christ?

You may discover, as I did with Jacob, that a story you’ve read dozens of times still has something new to say.

Because when you slow down and read the whole story, the Bible begins to reveal just how beautifully interconnected it really is.

◇

Read Scripture This Way for Yourself

This post accompanies the relaunch of my Genesis: Foundations of Faith series here on Wing It With Thought.

If you’d like to start noticing these patterns for yourself, I’ve created a free Bible Reading Guide (PDF)with five simple questions to help you slow down, read more intentionally and discover the connections you may have been missing.

👉 Download your free Bible Reading Guide here: link

info@wingitwiththought.com

© 2025. All rights reserved.

@wingitwiththought

✉️

@wingitwiththought

Join the community