HOW TO READ · 2026-09-23
The day's guides
Getting started
Read to the Bottom of the Page
Your daily goal isn't a chapter. It's the page you happen to be on.
Chapters feel like the natural unit for a daily reading, but they're a bad one. They weren't in the original text — a scholar named Stephen Langton added them in the thirteenth century, mostly for the sake of finding your place in a sermon, not for pacing a reader's day. The result is wildly uneven. Some chapters are three verses long. Psalm 119 is a hundred and seventy-six. If your plan says 'a chapter a day,' some days cost you two minutes and others cost you twenty, and you never know which you're signing up for until you open the book.
A page doesn't have that problem. It's roughly the same size every day, regardless of which translation you're using or which book you're in. That evenness is the whole point. A reading habit survives on days that are almost identical to each other — not on days that are heroic. If the unit of progress is honest and small, you can hit it on a bad day, a tired day, a day you almost skip. A chapter can ambush you. A page can't.
There's a second benefit, and it's less obvious: stopping mid-thought trains you to read the Bible as continuous writing instead of a shelf of separate, self-contained units. Letters weren't written in chapter-sized bursts. Neither was most narrative. When you stop at the bottom of a page instead of at a chapter break, you're forced to pick up tomorrow in the middle of something — a sentence Paul hasn't finished, an argument still building, a scene still in motion. That's closer to how the text actually works than the tidy little boxes the chapter numbers suggest.
Mark the page, not the chapter, in whatever you're using to track progress. If you're using a notes app or a sticky note on the nightstand, write the page number and nothing else. It removes a strange, low-grade guilt that chapter-based plans tend to produce — the sense that you've failed if today's chapter took longer than yesterday's. You haven't failed. Genesis 1 and Psalm 119 are not supposed to take the same amount of time, and no plan should pretend otherwise.
This isn't a substitute for eventually reading whole books in a sitting, which is its own kind of good. It's a starting habit — the smallest reliable unit you can commit to on the days you don't feel like committing to anything. Once the habit holds, the page stops mattering as much, because you'll find yourself reading past it anyway.
- Open to where you left off yesterday.
- Read until you reach the bottom of the physical page.
- Stop there, even mid-sentence, even mid-verse.
- Write down the page number, not the chapter.
- Pick it up at that exact spot tomorrow.
3 MIN
Tools
The Heading Isn't Scripture
Someone in a publishing office titled that paragraph. He did not write it, and he was guessing.
Open almost any modern Bible and you'll find bold print scattered through the text: 'The Prodigal Son,' 'Paul's Second Missionary Journey,' 'The Sin of Onan.' These look like part of the Bible. They are not. They have no verse number, no manuscript behind them, and no author who claimed them. They were added by an editorial team, sometime in the last few centuries, to help readers scan a page and find a story quickly — the same instinct that puts a table of contents at the front of a novel.
The trouble is that a heading isn't neutral. 'The Sin of Onan' has already told you what to think about the passage before you've read a word of it. A different publisher might have titled the same paragraph something more descriptive and less judgmental, and a reader working from that Bible would arrive at the text with a completely different starting assumption. Headings are interpretations wearing the typeface of fact. They feel like part of the furniture of Scripture, which makes them easy to trust without noticing you're trusting them.
This isn't a conspiracy — it's just a practical decision editors have to make, and it's worth knowing they made it. Earliest manuscripts had none of this scaffolding: no headings, no verse numbers, often not even spaces between words. All of it — chapters, verses, section titles — was added later by people trying to make an ancient, densely written text easier to navigate. Useful work, but not inspired work, and the distinction matters most exactly where the heading tells you what to conclude before you've read the argument yourself.
Try this once: before you read a passage, cover the heading with your thumb. Read the paragraph cold. Decide for yourself, in a sentence, what it's actually about. Then uncover the heading and compare. Sometimes they'll match. Sometimes you'll find the heading has flattened something — turned a complicated scene into a simple moral, or split two connected paragraphs into unrelated stories because a title had to go somewhere on the page.
None of this means ignore headings entirely. They're genuinely useful for the thing they were built for — flipping through to find the story you're thinking of. Keep using them that way. Just hold them the way you'd hold a stranger's opinion about a book you haven't finished yet: worth a glance, not worth your conclusion.
- Notice the bold words printed above the passage.
Method
A Number Is Usually Just a Number
Forty days, twelve tribes, a hundred and fifty-three fish — before you go looking for a code, ask if someone was just counting.
There's a real temptation, especially once you've been reading for a while, to treat every number in Scripture as a secret waiting to be decoded — seven for perfection, twelve for the tribes or the apostles, forty for testing, and so on down a list you half-remember from somewhere. Some of that instinct is earned. The Bible really does use numbers structurally: seven days of creation, twelve tribes, forty years in the wilderness, three days before the resurrection. These aren't accidents. Writers reused them on purpose, and a reader who never notices the pattern is missing something real.
The trouble starts when the habit of noticing patterns turns into a habit of manufacturing them — when every number you meet gets assigned significance whether or not the text is doing anything with it. John's gospel mentions a hundred and fifty-three fish in one very specific, oddly precise sentence, and centuries of readers have proposed elaborate theories about what the number represents. It's possible the writer meant something by it. It's also entirely possible the disciples counted their catch, the way fishermen do, and the number made it into the account because it was true and someone remembered it.
The useful test is whether the text tells you the number is doing extra work. When Daniel is given 'seventy weeks,' an angel explains what the number means and how to read it — the text flags its own symbolism. That's different from a number that shows up as a plain historical detail: the age of a king when he took the throne, the size of an army, how many years a famine lasted. Most numbers in Scripture are the second kind. They're there because someone was recording what happened, not because they're a puzzle addressed to you specifically.
A workable habit is to hold the interesting cases loosely. If a number seems to be doing something — repeating across stories that otherwise have nothing to do with each other, or explained by the writer as meaningful — note it and sit with it. If it's just a count, let it be a count. Either way, write it down as a question rather than forcing a verdict on the spot. Scripture rewards curiosity about its patterns far more than it rewards a reader determined to find one everywhere he looks.
- When you hit a number, ask first whether it's a literal count.
- Check whether the same number turns up across unrelated stories.
Back to today's paper →