I'll never forget the first time I was exposed to a Strong's Exhaustive Concordance. I was at a high school Bible study in which the Bible study leader decided it would be a good idea to teach us how to use a concordance. First he showed us how to look up a word in the concordance to find all its occurrences, and then he showed us the little numbers to the right of each occurrence. These, he explained, represented the original Greek or Hebrew word being translated. To find out more about that word, you simply turned to the back and looked up the number in the included Greek or Hebrew dictionary. He illustrated the usefulness of this practice with a few standard examples: the alternating use of agapao and phileo in John 21, the wordplay between adam (man, human) and adamah (earth, ground) in Genesis 2, and the semantic range of ruach, which can be translated as "spirit," "breath," or "wind."
At the time, this process of study seemed almost magical. What was I to conclude from all this but that if you knew the Greek and Hebrew, you could unlock a whole new level of meaning and know what the Bible "really says"? Fortunately, I didn't go out and buy a $50 Strong's Concordance and begin looking for secret knowledge. Instead, I invested in a $10 NIV and benefited from reading an English translation I could easily understand.
Today, I help develop software that makes it incredibly easy for those who don't know Greek and Hebrew to examine the original words behind their English translation, and I'm proud of that. The more people are equipped to examine the text of Scripture for themselves, the less susceptible they will be to the influences of the latest theological fads. But there are also dangers inherent in giving people powerful tools without also training them in how to use them.
That's why I cringe whenever I see Bible programs advertise that they will let you "unlock" the Greek and Hebrew without actually "knowing" the languages. For example, I once saw a demo of a Bible program in which the demonstrator (a college-age student who clearly had no seminary training) made much of the fact that in Matthew 28:19, the word usually translated "Go" is not actually an imperative, but a participle. The only imperative in that verse is "make disciples." Now, while that's certainly an interesting grammatical point to consider, this young man went so far as to say, "See, we've been translating and preaching this verse wrong all these years!"
I couldn't help but marvel at the hubris. By making much of a relatively minor grammatical distinction, this young man was willing to dismiss about a gazillion English translations which understand the participle in question to have imperatival force. Apparently this young man didn't realize that participles can sometimes function as imperatives.
Therein lies the problem with the promise that Bible software—any Bible software, including Accordance—will enable you to unlock the Greek and Hebrew without actually knowing it. I call this effort to find secret knowledge through the use of Strong's numbers Strongnosticism. I hope in upcoming posts to combat Strongnosticism by showing how you can effectively use Strong's numbered Bibles in Accordance to gain important insights, and by discussing how far such insights should be taken.
For now, I'll leave you with the number one way to avoid slipping into Strongnosticism:
Realize that Greek and Hebrew are merely languages, and think about how you use language every day.
To see how this works, ask yourself whether you "parse" most of the things people say to you. Do you ask yourself why they used this word and not that word? Do you ponder the verb tense they chose or puzzle over why they used a participle or infinitive? What if they break some grammatical rule like splitting an infinitive or ending a sentence with a preposition? Do you ponder what they meant by that, or do you just chalk it up to colloquial expression? When someone says something confusing or unclear, we do sometimes resort to this kind of parsing, but most of the time, we know what they are trying to get at and we don't get bogged down in the grammatical details. I'm convinced that if most interpreters kept that simple reality in mind, their interpretation of Scripture would be vastly improved, and they would avoid the temptation toward Strongnosticism.
Greetings, David! What you wrestle with with regard to Strong's is one of the things that the late author of the excellent syllabus DO IT YOURSELF HEBREW AND GREEK (Zondervan) deals with therein -- one of the first, in fact. How do you teach people to use the "English language tools" from Strong's upward without making them think they know more than they really do? Now I've learned Biblical and Classical Hebrew (accents -- after Suzanne Haik-Vantoura's deciphering key -- and all) well enough to use an all-Hebrew Bible created for Hebrew-Christian readers (the Letteris Edition OT and the Franz Delitzsch NT) in regular Bible study. [I also know just enough Greek to be dangerous. :) ] Permit me to speak from that perspective for a moment. On the one hand, there are some genuine pitfalls in the original languages which don't exist in English; for example, Biblical Hebrew in particular is notoriously context-driven in meaning. On the other -- and here's the real problem -- some would have you believe that Strong's, or their own low-end language tool, is sufficient to help a student grasp what those pitfalls are. One really has to study the languages *as languages* in order to grasp, piece by piece, their thought-worlds. And in that, I still count myself a student -- not an "expert" -- and plan to do so always. Humility is hard-won, but it goes a long way toward understanding *anything* properly!
This is for William Volm. The Greek NT gets much of its theological vocabulary from the Greek Septuagint version (LXX) of the OT. Edward Goodrick's DO IT YOURSELF HEBREW AND GREEK mentions sources that point out the cross-references. One venerable work is the HATCH-REDPATH CONCORDANCE. A recent and helpful work (designed to be a complementary one, in fact) is the HEBREW/ARAMAIC INDEX TO THE SEPTUAGINT by Takamitsu Muraoka (Baker). Another great source that often gives Hebrew and Aramaic parallels to NT Greek words is Walter Bauer's A GREEK-ENGLISH LEXICON OF THE NEW TESTAMENT AND EARLY CHRISTIAN LITERATURE (Chicago University Press). A good, SCHOLARLY Classical Hebrew NT version (like that of Delitzsch or Salkinson-Ginsburg) can give many valuable clues. You will need to at least know how to spell the appropriate Hebrew, Aramaic and Greek words to use these sources well, but it is not all that hard to learn how.
Great new word, David -- Strongnosticism! I love it....and I heartily concur with what you're getting at.
I appreciate your observation! What I wish for, as a person who is learning Greek (and maybe someday) Hebrew, is better and more accessible (esp. to the lay person) linguistic tools so that these issues can be attended as they come up. Having a good English grammar would help since many, many people who are being exposed to these powerful tools may not even know what a participle is!
Having said that, the reverse of your stated malady is having heated linguistic arguments about Bible words based exclusively on English grammar! I will usually chime in on the Greek that underlies simply to point out that the issues are far more nuanced and that some grace has to be given!
The biggest advantage to your and similar software is that we have the Greek words (mostly) fully parsed so that I have backup for my weak conjugation skills. But understanding verb agreements goes a long way to clarifying many texts! In this way it is superior to either the concordance or an interlinear text.
I appreciate these comments but I wonder if 'merely languages' is doing full justice to verbal inspiration. The old Newberry Bible made a big issue of the precision with which the Hebrew and Greek languages were used in the OT and NT.
God's choice of Hebrew and Greek I suggest was not just a happy coincidence but part of a particular choice which has included culture, idiom and even climate as a unique way of expressing his mind. In the way God chose Isaiah or Peter to perfectly express his mind in language which although theirs was also from the mouth of God, so God has chosen Hebrew and Greek as the best vehicles for his accommodation to communication with human beings. This is not to say we need Hebrew and Greek to know the mind of God but simply that Hebrew and Greek are not 'merely languages'.
I agree with Ron in that, if the Bible was inspired by the Holy Spirit, it will stand up to close inspection. Nevertheless, I would treat different portions of the Bible differently. To illustrate, while I might not parse the word choice of my friends, I feel that I can consider carefully the word choices of, say, O Henry, Ben Bernanke, or Justice John Roberts, because I can assume that each has chosen his words with care (albeit for different reasons). Likewise, the reader of the Bible needs to balance whether he is parsing the casual words of Paul (or Tertius) or the precise words of the Holy Spirit, and whether to consider carefully the word choices in Genesis 2, Exodus 20,Samuel and Kings, or the first 9 chapter of 1 Chronicles.
That is, on the one hand I might not always practice minute exegesis of the historical portions of the Bible, but on the other hand I can look carefully at the way the Holy Spirit chose to communicate the Law, Jesus' teaching, Paul's doctrine, and certain other portions.
Dave, I certainly agree that the Bible can stand up to close inspection, and I sure don't intend to discourage "minute exegesis" of the text. However, there's a sense in which many exegetes end up "straining at gnats and swallowing camels," because they fail to step back from the minutia to consider the main point the human and divine authors are making. If we fail to keep the main thing the main thing, allowing context to be the final arbiter of what the minutia actually add up to, we can easily spin off from the minutia into all kinds of erroneous interpretations. That's what I mean when I say that we need to think about how we use language every day.
Comments in this Category
All Comments