HOW TO READ · 2026-08-25
The day's guides
Getting started
Everyone Quits in Leviticus
The Bible is not arranged in order of difficulty, and nobody warns you about that.
It usually begins in January. Genesis is a page-turner — a garden, a flood, a family that cannot stop lying to itself. Exodus holds up: plagues, a sea, a mountain. Then comes Leviticus, twenty-seven chapters of sacrificial procedure written for men who worked in a tent, and somewhere around the instructions for mildew in houses the plan quietly dies. Worse, the reader concludes that the failure was personal. A lack of discipline, maybe. A lack of hunger for God.
It was neither. The order of the books is not a difficulty curve. This is not one book but a library — sixty-six documents written across roughly a thousand years, gathered by kind and by inherited tradition: law, then history, then poetry, then prophets, then the Gospels. Reading it front to back on a first pass is like reading an encyclopedia alphabetically. Nothing is wrong with the encyclopedia.
Start with Luke. It was written by a careful outsider, a physician, and addressed to a single man named Theophilus, who is told plainly at the top that this is an orderly account so he can know the certainty of what he has been taught. It carries the annunciation, the shepherds, the prodigal son, the thief on the cross, and two strangers walking to Emmaus without recognizing who is walking beside them. It is long enough to feel like a real book and short enough to finish across a week of evenings.
Then read Acts. Same author, second volume, the story simply continuing — which is why so many people who put down a Gospel with a sense of an ending find Acts startling. After that, Genesis, which will read differently now that you know what it was building toward. Then the Psalms, a few at a time, in no hurry at all.
As for Leviticus: come back to it with Hebrews open beside it. Blood, priest, altar, the one day a year when a man went behind the curtain — Hebrews is an extended argument about those chapters, and it cannot really be read without them. Taken in that order, Leviticus stops being an obstacle and becomes the thing being answered. Slow, strange, and suddenly load-bearing.
And when a reading plan dies, abandon the plan, not the book. Keep several bookmarks. A Bible being read in three places at once is still being read.
- Start with Luke, not Genesis.
- Read Acts next — same author, second volume.
- Then Genesis, then a psalm a day.
- Keep a bookmark in every book you're mid-way through.
- Save Leviticus for later, with Hebrews open beside it.
3 MIN
Practice
The Hand Is Slower Than the Eye
Your eye takes a paragraph in ten seconds; your hand takes six minutes, and the six minutes are the entire point.
Reading is fast, and speed is the problem. Your eye can take a paragraph of Paul in about ten seconds and hand you a rough impression of it — something about humility, something about the cross. Your hand needs six minutes for the same paragraph, and every word has to pass through you at roughly the speed of speech. That gap between ten seconds and six minutes is where this practice lives.
Pick something short. Philippians 2:5–11. Psalm 23. Colossians 1:15–20. Use a cheap notebook and whatever pen is nearest. Write it out word for word, and leave the verse numbers off. Do not letter it, do not illuminate it, do not buy special supplies. This is not calligraphy and the goal is not a beautiful page — it is a slow one.
What you notice first is repetition. Copying Colossians, your hand writes in him, and then in him again, and then in him a third time, and by the fourth you understand that Paul is not varying his phrasing because he is not trying to. The eye skims that as style. The hand experiences it as insistence.
Then you notice the joints — therefore, but, so that, because. These small words carry the whole argument and are precisely the ones a fast reader slides over. Written by hand, a therefore forces the obvious question: therefore what, following from what? You can't write it without briefly wondering what it is doing there.
Dropping the verse numbers matters more than it sounds. They aren't original to the text; they were added in the 1550s, and they are excellent for finding a passage and quietly terrible for reading one. Without them, the page is what it always was — sentences and paragraphs. You will find sentences that run straight through a number you would have stopped at, and arguments that were never meant to be quoted in slices.
The practice is old, and it was never decorative. Deuteronomy instructs a king, upon taking the throne, to write out a copy of the law for himself in his own hand — not to commission one, to make one. He had scribes. He had a treasury. The command is not about archiving. It assumes something plain: a man who has written a thing out slowly is harder pressed to be careless with it.
Ten minutes, twice a week, is enough. Read your copy aloud when it's done, then keep the notebook. After a year you will have a small anthology in your own handwriting of the passages that mattered enough to write down.
Method
The Bible Quotes People It Disagrees With
Scripture records what liars and fools and grieving men actually said, and it does not always stop to correct them on the spot.
Job's friends talk for about thirty chapters. They are eloquent, orderly, and endlessly quotable. Suffering is punishment, they explain. Examine yourself. God does not afflict the innocent. Then, near the end of the book, God speaks to Eliphaz and says: you have not spoken of me what is right. All of it is in the Bible, faithfully preserved, and most of it is wrong.
This is not a flaw in the text. Scripture is a truthful record, and a truthful record includes untrue speeches. The serpent in Genesis 3 opens by misquoting God, subtly, in a way you can only catch by turning back two pages. Job's wife says, curse God and die. The devil, tempting Jesus in the wilderness, quotes Psalm 91 and quotes it correctly. The report is reliable. The speaker is not.
So the habit is small and worth building: before you take a sentence as instruction, find out who is saying it, and whether the book agrees. Three questions, quick enough to become automatic. Who is speaking? To whom, in what situation? And does the surrounding text endorse this, merely report it, or answer it back?
Sometimes the answer sits in the next line. Sometimes it is a very long way off. The verdict on Job's friends arrives roughly forty chapters after their first speech. Ecclesiastes spends most of its length arguing that everything is vapor and that effort under the sun comes to nothing, and only at the close does it step back from the whole performance. This is the strongest practical case for reading entire books rather than collecting verses: in a well-made book, the judgment tends to live at the end.
One caution, because this tool can be misused. It is not a filter for removing the parts you would rather not have. The test is whether the text itself renders a verdict, not whether you would like it to. Paul writing to a struggling church in Corinth is not Eliphaz talking over a grieving man on an ash heap, and treating them the same is not careful reading, it is preference wearing a method's clothes. Where you genuinely cannot tell, mark it and leave the question open. An honest question kept open is worth more than a tidy answer arrived at by taste.
Try this once, concretely. Open Job and go through it with a pencil, writing the speaker's initial in the margin wherever a new speech begins — E for Eliphaz, B for Bildad, Z for Zophar, J for Job. It takes ten minutes and the book changes character entirely. What looked like a heap of solemn maxims turns out to be a transcript of an argument, with a court and a ruling and a man who was right to keep protesting.
Back to today's paper →