HOW TO READ · 2026-09-17
The day's guides
Method
What the Parable Is Actually About
A parable makes one point, not a treasure map of hidden meanings — learn to look for the one thing that would have surprised the room.
For centuries, readers treated parables like allegories with a key: the father is God, the older son is the Pharisees, the ring is grace, the fatted calf is the eucharist. Some of that isn't wrong exactly, but it isn't how the stories were built, and chasing every detail for a hidden meaning usually buries the actual point under a pile of symbolism the story was never carrying.
A parable is closer to a joke than an allegory. Jokes work because they set up an expectation and then break it at exactly the right moment — that's where the meaning lives, in the twist, not in every prop on stage. The Prodigal Son isn't really about a ring or a robe; it's about a father who runs, which no honored Middle Eastern patriarch would do, and a full house before the son has finished his apology. That's the surprise. That's the point.
So before you reach for meaning, reach for the room. Who's listening to Jesus tell this story — tax collectors, Pharisees, disciples arguing about who's greatest? What would they assume the story was going to do, based on stories they already knew? A parable about a lost sheep sounds like a story about carelessness until you notice the shepherd leaves ninety-nine sheep unguarded to chase one. First-century farmers would have winced. That wince is the sermon.
Once you've found the twist, resist the urge to keep going. Most parables carry one central comparison, and forcing every detail to mean something usually distorts the story rather than illuminating it. The unjust judge isn't a coded reference to God's character — the story works by contrast, not resemblance: if even a corrupt judge relents under pressure, how much more will a good one respond to persistent prayer. Not every character is a stand-in. Some details are just how stories get told.
Try this with a parable you think you already understand — the workers in the vineyard, the talents, the wedding banquet. Read it cold, picture the room, and ask only one question: where does this story do something no one in that room would have expected? That's usually where you'll find you didn't understand it as well as you thought.
- Read the parable once for the plain story, no symbols yet
- Ask who's listening and what they'd expect the ending to be
- Find the place where the story breaks that expectation
- Name the single comparison being made, not five
- Resist assigning a meaning to every character or object
6 MIN
Tools
The Notes Are Not the Text
Footnotes are a scholar's best guess at eye level with you, not a second layer of scripture — read them like a smart friend's opinion, not a verdict.
Study Bibles are useful enough that it's easy to forget the notes aren't inspired — they're one well-read person's judgment call, printed in smaller type at the bottom of an inspired page, and the two shouldn't be read with the same authority. The italics don't mean the sentence above is more certain than the text; often it means the opposite, that this is the place scholars are still arguing.
Try reading the verse cold first. Let it say what it says before anyone tells you what it probably means. Then drop down to the note and ask what it's actually doing — is it giving you a historical fact (this coin was worth a day's wage), a cross-reference (this phrase echoes a psalm), or an interpretation (many scholars believe this refers to)? Those are three different kinds of help, and only the first two are close to settled.
Watch for the hedges. "Possibly," "may refer to," "some understand this as" — these words are the editor being honest with you, not being vague for no reason. A note that hedges is telling you the underlying question is open, which means you're allowed to have a view of your own after doing some thinking, not just accept the paragraph as the last word.
It helps to check a second study Bible occasionally, especially on a verse that seems to be carrying real weight in an argument. Different traditions — Reformed, Catholic, Orthodox, Wesleyan — will sometimes gloss the same verse differently, and seeing two competent, careful people disagree is a fast way to notice where a note was quietly making a theological choice rather than just reporting a fact.
None of this is a reason to distrust the notes wholesale — a good study Bible saves you years of specialized reading. It's a reason to keep the hierarchy straight: text first, note second, your own marginal question third, and never let the third one go unwritten just because the second one sounded confident.
- Read the verse first, without glancing down at the note
- Read the note second and ask what evidence it's citing
- Notice hedge words like "possibly" or "some scholars" — that's a live question, not a settled one
Getting started
Read It Once, Badly, Before You Read It Well
Give yourself permission for one fast, sloppy pass through the whole Bible before you slow down — the map matters more than the mileage on a first trip.
Most people who quit reading the Bible quit because they tried to study it before they'd ever simply read it — stopping every few verses to look something up, feeling guilty for not absorbing everything, treating a first pass through Leviticus like a final exam. There's a different way in: read the whole thing once, on purpose, badly.
Badly means fast, forward-moving, and unconcerned with catching everything. You're not annotating. You're not cross-referencing. You're getting the shape of the thing — that there's a garden at the start and a city at the end, that exile is the hinge the whole Old Testament turns on, that Paul's letters are responses to problems you only half-understand yet, and that's fine. A first read is a map, not a survey. You're finding out where the mountains are before you hike any of them.
Set a real deadline, because an open-ended plan for reading the whole Bible has no natural stopping point and will drift. A summer works. So does the length of a school term. The deadline isn't about performance — it's about giving yourself a reason to keep moving instead of stalling out in Numbers for six weeks.
When you hit genealogies, census lists, or the tabernacle's dimensions for the third time, skim them. You're allowed. The point of this pass isn't mastery, and treating a list of names with the same weight as the Sermon on the Mount will just convince you the whole book reads like a phone directory.
Keep exactly one list going the whole way through — verses, questions, strange details — and don't stop to chase any of them down yet. Just write the reference and move on. That list becomes the itinerary for your second, slower trip.
When you finish, and you will finish faster than you expect, start over from Genesis, this time slowly, a book at a time, with all the tools — commentaries, cross-references, a notebook — you were told to skip the first time through. You'll read it differently now, because you already know where the story is going.
- Pick a timeframe — a summer, three months — and don't extend it
- Read for story and shape, skipping the urge to stop and study
- Skim genealogies and lists rather than parsing every name
Back to today's paper →