 |
| Christopher M. Hays |
“aha” moments: biblical scholars tell their stories (7): Christopher M. Hays
http://www.patheos.com/blogs/peterenns/2014/07/aha-moments-biblical-scholars-tell-their-stories-7-christopher-m-hays/
by Peter Enns
July 11, 2014
Today’s “aha” moments is by Christopher M. Hays (DPhil, New Testament Studies, University of Oxford). After completing his degree, Hays was a British Academy Postdoctoral Fellow for 3 years, and is now teaching at
Fundación Universitaria Seminario Bíblico de Colombia.
---
Graduate students are willing and eager to do miserably boring jobs for woeful wages. Professors, who also do a lot of boring work for only slightly less woeful wages, are willing and eager to give their grad students the worst of that drudge-work. (It’s called “mentoring.”)
That’s how, in 2003, I found myself naively happy to be cataloguing “textual variants” for 2 Peter, helping my boss and mentor,
Gene Green, on his then-forthcoming
commentary for Baker. (Not all ancient copies of biblical manuscripts are identical, so scholars have to decide which “variants” are likely to be older, and therefore more likely original.)
Now most textual variants are tremendously insignificant, which is why, when I found a slightly-less-insignificant one in 2 Peter 2:15, I felt a rush of nerd adrenaline.
2 Peter 2:15 mentions false teachers who have gone astray like Balaam, the prophet from Numbers 22:5 who was hired by King Balak to curse the Israelites. Some manuscripts of 2 Peter 2:15 called him “Balaam son of Beor” (which is what Numbers 22:5 calls him); other manuscripts of 2 Peter 2:15 call him “Balaam of Bosor,” which, as we’ll see in a moment, makes no sense at all.
“Beor” is a person’s name; it was the name of Balaam’s dad (his patronymic). Bosor is the name of a city (a.k.a. Bosorra). The problem is: the older, better manuscripts called him “Balaam of Bosor,” but Balaam wasn’t from anywhere near Bosor, which is in the land of Gilead. According to Numbers 22:5, Balaam was from “Pethor, which is on the Euphrates, in the land of Amaw.”
Later copyists, therefore, changed “Bosor” to “Beor” so that the text makes more sense.
So I asked myself, why did the author of 2 Peter call him “Balaam of Bosor”? I poked around, and then an answer suggested itself.
If you are a normal person, reading text criticism is about as much fun as un-sedated dental surgery, but I’m asking you nicely to hang with the next couple of paragraphs to see how I came to understand that the author of 2 Peter was himself confused about a historical detail.
The basic problem is that there was another guy in the Old Testament whose name sounded a lot like Balaam’s. Instead of being “Balaam son of Beor,” his name was “Bela son of Beor.”
The name Beor actually occurs in a genealogy (a king-list) that is copied three times in the Old Testament (Gen 36.33; 1 Cor 1.44; Job 42:17c [LXX only]). That genealogy mentions a king whose name was “Bela son of Beor,” who in turn was succeeded by aguy from the city of Bosorra (Bosor). And in one version of the genealogy (the LXX of Job 42), the king “Bela son of Beor” is actually called “Balak son of Beor”.
Now the King Balak son of Beor in this genealogy is a different King Balak (of Moab) than the one that hired Balaam son of Beor in Numbers. But you can see how people might get confused: same patronymic, similar sounding first names. You’re probably confused already! And so were some ancient Jews.
In fact, when you read the genealogy in ancient Aramaic translations of the Old Testament (the “targums”), which were already popular at the time of Jesus, you can see that they sometimes actually changed the name of King Bela/Balak son of Beor toBalaam son of Beor.
Since there was already a history of confusion over the Balaams and Balaks and Beors in the Numbers story and the genealogy, it seemed really understandable that the author of 2 Peter would be caught up in the flow and reproduce the same mistake.
What more natural way is there to explain the fact that he used “Bosor” instead of “Beor” than to say that he mixed up the patronymic of one person in the genealogy with the similar sounding hometown of the next person in the genealogy?
Yeah, yeah; I know it’s dull stuff. But I was fascinated, and so Prof. Green (who really was and is a brilliant mentor to me) fanned the flame, and helped me produce my first scholarly publication (an insignificant note in Filologia Neotestamentaria; if you are an insomniac, you can look it up
here).
It was at that point that my friends started to rain on my parade.
One of my buddies asked, “So, don’t you believe in inerrancy anymore?” I was taken aback. I was pretty sure I still believed in inerrancy. But he explained, no, no I didn’t; after all, I had just said that Peter (no scare-quotes at this point in my life) made a mistake.
(BTW, this totally messes up the silly idea that Scripture is “inerrant in the original autographs”; we of course will never have the original autographs, but in 2 Peter 2:15, for example, the most-original reading we have is the more problematic one; the later manuscripts in 2 Peter 2:15 are the ones that are without error!)
Then came my “Aha” moment: I realized that I thought Peter had made an historical mistake, and I realized that it didn’t make me trust themessage of Scripture less. The agenda of 2 Peter (to say that false prophets in his day were doing bad things, like Balaam did) is not remotely altered by the author’s snafu about Balaam’s surname.
In this case (though not in every case) the veracity of the theological message is in no way dependent upon the historical detail of the Old Testament illustration used to underscore the point. So I saw no reason to doubt 2 Peter’s criticism of the false teachers because of this tiny lacuna in his historical knowledge.
But for a lot of my friends, that wouldn’t be the case. In popular evangelical discourse (such as the Chicago Statement on Biblical Inerrancy), the historical and scientific inerrancy of Scripture is adduced as the reason one can trust Scripture’s message about God’s redemption in Christ.
So, if there are historical or scientific errors in the Bible, then the theological veracity of the Bible’s message is also jeopardized.
The conservatives have a point here; we can’t just pretend that historicity is entirely irrelevant to the Bible. The live debate among conservative and liberal Christian scholars has to do with how much historicity the Bible itself claims to possess and how much Christians are obliged to affirm.
We all agree (at least in principle) that inductive research should help us determine which of the portions of the Bible aim to be historical. We all agree (at least in principle) that a biblical text that doesn’t aim to be historical can still be true. For example, none of us will argue that the Parable of the Lost Son (Luke 15:11-32) is “false” even though we all agree—since it is a parable—it never happened in history.
But how much history is there? How much history needs to be there?
I’m inclined to say that lots of texts that evangelicals consider historical probably shouldn’t be read that way (e.g. Gen. 1-11). Nonetheless, lots of biblical texts are still very concerned with substantial historicity the key events. Moreover, the historicity of the events in the Bible does matter for lots of our Christian doctrines. So I don’t think we can make a binary distinction, claiming that the Bible is a purely theological but non-historical book.
We’ve got to be more refined than that, examining the texts of the Bible and the doctrines of the Church on a case-by-case basis to figure out where the points of friction are. (I recently edited a book exploring just this subject,
Evangelical Faith and the Challenge of Historical Criticism. Pete was kind enough to post an interview about it
here, if you’re curious.)
From a pragmatic point of view, there’s a downside to this nuanced construal of Scripture’s historicity. A definition of Scriptural truth that safeguards all its historical and scientific contents does build a nice fence around our other doctrines. (Muslims have a similar construal of the Qur’an, and it certainly can be useful.)
But the point of my “aha” moment is that the phenomena of Scripture itself don’t seem to support that depiction of Scripture. Scripture cannot bear the weight of the historical demands that many evangelicals place on it.
That sort of realization sometimes causes people to conclude (or fear) that all our other doctrines must be rubbish. But that’s sloppy logic; just because you can’t guarantee the historicity of every genealogical detail doesn’t mean that Jesus’ body is moldering in a tomb somewhere. There’s a ton of middle ground between those extremes, and evangelical biblical scholars (as well as non-evangelical Christian biblical scholars) can and should be (and are!) involved in mapping out that middle ground.
Are there doctrines “at stake” depending on the conclusions that people draw? Sure. But I don’t think our faith is actually well served by distorting the Bible, especially insofar as I think that the Bible is revelatory and true just as it is. As a good friend of mine,
David Lincicum, puts it, the job of the Christian biblical scholar is to seek the perfection Scripture has, rather than the perfection we would demand of it.
Index to Series -
Transparent Moments of Scholarship when a Theologian Must Either Stay or Change
