HOW TO READ · 2026-09-01
The day's guides
Method
Every Line Says It Twice
Hebrew poetry doesn't rhyme sound — it rhymes thought, and once you see the pattern you can't unsee it.
English poetry trained you to listen for rhyme. Hebrew poetry doesn't rhyme sound — it rhymes ideas. Almost every line in the Psalms and Proverbs comes in two halves, and the second half is doing something specific to the first: restating it, contradicting it, or carrying it one step further. Once you know to look for this, you stop reading verses as single flat statements and start reading them as small arguments.
The simplest version is synonymous parallelism, where the second half says the same thing in different words. "The heavens declare the glory of God; the skies proclaim the work of his hands" (Psalm 19:1). Nothing new is added in the second line — but it isn't wasted, either. The repetition is the point. It's emphasis by doubling, the way you might say something twice to someone who needs to actually hear it.
Then there's antithetic parallelism, common in Proverbs, where the second half says the opposite: "A gentle answer turns away wrath, but a harsh word stirs up anger" (Proverbs 15:1). Here the two halves are a matched pair, light and shadow of the same coin. Reading these well means holding both halves at once — the proverb isn't really about gentle answers or harsh words alone, it's about the fork in the road between them.
The trickiest and most rewarding is synthetic parallelism, where the second half doesn't repeat or oppose — it builds. "The law of the Lord is perfect, reviving the soul" (Psalm 19:7) starts a chain where each line adds a new claim on top of the last. Missing this, people read these verses as a list. Seeing it, you read them as a staircase.
None of this requires Hebrew. It requires slowing down enough to ask, after each line, what the second half is doing to the first — before you decide what the whole verse means. Try it on five verses in a row and write one word in the margin each time: same, opposite, or more. You'll start noticing which mode a whole psalm favors, and that tells you something about its mood before you've even finished it.
This matters most in the places people skim — long strings of proverbs, the middle of a lament psalm — because parallelism is exactly the structure that skimming destroys. Read the two halves as one thought and the verse opens up. Read them as two separate facts and you'll wonder why the Bible repeats itself so much.
It won't work on narrative or law — those aren't built this way. But wherever the text turns to poetry, this one habit — pause at the middle, ask what happened — will do more for your comprehension than any commentary.
- Open to a psalm or a chapter of Proverbs
- Read one verse and split it at the middle
- Ask what the second half does to the first — repeat it, oppose it, or push it further
- Name the move in the margin: same, opposite, or more
- Do this for five verses before you read for meaning
6 MIN
Practice
Say It Back to Him
The oldest use for scripture wasn't study. It was speech — words handed to you so you'd have something to say.
Most of the time you read the Bible about God — his character, his history, his instructions. This is a different move: reading a passage and then handing it back to him as speech. It's old — monks called it lectio divina and broke it into stages — but you don't need the Latin to do it, and you don't need to be a mystic. You just need to stop treating every verse as information and start treating some of them as things you could actually say.
Take a psalm, since psalms were built for this. Read Psalm 23 twice, unhurried. Something will catch — maybe "he restores my soul," maybe "I will fear no evil." Don't move past it looking for the next insight. Instead, flip it from third person to first, from description to prayer. "He restores my soul" becomes "restore my soul" or "thank you for restoring my soul." You're not writing new words. You're redirecting the ones already on the page.
This feels strange at first because it collapses the distance between reading and praying that most people keep carefully separate. Bible reading happens at the desk; prayer happens with eyes closed. But scripture was written, in large part, to give God's people language for exactly this — words for grief they couldn't articulate, words for gratitude too big for spontaneous sentences. Borrowing the phrase and saying it back isn't a workaround for not knowing how to pray. It's how the Psalms were used for three thousand years before anyone thought praying required originality.
It works outside the Psalms too, just less automatically. A line from Isaiah — "do not fear, for I am with you" — can be said back as a request: "be with me, even now." A line from Paul — "I can do all things through him who strengthens me" — can be said back as a confession of need rather than a boast of capacity. The move is always the same: find the phrase, turn the grammar toward God, say it.
Don't do this with every verse — it would drain the practice of its weight. One phrase, once, said slowly, does more than ten verses skimmed for material. And resist the urge to explain what you mean when you say it. The line already means something; you're not required to improve on it, only to mean it.
This is also a good test of whether a passage has actually landed. If you can't find anything in it you'd be willing to say to God directly, you probably read past it too fast the first time. Go back and read it again — not for the takeaway, just for the phrase that's honest enough to say out loud.
Tools
One Word, Underlined
Pick a single word, follow it through a chapter, and the writer's real argument shows up where you weren't looking for it.
Writers repeat words on purpose, and biblical writers more than most — Hebrew and Greek both had synonyms available and chose not to use them. When the same word shows up five times in twenty verses, that's not poor vocabulary. That's the seam of the chapter, and it's usually visible only if you go looking for it with a pencil.
Start with a chapter you think you already know. Read it once straight through, no marking. Then read it again, this time watching for a word that keeps coming back — not the title-page word everyone already talks about, but something smaller. In John 21, it isn't "love" that repeats most tellingly, it's "feed" and "know" — three times each, traded back and forth between Jesus and Peter like a hinge. In Genesis 3, it's "knew" and "naked," bracketing the whole scene. Underline the word every time, and you'll often find it clustered in a way a single reading never showed you.
The payoff isn't the count. It's what changes around the word each time it shows up. Who's speaking it? What's different about the sentence? In John 21 the word "feed" shifts from lambs to sheep across three repetitions — a small escalation easy to miss unless you've already flagged all three instances and can look at them side by side. That kind of pattern is exactly what a single read-through erases, because by the third repetition you've forgotten the first.
This works even without Greek or Hebrew, because most English translations are reasonably consistent about which underlying word they render with which English word — not perfectly, but consistently enough for a first pass. If you want to check your work, a free interlinear online will confirm whether "knew" in verse 3 is the same root as "knew" in verse 9, or whether your translation just happened to reach for the same English word twice.
Pick short chapters to start — a psalm, a parable, one scene from a Gospel. The technique falls apart across long stretches; it's built for a passage small enough to hold in view at once. And resist underlining every repeated word you find — "and" repeats constantly and means nothing. You're looking for the word that feels slightly too frequent for how ordinary it is.
What you end up with isn't a new fact about the passage so much as a new question: why this word, again, here? Sometimes the answer is obvious once you've asked it. Sometimes it just sits there, unresolved, which is its own kind of useful — a flag for the next time you read the same chapter and notice something the underlining didn't catch the first time around.
Back to today's paper →