By Larry Barnes in 2 Samuel — 16 Feb 2026

2 Samuel 11

02/16/2026

I have just finished reading 2 Samuel 11 NKJV. Since Uriah was a Hittite, was he probably one of David's Cherethites or Pelethites?

No, Uriah the Hittite was not one of David's Cherethites or Pelethites.

The Cherethites and Pelethites formed a distinct group in David's forces, repeatedly described as his personal bodyguard or royal guard (e.g., 2 Samuel 8:18; 20:7, 23; 1 Kings 1:38, 44). They were under the command of Benaiah son of Jehoiada and were foreign mercenaries—likely of Philistine or related origin (possibly Cretan for the Cherethites, and Philistine-linked for the Pelethites). They functioned as an elite protective unit, often mentioned separately from the main army or other elite fighters, and included groups like the Gittites (Philistines from Gath) in some contexts (2 Samuel 15:18).

Uriah the Hittite, by contrast, is explicitly listed among David's mighty men (also called "the Thirty" or the elite warriors), a separate group of about 37 highly valiant individual fighters renowned for battlefield exploits (2 Samuel 23:8–39; 1 Chronicles 11:10–47). In those lists, Uriah appears by name as the final entry: "Uriah the Hittite: thirty-seven in all" (2 Samuel 23:39 NKJV; similarly in 1 Chronicles 11:41). These mighty men included a mix of Israelites and foreigners (e.g., Zelek the Ammonite, Ithmah the Moabite), but Uriah is categorized among them, not with the Cherethites/Pelethites.

The Bible distinguishes these units:

The mighty men (including Uriah) were celebrated individual heroes integrated into Israel's forces.
The Cherethites and Pelethites were a standing bodyguard corps of foreign origin, not individually named in the heroic lists.

Uriah's Hittite background (likely from a remnant Hittite community in Canaan, possibly a convert or proselyte given his marriage to Bathsheba and Yahwistic name meaning "Yahweh is my light") made him a foreigner like some others in the mighty men, but he belonged to that specific elite warrior group, not the Cherethite/Pelethite guard. No biblical text or scholarly source equates or connects him directly to the Cherethites or Pelethites.

I have read this account many times and I know the story fairly well. Obviously, the first problem is that David did not go to war with his troops, but rather stayed behind for some unknown reason. I wonder if years of victory and kingship made him a little lazy and perhaps arrogant, thinking he was better than that.

That's a keen observation, and it's one that aligns with how many biblical scholars interpret this pivotal moment in David's story. The text in 2 Samuel 11:1 deliberately contrasts the expectation—"at the time when kings go out to battle"—with David's choice to send Joab and the army while he "remained at Jerusalem." This wasn't the norm; as king and a proven warrior, David had personally led his forces in prior campaigns (like against the Arameans in 2 Samuel 10:17), so his absence here stands out as unusual and sets the stage for the tragedy that follows.

Commentators often point to this as a symptom of complacency or overconfidence bred from years of triumphs and royal privileges. After establishing his kingdom through battles, alliances, and God's favor, David may have grown accustomed to delegating the gritty work, opting instead for the comforts of the palace. This "fatal dalliance in sensual ease," as one writer puts it, could reflect a subtle arrogance—thinking himself above the fray or indispensable enough to stay back without consequence. Others describe it as spiritual lethargy or self-reliance taking hold, where the once-vigilant shepherd-warrior lets his guard down amid prolonged success. It's framed not just as laziness, but as a sin of omission: neglecting his duty as leader, which opens the door to idleness and temptation.stbenedictstable.ca

The narrative doesn't spell out an explicit motive, leaving room for this kind of reflection, but the implication is clear—David's decision wasn't strategic or forced; it was a personal lapse that spiraled into adultery, deception, and murder. It's a stark reminder of how even the "man after God's own heart" could falter when prosperity dulled his edge.

This is a prime example of the old adage I've heard since childhood, "Idle hands are the Devil's workshop."

Yes, Larry, the old adage "Idle hands are the devil's workshop" fits David's situation in 2 Samuel 11 almost perfectly—it's a classic illustration that many preachers, commentators, and Bible teachers draw on when unpacking this chapter.

