HOW TO READ · 2026-10-10
The day's guides
Method
Read the Commands as Answers
Every instruction in the Bible was written to someone who had just been given a reason, so look for the reason first.
Most of us meet biblical commands as a list of demands. Be patient. Do not worry. Love your enemies. Read that way, the Bible can sound like a supervisor with a long memo, and it is easy to tire of it or to feel quietly graded.
But the writers rarely issue an instruction bare. They tend to attach it to something that has already happened or is already true. The Ten Commandments open with "I am the Lord your God, who brought you out of the land of Egypt." The command comes after the rescue, not before it. Paul's long ethical sections in Romans and Ephesians begin with "therefore," which is a sign that the instructions are standing on something he has just spent chapters establishing.
So try a small habit. When you hit a command, stop and hunt for its reason. Often it is in the same sentence: "Do not be anxious about tomorrow, for tomorrow will be anxious for itself." Sometimes it sits a few verses back, or a chapter back, or at the start of the book. Write it in the margin next to the command, short, in your own words. "Don't fear: he is with you." "Forgive: you were forgiven."
You will find that the reasons are more varied than you expected. Some point to what God has done, some to what God is like, some to how things will end, and a few to plain common sense, as in Proverbs. Each kind changes how the command sounds. An order resting on a rescue reads as an invitation to live in the new situation. An order resting on a warning reads differently, and it is worth noticing which you are holding.
Occasionally you will not find a reason, and that is useful too. Mark those commands with a small dot and come back to them. Sometimes a cross-reference or a note supplies what the text itself leaves out, and sometimes the reason is simply assumed by the first audience and has to be reconstructed.
Do this for a week and the margins of your Bible will start to show a pattern. The commands are rarely free-floating. They are answers to a situation, written for people who were told who they were before they were told what to do. That is a quieter way to read, and it is truer to the page.
- Pick a command in a passage you are reading, such as "do not be afraid" or "forgive."
- Look in the surrounding sentences for the because, since, or for that follows or precedes it.
- Write the reason in the margin in your own words, beside the command.
- Ask what the reader would have had to believe for the command to make sense.
10 MIN
Tools
A Pencil Index at the Back
The blank pages at the end of your Bible are there for the one reference tool you will actually use: your own.
Printed Bibles often end with a few empty pages, and most of us leave them empty. They are better used. A short index in your own hand, built over months, will do something no published concordance can: it will track the questions you are actually asking.
Start with a single heading. Choose something you have noticed coming up, not something you think you ought to study. "Waiting" is a good one. "Bread" is another. "Who is the stranger?" works too, because the headings do not have to be single words. Write it at the top of a line, leave a few lines beneath, and put in the first reference you can think of.
From then on, whenever a passage touches that theme, add its reference. Do not copy the verse. A reference and perhaps three words of reminder are enough: "Ps 27:14, wait, be strong." The point is to be able to find your way back, not to build a second Bible.
The index has a way of teaching you things. After a few months you will see that your Psalm references cluster in certain books and that your "Waiting" list leans heavily on the prophets. You will notice that two passages you had filed under different headings keep appearing together. That is the beginning of real study, and you reached it without a course.
Keep the system loose. Four or five headings is plenty, and you can abandon one that goes nowhere. Resist the urge to alphabetize or tidy. A crossed-out heading is evidence that you tried something and learned it was the wrong question.
Once a month, take one heading and read down its list in order, passage after passage, in one sitting. You will be reading a short, personal anthology that you assembled over weeks without planning to. It tends to be more instructive than any list you could have been handed, because every entry on it once caught your attention for a reason.
- Turn to the blank pages or the last endpaper of your Bible.
- Write a heading for a topic you keep returning to, such as "Waiting" or "Mercy."
- Under it, add the reference each time you meet a passage that bears on it.
- Reread one heading's list in full once a month.
Getting started
Read the First Page Twice
When you open a new book of the Bible, the opening lines carry more instruction than they appear to, and they reward a second pass.
Books begin on purpose. The writers of the Bible, like most good writers, put things at the opening that tell you how to read what follows, and the reader who hurries through the first page to reach the content has often skipped the instructions.
Take John, which opens with "In the beginning was the Word." Those lines do not just set a scene. They introduce the vocabulary of light, life, and witness that the whole Gospel will keep using. Take Hebrews, which opens with a single long sentence about God speaking in many ways and finally by a Son. The rest of the letter is largely an unpacking of that sentence. Even a modest opening like Ruth's, "In the days when the judges ruled," places the story in a hard and lawless time, and the quiet faithfulness that follows reads as a contrast.
So give a new book two readings of its first page. On the first, read for the plain facts. Who is writing or speaking? To whom? What has happened, or what is going wrong? Jot those answers in a line or two. You are not trying to be clever, only to gather what the author handed over.
On the second reading, go slower and look for words that seem to be doing extra work. A word that appears twice in the first few verses, a phrase that sounds like a title, a name given an unusual description: these are often the author's way of announcing what the book is about. Mark two or three and leave them alone.
Then read the book, and when you reach the end, turn back to those marks. Many readers are surprised by how much has been resolved or deepened. A word that seemed ornamental on page one turns out to have been carrying a load all along.
This habit is cheap. It adds ten minutes to the beginning of a project and nothing after. But it changes the way you walk into a book. You arrive with a few questions already in hand, and you read the rest as someone who was told, politely, what to watch for.
- Choose a book you have not read before and read only its first page or first chapter.
- Note who is speaking, who is addressed, and what is named as the problem or the occasion.
- Read the same opening again, slower, and mark any word or phrase that seems to be setting a theme.
Back to today's paper →