HOW TO READ · 2026-09-04
The day's guides
Method
Read Paul's Mail as Half a Conversation
You are holding one side of a phone call, and the other side left no transcript, but you can still hear it if you listen for the pauses.
Paul's letters are not essays. They are answers, and the questions have been cut out of the tape. That is not a defect — it is how first-century mail worked. Someone in Corinth or Galatia wrote or reported something, and the letter you're holding is the reply. Reading it as a reply, rather than as a freestanding statement of doctrine, changes what you notice.
Start with the seams. Paul often marks a shift with a phrase like 'now concerning the things about which you wrote' (1 Corinthians 7:1) — a flat announcement that a new topic, raised by someone else, is starting. Elsewhere the seam is rougher: a 'but' or 'therefore' that only makes sense if you assume an objection just landed. When Paul writes 'you foolish Galatians, who has bewitched you?' he is not opening a calm argument. He is answering something that happened while he wasn't there.
Some of the other side survives inside the letter itself, in quotation. 1 Corinthians is full of slogans Paul repeats only to correct: 'all things are lawful for me' shows up twice, each time followed by a qualification. Those are not Paul's convictions — they are the Corinthians' talking points, borrowed and turned back on them. Spotting a quoted slogan is one of the fastest ways to hear the other side of the call.
Try Galatians as practice. Paul never quotes his opponents directly, but the shape of his argument tells you what they were saying: that Gentile believers needed circumcision to belong fully. You can reconstruct that claim entirely from what Paul spends four chapters refuting. Do the same with 1 Corinthians 15 — someone was denying a future resurrection, and the whole chapter is built to answer that specific denial, not to give a general lecture on the afterlife.
Hold your reconstruction loosely. You are inferring, not reading a transcript, and it's easy to overreach — turning every 'but' into a conspiracy. The discipline is modest: before you read for application, write one sentence describing what you think prompted this letter. Revise it as you keep reading. A letter answering a real dispute lands differently than a letter treated as a position paper, and most of Paul's mail was written to put out a fire, not to file a brief.
- Read the whole letter once without stopping to look anything up
- Ask what Paul is defending, correcting, or answering
- Mark every 'but,' 'therefore,' and 'now concerning' — these are pivots
- Listen for quoted slogans ('all things are lawful,' 'some say there is no resurrection')
- Write the occasion you've reconstructed in one sentence at the top of the page
12 MIN
Tools
Line Up the Kings and the Prophets
A single opening sentence — in the days of King so-and-so — is a hinge that swings a whole book into the same room as another.
Most of the prophetic books open with a date stamp, and most readers skip right past it. 'The word that Isaiah son of Amoz saw concerning Judah and Jerusalem, in the days of Uzziah, Jotham, Ahaz, and Hezekiah, kings of Judah.' Amos, similarly, preached 'in the days of Uzziah king of Judah and Jeroboam son of Joash king of Israel, two years before the earthquake.' These aren't throwaway lines. They're addresses. The prophet is telling you exactly where to stand.
The problem is that most people read the prophets on their own, detached from the history they're addressing, which makes them sound like they're predicting doom from nowhere. They weren't. Amos preached during a genuine boom — Israel under Jeroboam II was wealthy, expanding, confident — and his fury about crushed poor and rigged courts only lands if you know that. Read 2 Kings 14:23–29 first, then Amos, and the prophecy stops sounding abstract.
The clearest case is Isaiah and 2 Kings side by side during Hezekiah's reign. 2 Kings 18–20 and Isaiah 36–39 tell the exact same events — the Assyrian siege of Jerusalem, Hezekiah's illness, the envoys from Babylon — almost verse for verse in places. Reading them together shows you two angles on one crisis: the court record and the prophet's read on it. That pairing alone is worth the whole exercise.
You don't need a scholar's chronology for this — a single printed timeline of the divided kingdom, cross-referenced with the prophets who preached during each reign, is enough. Keep it as a bookmark. Before starting any prophetic book, spend two minutes finding the king, finding the reign, and reading a chapter or two of the history first.
What changes is not the theology but the weight. A prophet warning a nation getting richer while the poor get poorer, right before Assyria arrives, is not a timeless abstraction — it's someone watching a specific collapse take shape and refusing to look away. Lining up the timeline puts you in the room where that happened.
- Find a one-page timeline of the kings of Israel and Judah
- Read the prophet's opening verse for the king's name (Isaiah 1:1, Amos 1:1, Hosea 1:1)
- Locate that king's reign in 1–2 Kings or Chronicles
Practice
Count the Word the Author Keeps Using
A word repeated nine times in twelve verses is the writer tapping you on the shoulder, not a rough patch in the translation.
Ancient writers didn't have italics, bold text, or headers to flag their main point. What they had was repetition. Say a word often enough in a short space and it functions like underlining — the reader can't miss it. Modern readers, trained by paragraphs with topic sentences, tend to read straight past this. The fix is almost embarrassingly simple: keep a tally.
1 John is the clearest place to try it. Read the whole letter in one sitting — it takes about fifteen minutes — and put a small mark in the margin every time you hit the word 'know.' By the end you'll have somewhere north of thirty marks in five short chapters. That is not incidental. John wrote to a church rattled by people who'd left and cast doubt on their assurance, and his answer, over and over, is: here is how you can know. The repetition is the argument.
Philippians works the same way with 'joy' and 'rejoice' — a letter written from prison, saturated with a word you wouldn't expect, until you notice it's the whole point being made in the choice of word itself. James does it with 'trials' and 'testing' bookending chapter one. None of this requires Greek or a commentary. It requires a pencil and the discipline of reading a short book straight through instead of a chapter at a time.
The tally does two things. First, it surfaces the word — you often don't consciously notice a repetition until you're counting it, and the count itself is a small jolt. Second, it forces a second question past 'what does this word mean': why does the author need to say it this many times, to this specific audience, in this short a space? A word repeated because a congregation needed to hear it thirty times is different from a word that shows up once.
Pick something short for your first try — a letter you can read in one sitting, not a book that takes a week. The tally only works if you can hold the whole thing in view at once. Write the final count at the bottom of the last page when you finish. It becomes a small record of what that book was actually doing, underneath what it was merely saying.
- Pick one short book or letter to read in a single sitting
- Keep a tally mark in the margin each time one word recurs
- Notice which word your eye keeps catching before you go looking for it
Back to today's paper →