The saying itself isn't a direct quote from Scripture (its closest biblical parallel appears in a paraphrase of Proverbs 16:27 in The Living Bible: "Idle hands are the devil's workshop; idle lips are his mouthpiece"), but the principle is deeply rooted in biblical wisdom. Proverbs repeatedly warns against laziness and idleness leading to trouble (e.g., Proverbs 19:15: "Laziness casts one into a deep sleep, and an idle person will suffer hunger"), and passages like 1 Timothy 5:13 and 2 Thessalonians 3:11 show how being unoccupied can open doors to gossip, meddling, or worse sins.

In David's case, commentators frequently apply the proverb directly: his decision to stay behind in Jerusalem—lounging on his couch, wandering the rooftop instead of leading his army—created the perfect vacuum for temptation. What started as idleness escalated into lust, adultery, cover-up, and murder. As one commentary puts it, "If idle hands are the devil's workshop, then the idleness we detect in David in this chapter leads to a great deal of mayhem indeed." Others note that his greatest moral failure began not with lust per se, but with laziness and a lack of purposeful engagement in his God-given responsibilities.

It's a sobering reminder that prosperity and success can sometimes breed the very complacency that invites downfall. Staying busy in meaningful work—whether kingdom duties, family, service, or pursuing God's calling—serves as a safeguard. David's story shows how quickly an idle season can turn destructive if we're not vigilant. You've nailed a timeless truth here that still resonates today.

I experience this regularly, since my wife has passed. I tend towards laziness around the house, trying to occupy my time with television. It seems laziness breeds laziness. Thankfully, I have a job that makes me leave the house during the week, so that limits the down time, but the weekends can get brutal. I am working on more activities to occupy my time and my mind.

I'm really sorry for your loss, Larry—losing your wife is one of the deepest kinds of grief, and it's completely understandable that weekends feel especially heavy when the routine of work isn't there to pull you out the door. That cycle you describe—laziness breeding more laziness, especially with TV as the default—is something so many widows and widowers talk about. The house feels emptier, the silence louder, and it's easy to slip into idleness that just amplifies the loneliness and low energy. But you're already taking a positive step by recognizing it and actively working on more activities to occupy your time and mind. That's huge; it shows resilience and a desire to keep moving forward, even when it's hard.

From what others who've walked this path share (in grief forums, articles, and support communities), weekends often hit hardest because they're when couples traditionally spent time together—errands, relaxation, shared meals—and without that, the void stands out sharply. Many describe it as feeling "forgotten" by others who are busy with their own families, which compounds the isolation. The good news is that small, intentional shifts can help break the inertia without overwhelming you.

Here are some gentle, practical ideas that come up repeatedly from people in similar situations:

Start small with one planned thing per day: Even 30–60 minutes outside the house can shift the momentum. A walk in a park, coffee at a local spot, visiting a library or botanical garden, or running a simple errand (like grocery shopping with no rush) gets you moving and changes the environment. Being "lonely but occupied" often feels more bearable than lonely at home staring at walls or screens.
Build in structure or rewards: Some folks treat a small task (like a short bike ride, yard work, or visiting a meaningful place) as a "chore" followed by a treat—maybe your favorite dessert or a favorite podcast/audiobook on the way home. It creates a sense of accomplishment and breaks up the day.
Lean into faith-based or community options: Since our earlier conversation touched on biblical principles, things like attending a weekend Bible study, men's group at church, or even volunteering (if it fits your schedule) can provide purpose and connection. Scripture encourages diligence and purpose (e.g., Proverbs 6 warns against sluggardly ways, while Colossians 3:23 reminds us to work heartily as for the Lord), but grace is there too—grief isn't laziness; it's a heavy burden, and God understands the struggle.
Creative or solo-friendly outlets: Journaling about memories of your wife (honoring her), listening to podcasts/audiobooks while doing light chores, exercising at a gym, or pursuing a hobby (reading, gardening, woodworking) can engage your mind productively. If you're open to it, online grief support groups (like those for widowers) or local meetups can offer understanding without pressure.
Reach out proactively: It's tough, but asking a friend, family member, or church contact for a walk, meal, or call can help. Many people want to support but don't know how—telling them "Weekends are rough; could we grab coffee Saturday?" opens the door.

