HOW TO READ · 2026-09-12
The day's guides
Tools
Match the Translation to the Job
There is no best translation, only the one suited to what you are about to do with it.
Every translation sits somewhere on a spectrum between two goals that can't both be maximized at once: staying as close as possible to the exact words and word order of the Hebrew or Greek, or rendering the meaning in the most natural English sentence. Move too far toward the first and you get syntax no one actually speaks. Move too far toward the second and you start losing distinctions the original writer built on purpose. Neither end is 'more accurate.' They're accurate to different things.
That's why the question 'which translation is best' is the wrong question. The right question is what you're about to do with the page in front of you. If you're comparing how a word is used across a book, or memorizing a verse you want to hold exactly, you want a translation that keeps the same English word for the same underlying word as consistently as it can — that's the literal end of the spectrum, and it's worth the occasional clunky sentence.
If you're reading a long narrative — a chapter of Kings, a Gospel start to finish — you want the opposite. You want a translation that reads like English, because friction on every third sentence is what makes people quit halfway through Acts. A dynamic translation smooths that out on purpose, at the cost of occasionally deciding an ambiguity for you that the original left open.
Paraphrases are a different tool again, not a lesser one. A paraphrase isn't translating from the source language at all — it's restating an existing English translation in fresher language. That makes it useless for pinning down doctrine, but genuinely useful for the specific problem of a verse you've read so many times it no longer says anything. Read the paraphrase once, then go back to your regular Bible. You'll often see the familiar version differently.
What doesn't work is switching translations mid-task looking for the one that agrees with you. If you're building a memory verse, a Bible study handout, or a sermon, commit to one translation before you start and let it stand even where it's inconvenient. Translation-shopping for the phrasing you like best isn't study — it's just picking the answer you already wanted.
None of this requires owning five Bibles. One literal and one readable translation, used on purpose rather than by habit, covers nearly everything a serious reader needs.
- Keep at least two translations within reach — one literal, one readable.
- Use a word-for-word Bible (ESV, NASB, KJV) for study, memorization, and comparing a specific word.
- Use a thought-for-thought Bible (NIV, CSB, NLT) for long reading sessions and reading aloud.
- Save paraphrases (The Message, The Passion Translation) for when a familiar passage has gone numb — not for settling an argument.
- Pick one translation for a given task and stay with it until the task is done.
4 MIN
Method
How to Read Job Without Trusting the Friends
Forty-two chapters, three friends, and only one speech at the end the book actually asks you to believe.
People misquote Job more than almost any other book, and it's usually not their fault — it's a structural trap built into how the book reads. Long stretches of it sound like wisdom literature: confident, aphoristic, delivered in the same poetic voice as Proverbs. 'The wicked man writhes in pain all his days.' 'God is far greater than we can understand.' Lines like that get lifted out and quoted as if the book is endorsing them. Often it isn't. It's recording someone saying it — and building toward telling you they were wrong to.
Job is not a collection of sayings. It's closer to a transcript of an argument, and the transcript tells you exactly who's talking if you look. Each speech opens with a formula — 'Then Bildad the Shuhite answered and said' — that functions exactly like a name tag before a line of dialogue in a play. Reading with an eye on those tags is the single biggest fix for misreading the book, because it turns forty chapters of undifferentiated poetry into a conversation with three distinct, identifiable voices plus Job's.
The shape underneath is a cycle: Eliphaz speaks, Job answers; Bildad speaks, Job answers; Zophar speaks, Job answers — three rounds, though the third breaks down before Zophar gets his final turn. Each round, the friends' theology gets more rigid and their tone gets sharper, while Job's answers swing between despair and something closer to demand. Watching that escalation is part of what the book is doing; it's not neutral background noise between the 'good parts.'
It helps to know the ending before you're deep in the middle. God's speech in chapters 38–41 never actually answers Job's question about why he suffered — it reframes the whole conversation by asking Job where he was when the foundations of the earth were laid. Reading that speech once, early, as its own unit gives you a fixed point to read the friends' arguments against, instead of wondering the whole time whether any of them are right.
Then comes the verse that reclassifies everything that came before it. In 42:7, God tells Eliphaz plainly: 'You have not spoken of me what is right, as my servant Job has.' That's the book's own verdict on seventy percent of its content. It doesn't cancel the friends' speeches — they're still worth reading closely, because bad theology delivered with total confidence is worth recognizing — but it tells you not to file their lines under 'things the Bible teaches.'
Practice
Read for the Verb
A sentence's mood lives in its verb — command, promise, or plain description — and mixing them up is where most bad application starts.
It's easy to read a whole page in one flat register, as though every sentence in the Bible is issuing the same kind of statement. It isn't. 'David took Bathsheba' is a description of what happened, not an instruction. 'You shall not commit adultery' is a command. 'I will never leave you nor forsake you' is a promise. Three verbs, three completely different jobs, and confusing them is how people end up either treating history as a how-to guide or draining a promise of its force by reading it like a rule.
The fix is a habit, not a system: as you read, notice what kind of thing the verb is doing. Narrative description tells you what happened to someone else, usually so you'll learn something from watching, not so you'll copy the action. A command is aimed straight at you, present tense, no room to negotiate. A promise is God committing to something on his own initiative — your job with a promise is to trust it, not perform it.
This matters most in Paul's letters, where the pattern is often indicative followed by imperative — a statement of fact, then an instruction built on top of it. 'You have been raised with Christ' (a statement) comes before 'set your minds on things above' (a command). Read the command without the statement underneath it and it turns into willpower advice. Read the statement without the command and it never leaves the page. The two verbs are doing different work and need each other.
Proverbs is trickier because its verbs are usually simple present-tense statements — 'a soft answer turns away wrath' — that function like commands without using command grammar. Reading for the verb here means noticing that a proverb is a general pattern, not a promise with your name on it; it describes how things usually go, which is a different kind of true than 'this will happen to you.'
None of this requires knowing Greek or Hebrew grammar. It requires slowing down at the verb the way you'd slow down at a street sign, and asking a plain question before you act on anything you've read: is this describing something, promising something, or telling me to do something? Most misapplied verses fail that one-second check.
- As you read, notice each main verb's mood: is it a command, a promise, or a description?
- Before applying a verse, ask: is this telling me what to do, what will happen, or simply what happened?
Back to today's paper →