I Chronicles 14

This chapter feels almost like a breather — three quick scenes stitched together without much transition — but it's doing real theological work if you slow down. Scene one: Hiram, the pagan king of Tyre, shows up with cedar logs and skilled craftsmen to build David a palace (verses 1-2). Scene two: a list of David's growing family in Jerusalem, sons and daughters, including the boy who'll become the next king, Solomon (verses 3-7). Scene three: two rounds of war with the Philistines, framed almost identically — they come up, David asks God what to do, God answers, David obeys, David wins (verses 8-17).

Here's what's easy to miss: the Chronicler is not writing straight chronology. If you compare this to 2 Samuel, some of this actually happened before David brought the Ark into Jerusalem, which the Chronicler covers in chapter 13 and then again starting in chapter 15. He's rearranged the order on purpose. Why? Because he wants you to see something: even in the awkward gap after the Ark disaster with Uzzah (chapter 13), while David is figuratively holding his breath, God keeps blessing him anyway — a palace, sons, military victories. David's security never depended on having his religious life perfectly arranged first Tyndale. That's a striking, almost uncomfortable truth sitting quietly under the surface.

The turn of the chapter is verse 2: "David realized that the LORD had established him as king." Everything before it (Hiram's gift) and after it (the family, the wars) gets read through that lens — not "look how great David is" but "look how clearly God is behind this." Even the family list, which includes the loaded name Solomon, is quietly pointing forward to where this book is actually headed: the temple, built not by David but by his son.

The two Philistine battles aren't filler — they're a matched pair to show growth. In the first, David wins the same way every time God fights for Israel: head-on, decisively. In the second, God gives a completely different, stranger battle plan — circle around, wait for a sound in the trees. The Chronicler wants you to notice: David doesn't run last year's playbook. He asks again Strong's.

Where readers disagree: some see verse 3's "more wives" as simply reported neutrally, a mark of ancient royal status; others (rightly, I think) hear a small warning note, since multiplying wives is exactly what Deuteronomy 17:17 tells kings not to do — a seed that will bear ugly fruit later in David's story Matthew Henry.

1 & 2 Chronicles were most likely written after the Babylonian exile — when Nebuchadnezzar's army destroyed Jerusalem and its Temple in 586 BC and marched the surviving Israelites off to Babylon — probably sometime in the 400s BC, after a remnant had returned home under Persian permission. The audience is a small, discouraged community trying to rebuild a life, a city, and a Temple out of rubble and memory. They don't need a history lesson; they need hope that God hasn't abandoned the promises he made to David's line.

That's why the Chronicler tells David's story differently than 2 Samuel does — he skips David's worst failures (the affair with Bathsheba, the family collapse that follows) and highlights God's covenant faithfulness and the establishment of worship. This chapter's material about Hiram of Tyre and the Philistine wars is lifted almost directly from 2 Samuel 5:11-25, but repositioned here to make a theological point about timing.

Hiram of Tyre ruled a wealthy Phoenician trading city on the Mediterranean coast, famous for its cedar forests, skilled builders, and sea trade — a superpower of craftsmanship even if a minor military power. His alliance with David (and later Solomon, 2 Chronicles 2:3) was a real diplomatic and economic partnership, not just a courtesy Jamieson-Fausset-Brown. The Philistines, meanwhile, were Israel's longtime rivals along the coastal plain, the same people who'd captured the Ark decades earlier and who had killed Saul. Their raid into the Valley of Rephaim, just southwest of Jerusalem, was a direct challenge to David's brand-new, still-fragile kingship — a test of whether this newly anointed king could actually hold the throne Adam Clarke.

In verse 2, David "realized" (יָדַע, yada, H3045) that the LORD had "established" (כּוּן, kun, H3559) him as king. Yada isn't casual noticing — it's the same word used for intimate, experiential knowing. David didn't just infer this from good luck; he perceived it the way you know something is true in your gut. And kun means to make something stand firm, upright, unshakeable — the picture is of a shaky tent pole finally driven deep and steady.

In verse 10, David "inquired" of God (שָׁאַל, sha'al, H7592) — the same root that gives Saul (Sha'ul) his name, ironically, since Saul rarely bothered to ask God anything before acting. David asks twice in this chapter (verses 10 and 14), and both times uses this same verb — it's a rhythm, a habit, not a one-off crisis prayer.

The battle name in verse 11, Baal-perazim (בַּעַל פְּרָצִים, H1188), literally means "possessor of breaches" or "lord of the bursting-through," built from the verb paratz (פָּרַץ, H6555), to break out violently — like a river bursting a dam Strong's. David's own words play on this: "God has burst out against my enemies" — he names the place after the very verb God used on his enemies, turning a battlefield into a monument to a specific action of God.

And notice verse 12: when the Philistines "abandoned" (עָזַב, azab, H5800) their gods, David burns them. The word for "gods" here (אֱלֹהִים, Elohim, H430) is the exact same word used for the true God throughout the chapter — a sly, almost mocking contrast between the God who actually shows up and answers (verses 10, 14) and the gods that get left behind in the dirt.

The clearest thread runs through Solomon's name quietly tucked into verse 4's list of sons. Solomon (שְׁלֹמֹה, Shelomoh, H8010) means "peaceful," from shalom. He's the son through whom God's promise to David — that his house and throne would be established forever ( 2 Samuel 7, echoed in 1 Chronicles 17:1) — begins to be worked out, and he's the one who will build the Temple with the very cedar Hiram sent ( 1 Kings 5:6-18, 2 Chronicles 2:3). But Solomon's peace is temporary and his kingdom eventually splits and falls. Matthew's Gospel opens by tracing Jesus straight through this family line ( Matthew 1:6-7) precisely because Jesus is the greater Son of David who actually secures what Solomon only foreshadowed — a kingdom and a peace that doesn't end.

There's also a quieter echo in the pattern of the two battles. David wins the first fight head-on, but the second only by watching for God to move first — "this will mean that God has marched out before you" (verse 15). That posture — waiting to see the Father act and then moving — is exactly what Jesus describes as the shape of his own life: "the Son can do nothing by himself; he can only do what he sees his Father doing" ( John 5:19). David's second battle isn't a proof-text about Jesus, but it's the same family resemblance: a king who wins not by his own cleverness but by staying attached to God's initiative.

And the burned idols in verse 12 point forward, faintly, to the far larger and final victory where every false god, every rival throne, gets stripped of its power — something the New Testament pictures as complete only in Christ's own reign ( 1 Corinthians 15:24-25).

Here's what gets me every time I read this chapter: David asks. Twice. Even after the first battle went exactly the way God said it would, he doesn't assume he knows the playbook for round two. He asks again — and God gives him a completely different plan, one that requires waiting for a sound in some trees before he moves a muscle.

That's the cost this chapter is quietly asking of you. Not heroics. Not a bigger faith than you have. Just the discipline of not running on autopilot with God — of not assuming that because he worked one way last time, he'll work the same way this time. How many of you pray once, get an answer, and then just apply that same answer to every future situation without ever asking again? I do it constantly. It's efficient. It's also a way of quietly stopping the relationship.

And notice what David does before any of this — he lets Hiram's kindness and his own success land on him not as "I've made it" but as "God has established me" (verse 2). That's a discipline too: refusing to let blessing turn into self-congratulation. Then, a few verses later, we watch him take more wives — the one place in this chapter where the man who just correctly perceived God's hand starts quietly writing his own rules Matthew Henry. That's not an accident either. It's how fast a person can go from clear-eyed dependence to careless drift, sometimes in the space of one paragraph.

So here's the honest question this chapter puts to you: where in your life have you stopped asking, because you already think you know the answer? And where has success made you a little too comfortable rewriting the rules for yourself?

• Lord, help me actually notice — like David did — the places where you've established and steadied things in my life that I've been taking for granted.
• Teach me to keep asking you, even in situations where I think I already know what you'll say.
• Show me the "more wives" moments in my own life — the places where success has made me start writing my own rules instead of staying dependent on you.
• Give me the patience to wait for you to move first, like David waiting for the sound in the trees, instead of always charging ahead on my own timeline.
• Thank you that you don't wait for me to have my whole spiritual life in order before you keep blessing and using me.

• Where in your life have you stopped asking God for direction because you assume you already know the answer?
• Can you name a time success or blessing quietly made you more careless with obedience rather than more grateful?
• What would it look like this week to wait and watch for God to "move first" instead of forcing your own plan?
• Who are the "Hirams" in your life — outsiders or unlikely people God has used to bless you — and have you actually thanked God for them?
• Is there a "false god" (not literal idols, but a source of security) that you've been slower to burn than you should be?