You're right that your weekday job is a built-in safeguard—thank God for that structure. And the fact that you're "working on" more activities shows you're not resigned to the cycle; you're fighting it. Grief doesn't have a timeline, and some days will still be brutal, but filling time with meaningful (even small) things can slowly rebuild a sense of purpose and reduce that downward spiral.

It has been 8 years since she passed, so the grief is not as bad, but there is still the loneliness, and laziness. Anyway, I am not here to talk about that. As I said, I am well familiar with this story, and it seems that today, my lesson is a warning against laziness and idle hands. I need to put forth an extra effort to combat this to help keep me on the straight and narrow.

That's a solid takeaway from the story, Larry—seeing David's lapse in 2 Samuel 11 as a clear warning against the dangers of idleness and the "idle hands" principle. It's powerful that you're letting it spur you toward extra effort right now, especially in staying on the straight and narrow path. The Bible doesn't mince words on this: laziness isn't just harmless downtime; it creates openings for temptation, decay, and missed opportunities to honor God through purposeful living.

Scripture is full of encouragement to combat that pull toward idleness with diligence, often framing it as a choice that leads to blessing, provision, and spiritual strength. Here are some key verses that directly address this battle—many from Proverbs, where the contrast between the sluggard and the diligent is stark, plus a few from the New Testament that tie it to living for the Lord:

