HistoricalChristian.Faith

One father-in-law, not a seam — the three names harmonized

Type: supporting argument (off-timeline) · Assessment: plausible — that Reuel, Jethro, and Hobab name one Midianite father-in-law and his household, so the received text is internally coherent and needs no redactional seam. The identification of Reuel with Jethro is widely granted (Reuel a personal or clan name; “Jethro,” from a root meaning “excellence, abundance,” plausibly an honorific), and the one hard datum — Hobab, called “son of Reuel” yet also Moses’ ḥōtēn — is reconciled by the genuine breadth of that Hebrew word (any relation by marriage, so Hobab is Moses’ brother-in-law), or by reading “Reuel their father” as grandfather (so Hobab/Jethro is the son and the actual father-in-law). Each move has real lexical warrant, so no contradiction is proved. But the reading falls short of demonstration: the harmonizing camp is not univocal (its two chief moves exclude each other), it must choose a different loose sense verse by verse, and the maximal rabbinic “seven names” form strains “son of Reuel.” Coherent and not ruled out, short of consensus · advanced by the rabbis’ seven names of Jethro and by conservative commentators (Barnes, Albright)

Related arguments: the three names of Moses’ father-in-law — see also The three names as a redactional seam

The claim

Reuel was probably not identical with Jethro: and Hobab was the brother-in-law, not the father-in-law, of Moses; the Hebrew word translated in the King James Version “father-in-law,” signifying simply any relation by marriage.

— Albert Barnes, Notes on the Bible, on Numbers 10:29.¹ The harmonizing thesis, in its strongest form, is not that one man improbably bears three unrelated names but that the text describes a single Midianite priestly household consistently: Reuel and Jethro are the one father-in-law, and Hobab is a second in-law of the same family — no seam, and no error, once the elastic Hebrew of kinship is read as elastic. The interpretation is weighed here, not any one proponent of it.

Who advances it

The reading is the default of the pre-critical tradition and of conservative exegesis after it. Its maximal ancient form is the rabbinic “seven names of Jethro” (Mekhilta de-Rabbi Ishmael, Amalek 3), which claims every name — Yether, Yithro, Chovav (Hobab), Reuel, Chever, Putiel, Keni — for one man, each glossed as a title of merit.² Later harmonizers refine it rather than repeat it. Albert Barnes and, before him, a long line of commentators read Hobab as Moses’ brother-in-law, taking ḥōtēn in its broad sense; Ellicott and the Pulpit Commentary make the same move, the latter noting that the word “has no such definiteness either in the Hebrew or in the Septuagint… It means simply a ‘marriage relation.’”¹ W. F. Albright, judging the Jethro–Reuel–Hobab traditions “quite homogeneous,” proposed that Reuel is the name of the clan to which both Jethro and Hobab belonged, so that the “son of Reuel” formula records clan membership, not paternity.³ Modern versions carry the reading into print: the NIV renders Hobab “Moses’ brother-in-law” at Judges 4:11.

The evidence for

Reuel = Jethro is barely a difficulty. That one person carries two designations across a narrative is unremarkable in the Hebrew Bible, and here the names invite it: Reuel (“friend of El”) reads as a personal or clan name, while Jethro/Jether derives from the root ytr, “excellence, abundance, pre-eminence,” and is plausibly an honorific title (“his excellency”) for the priest of Midian rather than a rival personal name. On that reading the shift from “Reuel” (when the daughters name their father, Exodus 2:18) to “Jethro” (once he stands in his priestly office, Exodus 3:1ff.) is a change of register, not of person.⁴

ḥōtēn really is a broad word. The whole knot is the Hobab datum — “Hobab, the son of Reuel the Midianite, Moses’ father in law” (Numbers 10:29), “Hobab the father in law of Moses” (Judges 4:11) — for a man cannot well be both Reuel’s son and Moses’ father-in-law if that father-in-law is Reuel himself. But the Hebrew ḥōtēn denotes a relation by marriage generally, not the wife’s father narrowly; the cognate ḥātān ranges over bridegroom, son-in-law, and any near kin by marriage. Read at that breadth, Hobab is Moses’ brother-in-law — the son of the father-in-law Reuel/Jethro, and so a brother of Zipporah — and Numbers 10:29 and Judges 4:11 agree without remainder.¹

Or “their father” is grandfather. A second, older harmonization keeps Hobab the father-in-law and moves Reuel up a generation: Hebrew Ḡb (“father”) commonly reaches to grandfather or ancestor, so “when they came to Reuel their father” (Exodus 2:18) can name the clan-head grandfather, while the daughters’ actual father — Moses’ father-in-law — is Jethro, alias Hobab, “son of Reuel.” Either way the point stands: a single genealogical fact (Reuel elder, Hobab younger) underlies all four passages, and the apparent clash is a translation artifact of forcing English “father-in-law” onto an elastic Hebrew word.

Adversarial assessment

What holds. No datum in the text forces distinct sources. Each harmonizing step rests on a real feature of the language, not on special pleading invented for the occasion: ḥōtēn genuinely is broad (translators and lexica agree, and the brother-in-law rendering is common enough to reach the NIV); Ḡb genuinely reaches to grandfather; a priest bearing a personal name and an honorific is ordinary; and Albright, no harmonist by temperament, still found the traditions “homogeneous” and Reuel best taken as a clan name. So the received text can be read as one coherent household, and the charge of flat contradiction does not hold against its strongest form.

What is overstated or imprecise. Three things keep the reading short of demonstration. First, the camp is not univocal. Its two chief moves are mutually exclusive on the plain question “who is Moses’ father-in-law?” — the brother-in-law reading answers Jethro (Hobab a sibling-in-law), the grandfather reading answers Hobab (Reuel an ancestor) — so the harmonizers agree only that a harmony exists, not on what it is, which is weaker than a single, forced reading. Second, it must choose its looseness verse by verse: a broad ḥōtēn here, a broad Ḡb there, the whole resting on selecting the non-default sense at just the points where the text pinches — defensible, but ad hoc. Third, the maximal rabbinic form overreaches: the “seven names” solution, by claiming even Hobab for the one man, collides with “Hobab, the son of Reuel” (a man is not his own father’s son), which is exactly why the stronger harmonizations quietly drop it and let Hobab be a second person. That overreach is flagged on the rabbinic detail page.

Assessment

Plausible. The received text can be read as one internally consistent portrait — Reuel and Jethro the one father-in-law, Hobab an in-law of the same household — and every load-bearing step draws on a genuine breadth in the Hebrew rather than on invented harmony, so the claim of a bare contradiction fails and no seam is required. What the reading cannot supply is a single, non-optional construal: it leaves open whether Hobab is the father-in-law or a brother-in-law, applies its loose senses selectively, and in its maximal “one man, seven names” form strains the very verse (“son of Reuel”) it is meant to absorb. That is enough to keep it coherent and live without making it compelling — the mirror image of the source-critical reading, which explains the same distribution more economically but at the price of the contested Documentary Hypothesis. On the harmonizing side the honest verdict is plausible: a defensible unity, not a proven one.

Sources