Scripture deserves a teacher, not a search box

There has never been a better time to look something up about the Bible. That turns out not to have been the problem.

Every concordance, every lexicon, every commentary out of copyright, a hundred translations set side by side. All of it free, all of it a few seconds away. By any reasonable measure the access problem is solved. And yet most of the people we talk to read less confidently than the abundance would predict, and can say less about what they read.

That is not a contradiction. Access was never the bottleneck. Understanding was.

A search box is a very good machine for one job: you know what you are missing, and it fetches it. Type a reference, get the verse. Type a Hebrew word, get its range of meaning. The transaction is clean because the shape of your ignorance is already known to you. But most of what stands between a person and a book like Isaiah is not a fact they could name. It is a way of reading nobody has shown them. You cannot search for that, because you do not know what to type.

You search the Scriptures, because you think that in them you have eternal life; and these are they which testify about me.

It is a striking sentence to sit with in the age of the search box. The people being addressed there are not lazy readers. They are searching: combing, examining, doing the work. The trouble is that searching and understanding are different activities, and the first does not turn into the second on its own.

What closes that gap is almost always a person. Somebody who has read the book before, who asks what you noticed, who lets you be wrong out loud and then points back at the page instead of at you. Nearly everyone who reads Scripture well got there partly this way. Every tradition that has lasted has known it and built for it: the catechist, the midweek study, the older Christian and the younger one at a kitchen table with two mugs going cold.

That relationship is expensive. It does not scale, it never has, and the shortage falls hardest on the people who need it most. The thirty-year-old who has never finished a book of the Bible and is embarrassed to say so. The shift worker whose church meets while she is at work. The new believer with five real questions and nobody to ask them at eleven at night.

Beginning from Moses and from all the prophets, he explained to them in all the Scriptures the things concerning himself.

The road to Emmaus is the picture we keep returning to. Two people walking, confused, and the teaching happens at their pace, along their road, starting from their confusion. He does not hand them a summary. He takes them through the texts. The walking is not incidental to the lesson; it is the form the lesson takes.

Most software built for the Bible lately has gone the other way. Ask it anything and it answers at once, at length, in a voice of complete confidence, and then the exchange is over. It feels like help. It produces true sentences a good deal of the time. But the transaction is upside down: the machine does the thinking and hands you the result, which is exactly the part you needed to do yourself. You come away with a paragraph you could not reconstruct an hour later. And when it is wrong (a verse that does not exist, a contested reading served up as the plain sense), it is wrong in the same warm, certain voice it uses when it is right.

We think the answer is not a better search box but a different posture. A tutor asks before it explains. It makes you commit to a reading, so there is something on the table worth testing. It supplies context at the moment context unlocks something, rather than as a lecture up front. It asks you to say the thing back in your own words, which is the moment you discover whether you actually have it. And it brings the passage back a week later, when you are beginning to lose it, because that is when returning does the most good.

None of that is a novel invention. It is what teachers have always done. What is new is only that a machine can now carry a narrow slice of it, patiently, at eleven at night, for somebody who does not want to admit in a small group that they have never read Leviticus.

A narrow slice. This part matters enough to be blunt about: a tutor is not a pastor, and a study tool is not a church. It cannot pray with you, sit with you in a hospital corridor, know your life, or tell you the hard thing a friend would tell you. If a piece of software ever leaves you feeling you need other Christians less, put it down. The whole purpose of understanding a text better is to carry the understanding back to people.

but his delight is in Yahweh's law. On his law he meditates day and night.

Delight, and day and night. That is not the vocabulary of efficiency. It is the vocabulary of a long habit: something returned to, unhurried, for years. No software can manufacture that. At best it can remove a few of the reasons people give up in the first month: the shapelessness, the embarrassment, the silence where a question should have been answered.

So this is what we are building, and what we are not. Not an oracle. Not a pastor. Not a faster way to get an answer about the Bible. There are plenty of those already, and the speed is precisely the problem. A teacher: patient, specific, willing to say it does not know, and stubborn about making you do the reading yourself.

The book is worth that. It has outlived every technology that promised to simplify it, and it will outlive this one. The only question worth asking is whether the tools we build in the meantime help people read it, or merely help them stop asking.