Proverbs 6:6-11 — "Go to the ant, you sluggard! Consider her ways and be wise... A little sleep, a little slumber, a little folding of the hands to rest—and poverty will come upon you like a robber, and want like an armed man." (A vivid call to observe diligence in nature and avoid the slow creep of laziness.)
Proverbs 10:4 — "He who has a slack hand becomes poor, but the hand of the diligent makes rich."
Proverbs 13:4 — "The soul of the sluggard craves and gets nothing, while the soul of the diligent is richly supplied."
Proverbs 14:23 — "In all toil there is profit, but mere talk tends only to poverty."
Ecclesiastes 10:18 — "Through laziness the roof sinks in, and through idleness of hands the house leaks." (This one echoes the consequences of neglect, much like how David's idleness led to his household falling into chaos.)
Colossians 3:23-24 — "Whatever you do, work heartily, as for the Lord and not for men, knowing that from the Lord you will receive the inheritance as your reward. You are serving the Lord Christ." (This shifts the motivation—doing even small tasks with excellence as worship.)
Romans 12:11 — "Do not be slothful in zeal, be fervent in spirit, serve the Lord." (A direct antidote: stay fervent and active in service.)

These aren't just warnings; they're invitations to a better way—diligence that brings fulfillment, guards against sin, and aligns with God's design for us. David's story shows how quickly idleness can snowball, but it also points to repentance and restoration (as we see later in his life). You're already ahead by recognizing the pattern and committing to push back with extra effort. Practical steps like planning one purposeful activity (a walk, a project, Scripture reading, or reaching out to someone) can build that momentum, turning the tide one day at a time.

Praying you feel strengthened in this resolve today—God's grace is there to help you "work heartily" and keep those hands busy for good. If there's a particular verse or area you'd like to dig into more, just say the word.

Thank you.

You're very welcome, Larry. I'm glad the conversation was helpful, and I appreciate you sharing how the story spoke to you today.

May God give you strength and fresh motivation as you put forth that extra effort—whether it's tackling a small task around the house, opening your Bible, or stepping out for a walk. One purposeful step at a time really does make a difference.

A later addition, after I posted the above portion.

I find it quite ironic that David, this great man of integrity, had his plans to hide his great sin thwarted by another man of great integrity, to the point that it drove David to commit the even greater sin of murder to hide what he had done.

Yes, Larry, the irony you point out is one of the most striking and sobering elements in the entire narrative of 2 Samuel 11—it's highlighted repeatedly in biblical commentaries as a profound reversal that exposes the depths of David's moral collapse.

David, the man Scripture calls "a man after [God's] own heart" (1 Samuel 13:14; Acts 13:22), the anointed king who had shown extraordinary integrity in refusing to harm Saul twice (1 Samuel 24; 26), now finds his elaborate scheme to conceal adultery thwarted not by an enemy or a rival, but by the unwavering integrity of one of his own loyal warriors. Uriah the Hittite— a foreigner by birth, yet fully integrated into Israel's covenant community—refuses to enjoy the comforts of home (eating, drinking, and lying with his wife) while his comrades endure hardship in the field. His words in 2 Samuel 11:11 cut straight to the heart: "The ark and Israel and Judah dwell in tents... my lord Joab and the servants of my lord are encamped in the open fields. Shall I then go to my house to eat and to drink and to lie with my wife? As you live, and as your soul lives, I will not do this thing" (NKJV).

This declaration isn't just polite loyalty; it's a vivid expression of self-denial, solidarity with the troops, and commitment to covenant faithfulness—qualities that David himself had once embodied as a fugitive and warrior. Commentators often describe Uriah as a "perfect Good Soldier of Israel," whose righteousness stands in sharp, ironic contrast to the king's self-indulgence and betrayal. A Hittite (from a people Israel had displaced) models the very covenant ethics that the Israelite king abandons. As one puts it, the sober king acts wickedly while the (later) drunk soldier remains righteous—even getting Uriah intoxicated doesn't break his resolve.

David's initial plan was clever in a worldly sense: summon Uriah, send him home to sleep with Bathsheba, and let paternity cover the sin. But Uriah's integrity makes that impossible. Instead of prompting repentance, it infuriates David and escalates the sin—from adultery and deception to conspiracy and murder (arranging Uriah's death via Joab in 11:14–17). The very man whose honor should have convicted David instead becomes the victim whose death David orchestrates to silence the threat.

This escalation shows how sin, when unrepented, doesn't stay contained—it compounds, dragging the sinner deeper and harming the innocent. Uriah becomes a casualty not just of battle, but of David's desperate cover-up. Later, 1 Kings 15:5 summarizes David's legacy as one who "did what was right in the eyes of the Lord... except in the matter of Uriah the Hittite," underscoring how this episode became the defining stain on an otherwise faithful life.

The irony serves as a powerful warning: even the greatest can fall when they drift from vigilance, and God often uses the faithfulness of others (even unlikely ones) to expose hidden sin. It echoes the broader biblical theme that attempts to hide wrongdoing are futile—sin will find us out (Numbers 32:23), and God's justice prevails. Yet the story doesn't end in despair; David's eventual repentance (Psalm 51) shows that deeper grace awaits those who turn back.

It's a gut-wrenching chapter, but one that reminds us why we need constant dependence on God to guard our hearts. Your observation captures the tragic heart of it beautifully.

I think the end of verse 27 is the saddest of David's story, if not most of scripture. I hope to never have it said of me, but I know I do things everyday that displeases the Lord. I am grateful for His Love, Mercy, and Grace that allows me the opportunity to repent and return to Him.

Yes, Larry, that closing line in 2 Samuel 11:27—"But the thing that David had done displeased the LORD" (NKJV)—lands with such understated weight that many readers and commentators call it one of the most heartbreaking and sobering verses in Scripture. After the detailed account of David's calculated steps—adultery, deception, murder, hasty marriage, and the birth of a son—the narrative doesn't dwell on drama or excuses. It simply states God's verdict in plain, piercing words. No fanfare, no elaboration—just the quiet declaration that the God who had exalted David, who had called him "a man after My own heart," was deeply grieved by what he'd done.

Commentators often highlight how this verse serves as the pivot: everything before it explains the sin, and everything after (chapter 12, Nathan's confrontation, the consequences) flows from God's displeasure. It's described as the climax of the chapter, the divine commentary that cuts through any illusion of success or cover-up. One writer notes it as a moment where God is "trembling within, sick to His stomach"—a vivid way to capture how profoundly sin wounds a holy God. Another calls it "one of the saddest chapters" summarized in this single, understated sentence. The fact that God is mentioned for the first time in the entire chapter only here underscores how absent He'd seemed in David's actions—yet He was watching all along, and His eyes see what human eyes miss.

Your reflection captures the heart of it so well: hoping never to have that said of us, yet knowing we fall short daily in ways big and small. David's story isn't just ancient history; it's a mirror. He, the giant-slayer, psalmist, and king, descended to this low point through complacency and unchecked desire. Yet what makes the gospel shine through the tragedy is exactly what you mentioned—God's love, mercy, and grace that open the door to repentance. David didn't stay in denial forever; when confronted, he owned it fully: "I have sinned against the LORD" (2 Samuel 12:13). And God responded with forgiveness, even though the consequences lingered (the child's death, ongoing turmoil in his house). Psalm 51, born from this very failure, becomes one of the most profound prayers of confession and restoration in all Scripture: "Create in me a clean heart, O God... Restore to me the joy of Your salvation."

That same mercy is extended to us. As 1 John 1:9 promises, "If we confess our sins, He is faithful and just to forgive us our sins and to cleanse us from all unrighteousness." We don't earn it; it's grace upon grace. Your daily awareness of displeasing the Lord, paired with gratitude for His forgiveness, is itself a mark of a tender conscience—much like David's eventual response. It's not about perfection but about turning back quickly when we stray.

Thank you for sharing such an honest, faith-filled insight. This chapter reminds us why we need a Savior daily, and why His grace is never exhausted. May it keep stirring that resolve in you to walk humbly and gratefully before Him.

That phrase makes me think of my Dad. When I did something wrong, I would far more rather him get upset, raise his voice, or spank me. Get it over with. The absolute worse was when he wouldn't look at me and I knew I disappointed him. That broke me worse than any spanking.

That's a powerful and relatable analogy, Larry—the kind of deep, quiet disappointment from a loving father that hurts far more than any raised voice or punishment. Many people describe it exactly that way: the silent treatment, the averted eyes, the heavy sigh that says, "I'm not just angry; you've broken my heart." It's the weight of knowing you've let down someone who believes in you, who has invested so much in you. That kind of pain cuts straight to the core because it comes from relationship, not just rules.

Your memory of your dad mirrors so closely what commentators often highlight about 2 Samuel 11:27 and God's response to David's sin. The verse is deliberately understated—no thunder, no immediate lightning bolt, just that simple, piercing statement: "But the thing that David had done displeased the LORD." It's like God turning away in grief rather than exploding in fury right then. Scholars describe it as divine heartbreak: God, who had poured out such favor on David (calling him a man after His own heart, establishing his kingdom, promising an eternal dynasty), now feels the sting of betrayal from His beloved son. One commentary likens it to a parent who, after investing everything in a child, can only ask "Why?" in deep hurt—echoing Nathan's later words in chapter 12. It's not explosive anger but a profound, personal disappointment that grieves because of love.

That silence before Nathan's confrontation (months of pregnancy passing without overt rebuke) must have felt like the heaviest kind of disapproval—the Lord withholding the usual signs of favor, letting the weight of conscience settle in. David knew he'd displeased his Heavenly Father, much like you knew with your earthly one. And just as your dad's quiet disappointment "broke" you more effectively than a spanking (leading, I imagine, to genuine sorrow and change), God's displeasure ultimately led David to brokenness and repentance in Psalm 51: "Against You, You only, have I sinned... Create in me a clean heart, O God."

It's a reminder that God's "displeasure" isn't cold rejection—it's the ache of a Father who loves us too much to let sin slide without consequence, yet loves us enough to pursue restoration. The same God who was grieved by David's failure is the One who sent His Son to bear the full weight of that displeasure so we could be welcomed back with open arms. Your gratitude for His mercy and grace fits perfectly here: we don't deserve the quick "get it over with" punishment sometimes; we need the deeper work that comes from realizing we've disappointed the One who loves us most.

Thank you for sharing that personal connection—it's moving, and it makes the Scripture come alive in such a real way. May the memory of your dad's love (and the Lord's) keep stirring that tender conscience in you, drawing you closer rather than driving you away.