Raisin Bran Sundays
Raisin Bran Sundays, Choco-Cereal Weekdays
Why Job and the early church refused to treat faith as a moral checklist
I asked Google: Today’s ODB reading is Job chapters 34-35 and Acts 15:1-21. The first thing I notice is Job 34:11 which still reflects the idea that loss is the evidence of a wicked heart whereas it seems clear to both David and Solomon that the wicked sometimes succeed and the good sometimes experience loss. I don’t know how Elihu can even say in verse 30 that God prevents the godless from ruling. This to me points to an authorship prior to Moses. How do these sentiments compare to the Code of Hammurabi?
Google: Elihu’s speeches in Job 34 reflect the strict, ancient worldview that earthly suffering is a direct consequence of sin. Unlike the later writings of David and Solomon, which acknowledge that the wicked sometimes prosper and the righteous suffer, Elihu rigidly defends God’s justice by assuming suffering always implies a wicked heart.
Comparing these specific sentiments to the ancient The Code of Hammurabi (c. 1750 BC) [1.2.1, 1.3.1) reveals a surprising alignment:
Divine Retribution & Earthly Order: Both Elihu and King Hammurabi believed that the gods actively orchestrate earthly justice, rewarding the good and punishing the wicked. The Prologue of the Code of Hammurabi explicitly states that the Babylonian gods appointed Hammurabi “to destroy the wicked and the evil-doers; so that the strong should not harm the weak”.
The Problem of Rulership: Elihu’s claim that God prevents the godless from ruling (Job 34:30) mirrors the ancient Near Eastern theology embedded in law codes. The Code of Hammurabi operates on the premise that a properly functioning society under a righteous king is evidence of divine blessing, whereas a wicked ruler is cursed by the gods.
Differing Perspectives on Theodicy: While both frameworks assume moral cause-and-effect, they handle anomalies differently. Hammurabi’s Code is a practical, secular-religious system that focuses on social order and monetary restitution. The Book of Job pushes far beyond this, grappling with the reality that good people do experience profound loss, ultimately pointing forward to a deeper, mystery-laden theology of grace.
Me: I’m interested in the date of authorship even if it is speculative. If Job was authored during the Babylonian exile I suppose the sentiments might reflect Persian thought. How does that local wisdom compare to Job and the Code of Hamurabi.
Google: If the Book of Job was written or finalized during the Babylonian exile or the early Persian period (539–330 BC), it would have been composed in a world deeply saturated with Persian (Zoroastrian) thought. [1, 2]
This creates a fascinating philosophical intersection. While the Code of Hammurabi operates on legalistic earthly retribution and Job operates on transcendent divine mystery, Persian wisdom introduces cosmic dualism. [1, 2, 3, 4]
The Core Philosophies of Suffering
A direct comparison highlights how these three systems handle justice, rule, and the reason behind human misery:
The Code of Hammurabi (Mesopotamian)
Source of suffering: Human transgression or social lawbreaking.
Innocent suffer because: The system failed or a hidden vow was broken.
Nature of rulership: King chosen by gods to enforce order.
Ultimate resolution: Immediate physical or monetary restitution.
Persian Wisdom/Zoroastrianism
Source of suffering: Angra Mainyu (the chaotic, evil cosmic spirit).
Innocent suffer because: They are caught in the crossfire of cosmic war.
Nature of rulership: Leaders must align with Asha (truth/order).
Ultimate resolution: Eschatalogical victory and final judgment.
The Book of Job
Source of suffering: Divine allowance hidden in cosmic complexity.
Innocent suffer because: No reason. God’s wisdom transcends human metrics of fairness.
Nature of rulership: Moot point. Earthly empires are temporary; God mocks tyrants.
Ultimate resolution: Personal encounter with the Creator.
[Table transcribed by the author of this post and lightly edited for readability.]
How Persian Thought Inverts the Narrative
If the author of Job was exposed to the Persian Empire, they would have encountered a radical alternative to Elihu’s “suffering equals wickedness” model:
Separation of God from Evil: In Persian thought, the supreme god Ahura Mazda is only good. He does not cause suffering. Chaos, illness, and loss are caused entirely by the evil spirit, Angra Mainyu. [1, 2]
The Cosmic Battleground: Humans possess free will and act as soldiers in this spiritual war. Therefore, a righteous person suffering is not being punished by God; they are being attacked by the forces of darkness. [1, 2, 3]
The “Satan” Connection: The prologue of Job features ha-satan (the Adversary) bringing havoc upon an innocent man with God’s permission. Many scholars argue this character reflects the shifting post-exilic Jewish mind absorbing Persian ideas of an active, personalized source of evil, distinct from Yahweh. [1]
The Contrast with Hammurabi
While Hammurabi relies on a cold, math-like checklist of physical justice (“an eye for an eye”), Persian wisdom leans into a grand spiritual narrative. [1, 2]
The Book of Job ultimately rejects both paths. Job does not accept that his suffering is a legal punishment (contrary to Hammurabi and Elihu), nor does the book completely dualize the universe into equal forces of light and dark (contrary to the Persians). Instead, Job lands on a unique, fiercely monotheistic conclusion: God remains completely sovereign over both prosperity and ruin, even when His reasons are entirely beyond human comprehension. [1]
If you want to keep tracking this timeline, we could look at the Aramaic loanwords in Job that scholars use to argue for this late date, or we could contrast the Babylonian Job text (Ludlul Bel Nemeqi) with the biblical version. Which direction interests you? [1]
Me: Ok the Aramaic loanwords sounds like the gavel that makes the decision.
Google: The “gavel that makes the decision” is exactly how many modern biblical linguists view it. The presence of Aramaic loanwords, morphology, and syntax provides some of the most compelling “forensic” evidence for a post-exilic date of authorship. [1, 2]
When scholars dissect the Hebrew text of Job, they find that while the author tried to make the story sound ancient and patriarchal, their actual grammar and vocabulary give away their true time period. [1, 2]
The Linguistic Fingerprints in Job
Aramaic became the lingua franca (the common international language) of the Near East during the Neo-Babylonian and Persian Empires. If Job was written or significantly edited during this time, Aramaic would naturally bleed into the author’s Hebrew. [1]
The Vocabulary Shifts: In classical, pre-exilic Hebrew, the standard verb for “to take” or “receive” is laqach. In Job 2:10, the author uses leqabbel. This exact root is heavily used in Late Biblical Hebrew books like Esther, Ezra, and Chronicles, which are indisputably post-exilic. [1]
Aramaic Plural Endings: Classical Hebrew indicates a masculine plural with the ending -im (e.g., devarim for words). In Job 4:2, the author uses the Aramaic plural ending -in, writing millin instead. [1]
Parallel Hybrid Words: In Job 16:19, the author writes a poetic parallel line using both languages: “Even now, behold, my witness [Hebrew: ‘ed] is in heaven, and he who vouches for me [Aramaic: sahad] is on high.” [1]
Syntactic Borrowing: Beyond just dropping in cool foreign words, the very structure of the sentences (syntax) shifts in the poetic dialogues of Job, mimicking Aramaic sentence flow. [1]
The “Archaizing” Trap
This linguistic evidence directly explains why Elihu’s rigid, Hammurabi-like sentiments feel so out of place.
The author of Job was likely engaging in a literary technique called “archaizing.” They set the story in the deep past—the patriarchal era of Abraham, where wealth was measured in livestock and long lives—to give the dialogue a timeless, legendary weight. [1]
However, just like a modern filmmaker making a movie about medieval knights but accidentally leaving a Starbucks cup in the shot, the post-exilic author left Aramaic “linguistic cups” all over the text. [1]
Why Elihu is the Climax of the Debate
This late-date theory makes Elihu’s speech (Job 34–35) even more brilliant. The author is likely using Elihu to represent the old, traditional, black-and-white retribution theology that still dominated religious thought, even after the Exile. By having God completely ignore Elihu and speak directly out of the whirlwind in chapter 38, the late-date author is essentially putting a gavel down on the ancient Near Eastern worldview: The universe cannot be reduced to a legal checklist.
Would you like to explore how other late post-exilic texts, like Ecclesiastes, wrestled with this exact same breakdown of the old reward-and-punishment system?
Me: I’m also curious about the sheer length of this book. Is there discussion about why these back and forth claims and God’s response are so wordy? Is that also a Persian conceit?
Google: The immense, exhausting length of the Book of Job—with 29 chapters of cyclical, highly repetitive back-and-forth arguments—is a deliberate literary strategy rather than just a Persian artistic quirk. [1, 2]
Scholars widely discuss the book’s “wordiness,” noting that its architectural scale serves specific psychological, theological, and historical purposes:
1. The Exhaustion Strategy (The “Waiting Room” of Grief)
The exhausting repetition mimics the actual experience of prolonged trauma and grief. By forcing the reader to sit through three agonizing cycles of the exact same points rehashed by Eliphaz, Bildad, and Zophar, the author ensures you feel as drained as Job does. The “wordiness” strips away the reader’s patience, completely dismantling any neat, fast answers to suffering. [1, 2, 3, 4]
2. Scholarly Competition in the Persian Court
During the Persian (Achaemenid) period (539–330 BC), wisdom literature evolved into an elite, courtly art form. Scribes across the empire engaged in high-level intellectual debate, pulling from various regional philosophies. [1, 2, 3, 4]
The Aramaic Context: A late-date Jewish scribe writing Job would be familiar with epic, lengthy Aramaic texts like the The Aramaic Ahiqar found in Persian military garrisons. [1, 2]
Intellectual Flexing: To command respect in this international environment, a literary work needed epic proportions. The author uses thousands of lines of highly sophisticated, learned Hebrew to comprehensively defeat every existing Near Eastern philosophy of justice, giving the book the weight of a monumental legal defense. [, 2, 4, 5]
3. Deconstructing the “Talkers”
The sheer volume of human speech stands in stark contrast to its absolute lack of value. The friends speak thousands of beautifully crafted words, yet they say nothing of substance. When Elihu bursts onto the scene in chapter 32, he literally starts by apologizing for how wordy he is about to be, then spends six chapters repeating the previous arguments. The author uses this wordiness ironically to show that human wisdom, when left to its own devices, just loops in circles. [1, 2, 3, 4, 5]
4. Why God’s Response is Similarly “Wordy”
When God finally answers out of the whirlwind in chapter 38, He matches the friends’ verbosity but completely flips the subject. God doesn’t give a concise legal verdict; instead, He delivers a sweeping, panoramic tour of cosmic architecture, wild weather patterns, and terrifying beasts like Leviathan. [1, 2, 3, 4, 5]
God’s “wordiness” is an intentional sensory overload. He lists dozens of things humans can neither control nor understand to make a singular point: If human language cannot even capture the complexity of the physical ecosystem, it is utterly inadequate to summarize the moral governance of the universe. God overwhelms Job with words to bring him to a silence that isn’t empty, but full of trust. [1, 2]
Me: Let us move on to the New Testament reading. As usual0.
, there is an elegant link between them. Job “breaks the internet” for his time period just as Paul and Barnabas call a hard left turn in religious thought.
Google: The elegant link between the two texts lies in the total destruction of a transactional checklist. Just as Job’s story shattered the ancient Near Eastern “checklist” that said good behavior equals prosperity and bad behavior equals loss, Paul and Barnabas in Acts 15:1-21 shatter the religious “checklist” that says faith in Messiah plus circumcision and Mosaic law equals salvation. [1, 2]
Both moments represent a hard, shocking pivot away from rigid legal human systems and toward the overwhelming mystery of a sovereign, gracious God.
1. Breaking the Institutional “Internet”
In the ancient world, circumcision and the Mosaic law were not just religious preferences; they were the absolute boundaries of identity. When teachers from Judea arrive in Antioch saying, “Unless you are circumcised according to the custom of Moses, you cannot be saved,” they are protecting a centuries-old theological paradigm. They are the “Elihus” of the New Testament—rigidly protecting a system that makes mathematical sense to them. Paul and Barnabas step in and violently flip the table on this assumption, triggering a massive institutional shockwave that forces the historic Jerusalem Council. [1, 2, 3, 4, 5]
2. Moving from Merit to Mystery
The debate in the Book of Job and the debate at the Jerusalem Council are ultimately asking the exact same question: How does a human being stand justified before God?
The Old System (Elihu / The Judaizers): You must check the boxes. For Elihu, you stay out of trouble to avoid suffering. For the Pharisaic believers in Acts, you must keep the law and be circumcised to be clean. It is transactional. [1, 2]
The Hard Left Turn (God’s Whirlwind / Paul’s Gospel): Both God in the whirlwind and Peter/James at the council declare that God cannot be put in a human box. As Peter famously says in verse 11, “We believe it is through the grace of our Lord Jesus that we are saved, just as they are.” [1, 2, 3]
3. The Collapse of the Legal Yoke
In the dialogue of Job, the friends try to force a heavy moral “yoke” onto Job, forcing him to confess to sins he didn’t commit just to satisfy their theological equation. In Acts 15:10, Peter uses that exact imagery to describe the legalists, asking why they want to put a “yoke on the necks of the Gentiles that neither we nor our ancestors have been able to bear”. [1, 2, 3, 4, 5]
Both the conclusion of Job and the decision of the Jerusalem Council strip away human-made prerequisites. God demands faith, trust, and a heart transformed by grace, completely bypassing the neat, transactional rules that human institutions love to create. [1, 2, 3]
Me: It’s so funny you mention “box-checking” because that was really on my mind Sunday. We don’t just “get through church” and check the box so we can go the rest of the week doing our own thing. This is like me inspired one day this week to eat a healthier bowl of Raisin Bran but the rest of the week I’m all about the Cocoa Crispies.
Google: That is a perfect analogy. The “Raisin Bran Sunday, Cocoa Crispies Weekday” routine is exactly how the human brain naturally tries to compartmentalize faith. We want to hand God a single, highly nutritional box check on Sunday so we can claim our “righteousness credit” and then run off to indulge our sweet tooth for the rest of the week.
But both Job and the Jerusalem Council are screaming that God refuses to be a Sunday box check.
The Problem with “Dietary” Religion
When we treat faith like a checklist, we are operating exactly like Elihu and the Judaizers. We think:
If I eat the “Raisin Bran” (go to church, read the verses), God owes me a smooth, prosperous week.
If I get hit by a trial, I must have snuck a bowl of “Cocoa Crispies.”
It turns God into a celestial vending machine. But when God shows up in the whirlwind at the end of Job, He doesn’t say, “Thanks for the Raisin Bran, Job.” Instead, He points to the wild, untamed ecosystem of the universe. He is saying that faith isn’t a diet plan; it is a total, ongoing surrender to a sovereign Creator who rules over the whole week, not just the hour we spend in the pew.
The Acts 15 Shift
The leaders in Acts 15 realized that if they forced Gentiles to check the circumcision box, they were just creating an institutional health-food craze. It would make people feel righteous on the outside while leaving their hearts completely unchanged. Peter and James realized that true grace changes your entire palate. It’s not about surviving a bowl of bran once a week to satisfy a rule; it's about a complete lifestyle transformation.
Me: Final thought. Job is obviously an influential book even today, so I can imagine it was popular with the Jewish peoples. It’s even referenced in the New Testament. I’m trying to picture, especially in the light of recently learning rabbinic students mainly study the Torah. Describe how Job made its way into the collection of books we call the Old Testament?
Google: The Book of Job made its way into the biblical collection through a distinct channel of Hebrew Scripture known as the Ketuvim (The Writings). [1, 2]
While it is true that rabbinic students focused intensely on the Torah (the first five books of law), the Hebrew Bible actually developed as a three-part library: the Torah (Law), the Nevi’im (Prophets), and the Ketuvim (Writings). Job is anchored right in the heart of that third section. [1, 2, 3, 4, 5]
Job secured its permanent place in the Old Testament through three key developments:
1. The “Moses Attribution” Pass
For an ancient book to be considered holy and authoritative by the Jewish community, it needed a link to a prophet or a foundational leader. Even though modern linguistic evidence points to a late, Persian-period authorship, ancient Jewish tradition found in the Talmud (Bava Batra 14b) actually attributed the Book of Job to Moses. [1, 3]
The rabbis reasoned that since Job lived in the land of Uz (near Midian) and lived a long, patriarchal life, Moses must have discovered Job’s story during his 40 years of wandering in the wilderness and written it down. This apostolic-style endorsement from Moses gave the book immediate authority and protected it from being cast aside as purely secular literature. [1, 2, 3, 4, 5]
2. The Power of “Sifrei Emet” (The Truth Books)
Within the Ketuvim, the Jews separated the material into functional categories. Job, Psalms, and Proverbs were grouped into a highly prestigious, specialized triad called the Sifrei Emet (The Books of Truth). [1]
Emet is the Hebrew word for truth, but it also serves as an acronym for the three books: Iyyov (Job), Mishlei (Proverbs), and Tehillim (Psalms). [1]
These three books share a unique, complex system of poetic punctuation and musical chanting (cantillation) not found anywhere else in the Hebrew Bible. [1]
Because Psalms and Proverbs were central to Temple worship and daily wisdom, Job was pulled along into canonical status by its close literary and spiritual association with them. [1, 2]
3. Survival of the Exile
When Babylon destroyed Jerusalem and sent the Jewish people into exile, the old, rigid national identity collapsed. The Jews desperately needed literature that helped them process tragedy, loss, and the feeling that God had abandoned them.
The story of Job became a mirror for the entire nation. Like Job, Israel felt they had lost their home, their wealth, and their children through no immediate fault of the current generation. Job’s raw, agonizing honesty provided a vocabulary for Jewish survival. It proved that a person could wrestle fiercely with God, question His justice, and still be considered a faithful servant in the end. It was too valuable to leave out of the sacred library. [1, 2, 4]

Comments
Post a Comment