Mark D. Roberts

Mark D. Roberts


Introduction to Nehemiah

posted by Mark D. Roberts

Part 4 of series: A Theology of Work in Ezra and Nehemiah
Permalink for this post / Permalink for this series
Last week I introduced the Theology of Work Project (TOWP). I explained the vision of this project and my own participation in it. My task, as you may recall, is to do a commentary-like overview of the Old Testament books of Ezra, Nehemiah, and Esther. For each book, this overview seeks to answer the question: What is the theology of work in this book?
As I mentioned before, none of these books is composed primarily of didactic or legal or prophetic material. You can’t turn to a chapter that instructs on the nature of work or how we should do it. Rather, Ezra, Nehemiah, and Esther are narratives, and in these narrative, work happens. Thus we can learn from the example of the “workers” in these books. Moreover, upon occasion, one of the leading characters says something that, by implication, helps us to glimpse an implicit theology of work.
At the end of last week I examined the book of Ezra, introducing the text and then examining it for theology of work material. Ezra doesn’t have much to say about work, per se, though it does feature a kind of work, namely building (or rebuilding) the Temple in Jerusalem. This effort reveals something of the nature of work, when seen from a biblical point of view.
The book of Nehemiah is similar to Ezra in many ways. This comes as no surprise, of course, once we know that Ezra and Nehemiah were once part of a single, two-part work. In fact, in my commentary on Ezra, Nehemiah, and Esther for the Communicator’s/Preacher’s Commentary series, I treated Ezra-Nehemiah as a single work. The book we call Nehemiah continues the story began in Ezra, focusing on the rebuilding of the wall of Jerusalem and the rebuilding of the people of God in light of the covenant.
The book of Nehemiah, which features the rebuilding efforts of the man Nehemiah, opens by placing the events in a historical context: “In the month of Kislev in the twentieth year, while I was in the citadel of Susa . . .” (1:1). This gives us a date and a place. Of course we have to ask, “In the twentieth year of what?” The answer comes in Neh 2:1, where it says, “In the month of Nisan in the twentieth year of King Artaxerxes . . .” (2:1). But even this isn’t entirely helpful, because the Persians had three kings named Artaxerxes. So which one is in view here? Though there is not scholarly unanimity on this matter, many believe that Nehemiah refers to Artaxerxes I who ruled from 465 to 423 B.C. This would place the beginning of Nehemiah in 445 B.C., which would be about thirteen years after Ezra’s work in Jerusalem.
The “citadel of Susa,” or perhaps the “capital of Susa,” points to the winter lodging for Persian kings. The city of Susa, located in modern Iran, not far from the Iraqi border, included a large palace that had been built by Darius. The fact that Nehemiah was in Susa suggests what is made explicit in the last verse of the first chapter, that Nehemiah was associated with the Persian king Artaxerxes I. (Photo: Excavation of the palace in Susa. The cell phone tower in the background was a later addition, not found in the time of the Persian kings.)
In fact, Nehemiah was the king’s “cupbearer” (1:11). To us, this may sound like a lowly position. After all, Nehemiah was not only the one who held the king’s cup, but also the one who tested the king’s drink to make sure it was safe. Even as Secret Service agents are committed to “take a bullet” for the President, so Nehemiah was willing to “drink the poison” to protect his king. But, in reality, the cupbearer was also a trusted adviser to the king. He enjoyed a position of honor, luxury, and authority. As we’ll see in the unfolding drama of Nehemiah, his position with the king was crucial in his effort to restore the city of Jerusalem.
In my next post I’ll have more to say about what we learn about Nehemiah in chapter 1, and how this touches upon our understanding of work.



Previous Posts

More blogs to enjoy!!!
Thank you for visiting Mark D. Roberts. This blog is no longer being updated. Please enjoy the archives. Here are some other blogs you may also enjoy: Red Letters with Tom Davis Recent prayer post on Prayables Most Recent Inspiration blog post Happy Reading!  

posted 2:09:11pm Aug. 27, 2012 | read full post »

Why Did Jesus Have to Die? Conclusions
In this series on the death of Jesus, I have presented four different perspectives on why Jesus had to die: Roman, Jewish, Jesus’, and Early Christian. I believe that each of these points of view has merit, and that we cannot fully understand the necessity of Jesus’ death without taking them all

posted 2:47:39am Apr. 11, 2011 | read full post »

Sunday Inspiration from the High Calling
Can We Find God in the City? Psalm 48:1-14 Go, inspect the city of Jerusalem. Walk around and count the many towers. Take note of the fortified walls, and tour all the citadels, that you may describe them to future generations. For that is what God is like. He is our God forever and ever,

posted 2:05:51am Apr. 10, 2011 | read full post »

Why Did Jesus Have to Die? The Perspective of the First Christians, Part 3
An Act and Symbol of Love Perhaps one of the most startling of the early Christian interpretations of the cross was that it was all about love. It’s easy in our day, when crosses are religious symbols, attractive ornaments, and trendy jewelry to associate the cross with love. But, in the first

posted 2:41:47am Apr. 08, 2011 | read full post »

Why Did Jesus Have to Die? The Perspective of the First Christians, Part 2
The Means of Reconciliation In my last post, I examined one of the very earliest Christian statements of the purpose of Jesus’ death. According to the tradition encapsulated in 1 Corinthians 15, Jesus died “for our sins in accordance with the scriptures” (15:3). Yet this text doesn’t expl

posted 2:30:03am Apr. 07, 2011 | read full post »




Report as Inappropriate

You are reporting this content because it violates the Terms of Service.

All reported content is logged for investigation.