Threads from Henry's Web

Category: Energion.com

  • Preserving Literary Quality?

    Bryon’s Weblog has a quote from Leland Ryken and some commentary, followed by some rather silly comments by an obvious troll.

    What I found interesting here, however, was the idea of preserving the literary qualities of the Bible.  Let me reproduce the quote Bryon used:

    “If your essentially literal translation is the RSV, the ESV, or the NKJV—in other words, if your essentially literal translation rides the literary coattails of the matchless KJV—you can trust it to preserve the literary qualities of the Bible that the KJV gave to the English-speaking world for nearly four centuries.” [I did different emphasis than Bryon–HN]

    My hope here is that he means that the KJV passed on literary qualities of the Bible to the English speaking word, though I think he would still be wrong.  Since I don’t have the book I can’t check the context, but is it possible he’s praising literary qualities introduced by the KJV?  There was a time when I would have dismissed such an interpretation out of hand, but now I don’t know.

    Let me assume the best, however.  Even so, there seems to be a very strong tendency to regard representing something like the literal forms of the source language in words in a new language as somehow reproducing those literary qualities.  But that is not correct.  A similar combination of grammatical forms in one language need not, and in fact likely does not, mean the same thing to a reader.  And if the reader doesn’t read or hear the form in the way it would have been read or heard in the source language, has it been passed on?

    Creating some new literary quality that pleases certain academics or people of particular literary tastes is easy.  Actually producing a form that has a similar impact is much harder.  To support the value of literal translation over dynamic or functional, other than as a sort of crib sheet for the source language, requires more than finding badly done dynamic translations of which there are plenty.  It requires demonstrating that the nuances and literary features presented by the literal translation both occur in the source language, and are conveyed to the target audience by the literal translation.

    Other than amongst the advocates of these literal versions, I don’t see that happening.  In fact, most of the people who “get” the literary nuances do so not because they were actually conveyed by the translation, but because that person knows enough of the source languages to recognize the construction and thereby reads that literary quality into the English.

  • Book Notes: God’s Problem (Ehrman)

    Ehrman, Bart D. God’s Problem: How the Bible Fails to Answer Our Most Important Question-Why We Suffer. New York: HarperCollins, 2008. ISBN: 978-0-06-117397-4. 294 pp.

    I have previously noted that Bart Ehrman’s books are much more controversial on their jackets than on their pages (see notes on The Lost Gospel of Judas Iscariot and Response to Misquoting Jesus). This is not to say that there is nothing controversial. Rather, well-known issues are stated in a stark and controversial way.

    This book is no exception to this prior experience. I was both amused and annoyed that my copy from the library had been “annotated” by some previous user. That always annoys me, because defacing library books is vandalism and I don’t like it. But the form it took is interesting.

    On the title page the words “fails to” are crossed out of the subtitle, and and “s” is added to “answer” to that it says “How the Bible Answers Our Most Important Question.” Then there is a note that says simply “sin, In the 1st Book Genesis 3.” Of course, as any competent scholar would, Ehrman covers the role of sin in human suffering according to various Biblical authors.

    In the conclusion he also notes how people are divided between two groups. Those who announce their answer as though it was conclusive and obvious, as this annotator did, and those who really don’t want to discuss the topic at all.

    I have thought a great deal about the problem of suffering and am willing to talk about it a great deal, but I don’t actually think I have any very good answers. It was interesting to me that neither Ehrman nor I will give a definitive answer, but we have a certain amount of affinity for similar answers. The bottom line for me is simply, “That’s the way the universe works.”

    Of course there is also suffering caused by human evil, so the “sin” solution is certainly a part of suffering. But any of these leaves one with the question of just how God fits in. And there I would differ with Ehrman considerably. The problem of suffering itself is one thing; one can even ask the question why we should not suffer. The problem of suffering when one also believes in a “good” God is another matter entirely.

    And that’s why the book is titled “God’s Problem.” On one level this is simply a summary of how the various Bible writers answer the question of why we suffer. On another, it is Dr. Ehrman’s journey in dealing with the fact that we do suffer and the implications of that fact for our understanding of God. Some may dislike the idea of mixing one’s personal experience with a book of scholarship, even a popular one. I would disagree. I think the personal reflections, however much they differ from my own, enhance the book and help one to connect the various scriptural responses to real life.

    Let me look at these two levels separately. It was interesting to read this book nearly simultaneously with Bruce Waltke’s An Old Testament Theology. The books differ a great deal in size, intended audience, style, and the level of presentation, yet they very clearly illustrate a significant divide in Biblical scholarship. Do we look try to see the scriptures as ultimately unified, and thus reconcile apparent differences theologically or do we lay out those difficulties as starkly as possible?

    That question outlines extremes. There are many variations along the way, including a kind of unity in diversity. I like to refer to the unity of a large river system, rather than that of a carefully delineated pathway. But Waltke approaches the Bible as a unity to be brought into subjection to his christology, while Ehrman sees the Bible as many individual schools of thought and tends to demarcate these schools rather strictly.

    As an outline, I’m rather happy with Ehrman’s work. He points out what the major positions are. I think there could be some more work done on seeing how those positions might coexist. For example, the view that suffering is a punishment for sin can co-exist with the apocalyptic view that sees suffering as something inflicted by evil forces. I know people in real life who will respond with either of these options according to the circumstances. They don’t always have any logic other than whether they feel that a particular person is deserving of “discipline” or is demonstrating strength as they face the forces of evil.

    Scholars tend to try to keep things more logically disciplined than that, which is probably a good attitude for a scholar to have. But it can get in the way of describing real people who are quite frequently a great deal messier.

    In particular, I question some of Ehrman’s work on Job. I think he takes a view on Job that would require the final redactor to be some sort of idiot. See my notes on this on my Participatory Bible Study Blog.

    Those who would be very critical of Ehrman’s approach, however, should consider the almost casual way theologians often try to brush aside such objections. I did not include this topic in my notes on his book, but Waltke brushes aside major issues in this fashion, particularly when talking about genocide in Joshua.

    There he dismisses the problem by suggesting that those who were willing to repent and convert, such as Rahab were subject to destruction, while those in Israel who failed to maintain the standards, such as Achan, were also destroyed. Many people, myself included, would not see a “convert or die” approach as substantially more acceptable than genocide. In fact, any theory of inspiration that does not take adequate account of human failings and ideas runs aground on this problem. If God in fact said “kill them all, even babies” and intended this as a good thing, then God is monstrous. It is possible that God allowed them to think that, because that was what they were inclined to do. It is sufficiently difficult to explain God allowing such a thing, much less explaining why he would positively demand it.

    Yet of course the text says that God did just that. For me, that is a strong sign of how the Bible deals with people, still steeped in the culture and moral standards of the time, struggling with what God would have them to do. This is an aspect of the problem that Ehrman only touches on as part of the punishment for sin view.

    As for Ehrman, just as I noted in my review of his book Misquoting Jesus, I think he responds largely to a fairly conservative evangelical view of Biblical inspiration, such as would be espoused by Waltke. I don’t mean that a bit of adjustment in one’s view of inspiration solves all the problems. Hardly! But it does make the discussion much more interesting and offer more avenues for a solution.

    And this is where we come to the more personal issue. While I did not go on to get a doctoral degree, nor have I written such popular books, I really empathize with Ehrman’s experience. I came out of seminary with a “this can’t be” kind of feeling, and departed the faith at that point. Twelve years later I came back, but to a much more liberal theology. I came to the realization that I did believe in God, however much I might prefer not to, and thus I would have to deal more with my concept of God.

    I’m not trying to present my position as the better option, though obviously I prefer it since it’s mine! But if I’m to believe that the physical universe reveals its creator, then I have to be willing to adjust either the adjectives I use in referring to God or the meanings of those adjectives. In general, it may be more honest to use different adjectives.

    That’s why I have written that God is more interested in freedom than comfort. Ehrman discusses the “freedom of the will” explanation for suffering, though he correctly points out that the Bible isn’t that much concerned with such an explanation, and also that it fails to deal with natural disasters that are chosen by nobody. At the same time the Bible does address this issue from the direction of responsibility. Sin comes through one man and thus death (Romans 5:12). But the Bible tends to lay responsibility without really acknowledging freedom, something that puts Paul into contortions in chapter 9, from which he extracts himself (if one is generous) by breaking into a bit of doxology.

    By freedom, however, I mean something more than freedom of choice. Rather, God constrains the universe within laws rather than directing particulars. God didn’t want Hurricane Ike to destroy so many homes on the gulf coast; he wanted each hurricane to behave as hurricanes do. If you want to see God as loving, you also have to see him as willing to allow hurricanes to be hurricanes.

    Is that a solution? All I can say is that it works for me, but I know plenty of people, my wife being one, who do not find that very satisfying. I found it interesting that Dr. Ehrman and his wife also differ, more profoundly than I do with my wife, on the very issues involved.

    The bottom line here is that I deeply appreciate this effort to discuss such a difficult problem, and to relate it to one’s personal struggle. I disagree substantially with the conclusions, but largely because I start with different premises. My belief in God, with the kernel being “ground of all being” (Tillich) is fundamental, while my concept of God is more flexible. I’m much less likely to say, “I see that my old concept of God won’t fit with the suffering in the world, so there must not be a God” than to say, “My concept of God doesn’t fit with the suffering in the world, so I must have misunderstood God.”

    That difference is personal and experiential at root, I think, and would be very hard to reconcile. It lies way too far outside the realm of “mostly certain” knowledge. In the meantime, you could do worse than to read this book and see how it helps you think about the problem of suffering.

  • Source and Redaction Criticism: Ehrman on Job

    In chapter six of his book God’s Problem, Ehrman tackles the book of Job.  (My notes on the book as a whole are here.)  He describes the book as coming from two sources, one containing the narrative portions, and one containing the poetic dialogues.

    This view is not that exceptional, though one should also consider a very common alternative, that the dialogues were written separately, but that one and same person wrote the narratives and redacted the entire book.

    Ehrman says:

    Most people who read Job do not realize that the book as it has come down to us today is the product of at least two different authors, and that these different authors had different, and contradictory understandings of why it is that people suffer. . . . (p. 162)

    The prose author, he says, sees suffering as a test of faith, while the author of the dialogues believes that there ultimately is no answer.

    Ehrman correctly notes differences of genre, and differences of style.  The seams in the book suggest the possibility of multiple sources.  Ehrman adds to this a difference in the portrayal of Job.  While I have been aware of the possible sources since college, and have read the book many times, I have never seen a problem with the characterization of Job.  I chalk this one up to the common scholarly exercise of trying to make people more coherent and logical than they normally are.

    Ehrman also feels that the parts were not combined very well.  On page 167 he notes the reaction of God in chapter 42:

    . . . It is obvious that a bit of the folktale was lost in the process of combining it with the poetic dialogues, for when it resumes, God indicates that he is angry with the three friends for what they have said, in contrast to what Job has said.  This cannot very well be a reference to what the friends and Job said in the poetic dialogues, because there it is the friends who defend God and Job who accuses him.  And so a portion of the folktale must have been cut off whent he poetic dialogues were added.  What the friends said that offended God cannot be known. (p. 167)

    All of which treats the final redactor as an idiot.  This is one of the key problems when source and redaction criticism are viewed as providing “the” answer to the meaning of a passage or book.  Source critics tend to think they’re done when they have finished identifying the sources and mourning the missing parts.

    But is the redactor (or final author) actually so silly that he fails to miss the fact that the friends are defending God and Job is challenging him?  I think there is good evidence to suggest not.  In the dialogues, the friends hold that Job is guilty of something and that God is punishing him.  The narrative portions clearly state that this is not the case.  In other words, the friends have been making false claims about God and accusing Job of wrongdoing, when no such wrongdoing has taken place, according to the narrative portions.

    If one takes the resultant whole as a polemic against the Deuteronomistic approach (or at least a supplement to it, as the two are not completely incompatible), which holds that blessing comes to those who do right and curses to those who don’t, then I think the combined text makes quite good sense.  It is not a theodicy.  I want to scream when people insist it is; there is no intention of justifying God in the book of Job.  If there is, it is a miserable failure.  It is not a coherent picture of why people suffer.  In fact, it makes clear that one cannot know.  From the point of view of the text as a whole, Job never gets to know what the problem was.  He may have been enduring a test of faith, but all he knows is that he is a) innocent and b) suffers.  He is satisfied that God appeared, and he is affirmed as a righteous man by God’s actions.

    I think a better redaction theory would be that the narrative author had the dialogues before him, which fail to present an answer.  Suffering there is mysterious, and the issue is never resolved.  He wraps this in a story that makes the mysterious suffering have a cause, in this case, the test.  While Job still remains in mystery, he is satisfied that at least God showed up.

    Ehrman comments on Job’s response to God’s presence:

    . . . God is not to be questioned and reasons are not to be sought.  Anyone who dares to challenge God will be withered on the spot, squashed into the dirt by his overpowering presence.  The answer to suffering is that there is no answer and we should not look for one.  The problem with Job is that he expects God to deal rationally with him, to give him a reasonable explanation of the state of affairs; but God refuses to do so.  He is, after all, God.  Why should he have to answer to anybody?  Who are <em>we</em>, mere mortals, to question GOD? (p. 188, emphasis in original)

    The problem, in my view, is that this does not give adequate credit to even the literary concept of an encounter with God, much less the reported personal experience.  People speak of being terrified, spent, and shattered, yet they come out encouraged and feeling positive.  Those who have had mystical encounters, amongst whom I count myself, may well not record such encounters as entirely joyful, and may not come out with all answers, but at the same time, generally don’t feel that they can no longer seek answers.

    In this concept, the friends have to repent of trying to represent God, and doing so incorrectly.  They have to repent of accusing an innocent man.  Job, on the other hand, at the same time repents of thinking he’s going to be able to handle it and understand it, yet he is not condemned for seeking an answer, and for upholding his own innocence even in the face of seemingly irrefutable theological positions.

    The redactor is thus not an idiot.  I personally don’t find his approach to suffering all that helpful, but I do find it challenging.  It provides a way to think further.  This redactor, or final author, if he is trying to present Job as squished into the dust and intimated into no longer seeking answers, has a rather odd way of doing so.  He presents a book that seeks after answers, challenging old ones and suggesting new ones.

    I think that Ehrman has misunderstood the narrative portion, and done so in such a way as to present some unknown final redactor in the worst possible light.  Careful reading of the final whole finds a viewpoint that is worth considering in itself.

    This doesn’t detract fromt he sources, though personally I think that there is only one source, the poetic dialogues.  The author of our canonical book took those dialogues and wrapped them in prose, forcing them to serve him.  Far from being an idiot who couldn’t tell that his ending didn’t match his beginning, he was a creative author who molded older material into a new and useful form.

  • Etymology but no Fallacy

    I’m glad to see Bill Mounce discuss valid use of etymology.  I’ve long thought that we have fallen into an “every etymology is a fallacy” trap, but it’s good to see an acknowledged expert say that.  Note that the vast majority of etymologies I hear are indeed false etymologies, but there are valid uses.

  • Book Notes: An Old Testament Theology (Waltke)

    Waltke, Bruce K. with Charles Yu. An Old Testament Theology: an exegetical, canonical, and thematic approach. Grand Rapids: Zondervan, 2007. ISBN: 0-310-21897-7. 1040 pp (940 excluding front and back matter).

    I’m going to complain a bit about this book, so first let me tell you the good things about it. It provides a solid introduction to the scope and theology of the Old Testament from a confessional point of view, starting from Christian orthodoxy. The tendency is the conservative edge of evangelicalism. It is not fundamentalist, and struggles with many issues that one might expect fundamentalists to ignore.

    In addition, there are several very strong points about this:

    • Waltke clearly expounds his approach and the understanding of inspiration on which he bases it. He then consistently applies that throughout.
    • The discussion of narrative theology and how one goes from narrative all the way to application. I don’t always agree, but the discussion is enlightening.
    • The chapter on creation has much to commend it, though it features in my complaints as well.
    • Chapter 16, The Gift of Liturgy is again excellent.
    • The overall theme of covenant theology is well-done and will be very helpful along with the discussion of alternatives.

    A substantial portion of the book is taken up simply narrating the story of the various Old Testament books and providing an introduction and background. Thus there is less on the theology of a book than there is simply bringing the reader to the point of understanding. This is probably required in an introduction of this sort, though ideally I would hope someone would take an Old Testament introduction before taking Old Testament theology.

    The confessional approach is not precisely one that resonates all that well with me in the study of the Hebrew scriptures or the Old Testament. This should not be a complaint because one can hardly criticize a book for being what it sets out to be. One should, however, note that Waltke is quite serious about this and that the confessional approach shows through.

    The book is also true to its title as an Old Testament theology, and not a theology of the Hebrew scriptures. In other words, the Old Testament passages are read Christologically, and chapters frequently conclude by discussing how these concepts carry through into the New Testament. Again, this is an approach that is clearly stated in the early stages of the book, and then carried through consistently.

    Though I personally would prefer more discussion of the theology in the historical context rather than the context of Christian canon and theology, this is again a stated goal of the book as a whole. You will find the justification for that approach in the preface and the first several chapters.

    Now for some complaints:

    • The author affirms Biblical inerrancy. While I do not, that is not the complaint. In his support of inerrancy and the unity he expects as a result, he seems to gloss over differences in theology between various books with very limited explanations. For example, the difference in perspective on marriage outside of Israel between Ruth and Ezra/Nehemiah is not so much as given a routine dismissal.
    • The author is very much opposed to the historical-critical method, but doesn’t really bother to explain very much of it. I would expect that if one dismisses a particular method in an introductory work, one needn’t go into depth on it, but he repeatedly references and disparages the method, almost exclusively by discussing naturalistic presuppositions, yet fails to provide sufficient foundation in my view.
    • The discussion of creation is really quite good, but is marred by a dismissal of “evolutionism” based again on its supposed naturalistic assumptions. In fact, some varieties of theistic evolution would fit quite well with the interpretation of the early chapters of Genesis provided.
    • Chapter 9, The Gift of the Bride is dismal throughout, in my view, as Waltke embraces patriarchy with both arms. That is too long of a discussion to go into here. Suffice it to say that I disagree with almost the entire chapter, including the notion that Deborah is the “exception that proves the rule” (p. 245).

    I just reviewed DeSilva’s New Testament introduction, which is also from a more conservative perspective than my own, though not as conservative as Waltke’s. Yet DeSilva managed to present a variety of viewpoints while at the same time letting you know where he stood. He provided enough material for the student to evaluate without even going to the references. That is a quality I really appreciate in an introductory work.

    I am not a fan of purported neutrality. The author does have a viewpoint, and I think it is better to let the reader know what that is. Yet advocacy can be combined with a broad coverage of alternatives that give the student a good perspective. I know a number of liberal works that write as though all conservative views can be dismissed. For example, one will search in vain for defenses of Mosaic authorship in many critical commentaries on the books of the Pentateuch, even defenses presented for the purpose of refutation. This book appears to be a good example of the reverse.

    It’s a bit cheeky of me to review the work of so well-respected a scholar as Waltke, whose Biblical Hebrew Syntax I consult regularly (it’s on my “constantly available” shelf). But while I did find considerable here that was helpful, the items I mentioned detracted substantially from the value of this experience. Were I asked to teach Old Testament theology (much more likely than that I would be asked to teach New Testament intro!–see my comments on DeSilva), this would not be my text.

  • New Creationist Prize

    . . . and it’s sillier than the old ones.

    Adnan Oktar, who writes as Harun Yahya, is offering the prize, according to the Telegraph.co.uk (HT: Breaking Christian News, surely an interesting place to find this):

    Mr Oktar, 52, who successfully campaigned for Mr Dawkins’ official website to be banned in Turkey, has said he will give 10 trillion Turkish lira, roughly equal to £4.4trn “to anyone who produces a single intermediate-form fossil demonstrating evolution.”

    The problem with all these prizes is that the folks offering them demonstrate no comprehension of even the most basic elements of how an historical science is carried out, and simply cannot recognize the abundant evidence when they see it.

    Of course, the effort to ban the Dawkins web site amply demonstrates Mr. Oktar’s particular methodology. He doesn’t have the facts, so he prefers to ban the opposition.

    As an interesting side note, and a case of “with friends like these, who needs enemies,” Mr. Oktar defended Dr. Michael Reiss:

    Mr Oktar has also defended Professor Michael Reiss, the British biologist who resigned as the director of education for the Royal Society earlier this month after suggesting science teachers should tackle creationism if the matter is raised by pupils.

    I also believe Dr. Reiss was treated wrongly, and even more the cause of sound science education was dealt a blow. But Mr. Oktar should consider that he wants to ban a web site entirely for disagreeing with him, while complaining that a scientist lost one position. He should be too embarrassed by his own actions censoring dialog to complain about those of others.

  • Book Notes: An Introduction to the New Testament (DeSilva)

    DeSilva, David A. An Introduction to the New Testament: Contexts, Methods, and Ministry Formation. Downers Grove, IL, 2004. ISBN 0-8308-2746-3. 974 pp. (904 without front matter and indexes).

    This is a bit out of place for review here and by me, but I wanted to write a few notes about it anyhow.

    If I were to teach an course in New Testament Introduction, admittedly not all that likely, I would want to use this text. I’m not an NT specialist, and this book is not well suited to the groups I usually teach. It’s designed for the seminary student, and I wish I’d had it as a text at that time. Alas, that was the 70s, and the copyright date is 2004.

    Why do I like it? The primary reason is that it covers issues in New Testament criticism effectively and practically. By “effectively” I mean that various critical methods are described briefly and clearly so that the student can grasp both the origins of the method and how the method might be applied even by those who don’t accept all the presuppositions of those who originated it. The description is rounded out by examples. By “practically” I mean that each such section concludes with practical exercises.

    I had to figure a great deal of this stuff out by working backward from commentaries. There are, of course, a number of rather good books which I discovered along the way (Augsburg Fortress’ series Guides to Biblical Scholarship comes to mind), but both my undergraduate and graduate experiences generally involved hearing or reading the claims, struggling with the material, and then finding the good explanations afterward.

    These sections don’t just cover a few traditional critical skills. They range from textual criticism to feminist criticism with the positive and negative aspects of each, and all those between.

    A secondary reason to like this book is the emphasis, indicated in the subtitle, on ministry formation. I work largely with lay audiences, but I do frequently get to talk with pastors, and one great weakness of seminary education, from my unscientific survey, is a lack of practical application. I can do [something taught in seminary], but how will I use it? Each book of the New Testament has a discussion of how it can be helpful in ministry formation.

    These sections are good. I would think that a good seminary student would want to keep this one for his library shelves. If he or she did not, it would set off alarm bells for me.

    Just to give an example of the types of topics, let me look at the book of Romans, since it’s one I’m studying for personal devotions at the moment, as well as at church. We encounter a full page excursus on the literary integrity of Romans, a slightly longer one discussing faith in Romans, another titled “Grace and Justification in Jewish Sources”, one on “Paul’s Hermeneutics and the Pesharim of Qumran”, another on “The Enigma of Romans 7:7-25” (he and I would disagree in part there, but it’s a pretty thorough discussion), and “The Law: Catalyst for Sin or Divine Remedy.” The “EXEGETICAL SKILL” section is a bit over 2 1/2 pages on social-scientific criticism discussing analysis of ritual. The Ministry formation section covers a bit over seven pages. All of this is the extras that frame an excellent introduction to the book and to tendencies in interpretation. DeSilva even manages to discuss homosexuality, though doubtless due to the nature of the topic, nobody will be satisfied!

    Not being a specialist in this area, I really haven’t surveyed the full field of New Testament introductions–there are quite a number of them–but I have read a few, and none matched the quality of this one in all ways.

    I should note that DeSilva is clearly more conservative theologically than I am and more negative on the values of some of the older forms of criticism–form, redaction, and source, for example. But that does not prevent him from presenting both the positive aspects and the nuts and bolts methodology, within the scope to be expected of a work of this size. I would not be uncomfortable basing a class discussion on his material on any of the topics, even homosexuality.

    Unfortunately, as I said, I won’t get much opportunity to use this book, but I did enjoy reading it, and I do recommend it as a way to kind of round up your New Testament exegetical skills, especially if you’ve gotten stuck a bit in a specialist’s rut. If you are an NT specialist about to teach NT introduction, check it out.

  • Borrow, Spend, and Rescue

    The senate has passed the bailout bill, and the house is expected it soon. I greet this event with seriously mixed emotions.

    I do believe that responsible legislators, should there be any, needed to support quick action, and because the action was quick, and because it was in response to a crisis, it is likely to be much less than perfect. Also, by the time you make all the compromises necessary to pass a bill quickly, the result is going to be substantially less than ideal.

    But while it is necessary at this point, this bill also reflects much of the financial mismanagement of which our government is guilty. I do blame both parties on this, though in different ways. (In my oft-repeated phrase, that’s another post.)

    The compromise results in borrowing more money, handing out more authority to executive agencies without adequate supervision, and in other measures that will serve to increase the deficit and our growing national debt. It seems that whatever good intentions the legislators start with, every bill ends up with us spending more and going deeper into debt.

    As a stop-gap, perhaps $700 billion, along with an extra $100 billion or so in tax cuts will help temporarily. But we cannot go on forever behaving in this fashion. Sometime things have to be paid for. Democrats want the government to do more, and at least they admit it. Republicans talk about smaller government but continually expand it, and also tend strongly to increase executive power.

    So while I believe this was necessary as a short term solution, I believe that we, as a nation, should feel like the consumer who has just charged his power bill by maxing out his last credit card–it can’t go on. Something has to give.

  • Seeing What We Expect

    I was interested in watching the reactions to the debate the other night. No, I didn’t watch it, so I’m not going to give any opinion about who won or lost, or who was right.

    But in the blogs to which I subscribe I found two posts that were very interesting to me. The questions involve just which candidate is more “presidential.” Of such very subjective judgments many votes are crafted. A president might be chosen because too many people didn’t like how many times he looked at his opponent in a debate, or his use of a first name.

    The first reaction was from Brian McLaren. Not too surprisingly he found that Obama’s performance was more presidential.

    The second was from C. Michael Patton. Quite unsurprisingly he thought McCain was the most presidential.

    Go read them both. I have no idea what set of mannerisms would indicate that someone was truly presidential. I’ve never made a voting decision on that basis. I think leadership can come in many styles, and in some cases a good leader might be a lousy debater or speaker. Each thing is a factor, but I have a hard time figuring out just what would constitute “presidential” behavior.

    Both of the men to whom I linked are intelligent Christian leaders and are good writers. I really enjoy both of their writing on religion and politics, though I obviously disagree with each on a number of items. It seems to me that they interpreted the mannerisms of the candidate that they already favored positively, and those of the other man negatively.

    I’ve noticed this tendency in reporting. It’s one of the reasons I’ve started limiting my reading to FactCheck.org and PolitiFact on anything that’s about campaign politics, in which I include ads, claims, counter-claims and so forth, rather than substantive policy discussion. So much material on all sides simply appears to me to amount to putting the best construction possible on things said by your own side and the best worst [see comments] possible construction on things said by the other.

    I don’t think it’s possible to shed bias completely, but I think we ought to ask ourselves just what we would think of the same actions or the same words if they were spoken by our own favored candidate.

  • RefTagger from Logos Bible Software

    I generally read Adrian Warnock’s blog because his theology is so glaringly different from my own that I think there’s a certain amount of community accountability that results just from forcing myself to read and consider his viewpoint.  (Sorry, Adrian, but that’s how it is!)

    But today he pointed me to a new tool from Logos Bible Software, RefTagger which appears to be a wonderful addition to this blog, considering the number of Bible references I use, and also the fact that I use the Logos software on my laptop.  (This is a Linux machine, so no Logos, but via my home network, I can remote control by laptop and use Logos anyhow.)

    It comes either as a snippet of code, or as a plugin for your WordPress blog.  I’m going to test it here and see how I like the overall result, but I will probably end up adding this code to a large portion of my various sites.  So thanks to Adrian for pointing it out!

    I also just have to point out, being who I am, that I am starting with a default version of TNIV for the tooltips, whereas Adrian, of course, has the ESV.  It’s fun to be different!