Showing posts with label life. Show all posts
Showing posts with label life. Show all posts

Monday, October 28, 2024

Number Our Days

My family recently had the pleasure of taking a vacation to the beach with some dear friends.  It was especially meaningful because these days, with both our sons working and doing the college thing, it can be hard to get us all in to the same place for 30 minutes, much more so for several days.  I'm grateful for every such opportunity we have.

Because our trip spanned a Sunday, we did as we've done for years in such situations and planned to have our own Sunday worship session.  Usually one of us Dads will prepare and share a devotion, and we spend a little time in prayer and musical worship.  This time around, I volunteered the lead the devotion, and set about praying and considering what might be of particular relevance to our families in this season.  "This season" is more than just another milestone along the course of our collective aging.  We've recently endured quite a bit of heaviness between our families, including the death of a mother/grandmother and the wildly destructive Hurricane Helene (which is what brought us to the beach in the first place, since the mountain vacation we'd already planned became a non-option).

It's a bit challenging to convey all that went into my consideration of a text to focus on, but there were several key things.  It started, of course, with the weight and near reminder of how close death can be.  But beyond that, I'd had recent conversations about how the more melancholy worship songs (some of which are musically lovely!) always feel out of place in a Sunday morning service, at least in my denominational context.  The book of Psalms has such songs, so songs of sorrow are completely relevant and legitimate for congregational worship.  I recalled that the Church has had for many years a mechanism for touching on all the various valid emotions of the Christian life:  cyclic, planned liturgies.  On a whim, I looked up the Anglican liturgical calendar to see what readings were scheduled for our Sunday away.  Almost unsurprisingly, they were all readings focused on sorrow.

Two other things happened while at the beach that narrowed my search into a decision.  While walking in a beach souvenir shop, the overhead radio program (featuring John Tesh) was musing about midlife crises.  I was only half paying attention, but I heard Tesh saying something about age 40 being the halfway point of the average lifespan.  Then the following day, I took a solo side quest up to Southport, where I spent some time poking around an interesting cemetery.  (In a fun plot twist, I later went off to find a multi-stage geocache that led me around town picking up clues, and the final destination turned out to be none other than that same cemetery.)  There I noted the ages on many of the headstones — people dying at age 60. 40. 21. 18. 7. 1. Even a trio of three-month-old children laid in a row.  My thoughts kept returning to just how fleeting life is for us.  And that was all I needed to secure a text for our Sunday morning devotion.  Without yet knowing where the study would lead, I chose Psalm 90.

I won't attempt to recount the whole devotion here, but as I studied the text over the next half-day, I couldn't avoid seeing phrases and themes that reminded me of the Genesis accounts of Creation and the Fall.  Themes of toiling, day after day; literary hints such as the morning and evening cycle; an eventual return to dust — all point to Genesis 1-3.  A Psalm that at first glance might appear to picture an arbitrarily wrath-filled God is reminding us that because of the first sin, the earth and its inhabitants are under a curse.  God hates sin.  It was sin that introduced death into Creation in the first place.  And the Psalm (with a bit more authority than Mr. Tesh) reminds us that life is roughly 70 years long — 80 if you're lucky.

After reading and commenting a bit on the Psalm that Sunday morning, I employed an unconventional analogy in order to help our families consider what "80 years" looks like.  If life is a pizza with eight slices, our family members' ages fell pretty neatly into clean "slice counts".  My daughter is 10 — one of her slices is already gone.  The older boys' ages hover around 20 — two slices gone.  Jason and Cassandra (the parents in the other family) have consumed half of their pizza.  And Amy and I are down to just three slices left.  This is a sobering thought, and is surely why Psalm 90's final section asks of God, "So teach us to number our days that we may get a heart of wisdom."

Father in Heaven, teach us to number our days that we may get a heart of wisdom.  Have pity on us.  Satisfy us in the morning with your steadfast love, that we may rejoice and be glad all our days.  Amen.

Wednesday, September 4, 2024

Ten Commandments of Dating

Some years ago, as my sons were approaching the age at which words like "girlfriend" and "dating" were being used more often, I began thinking through what a biblical framework for dating might look like. This is not the most obvious enterprise because the Bible was written to a culture wildly different than our modern western society, with patterns and norms for establishing relationships of this sort that look nothing like those we experience today. Still, I was convinced that the Bible carried principles that reflect the character of God and His intention for all people across all of time, so I turned to what I felt was the most obvious place – the Ten Commandments.

The Ten Commandments are of course pretty widely known, and are both respected and recognized for what they are: brief summary statements that encapsulate many deep layers of thought and consideration.  From these ten basic commandments would flow another 600+ more detailed laws given to the Israelites through Moses, which would then give way to countless codified interpretations and applications over the years as the nuance and complexity of society would give rise to such a need.

What follows here is my attempt to apply the basic principles of the Ten Commandment to the realm of pre-marital romance.  The document carries a heavy Christian slant (for which I make absolutely no apology) and is written from a first-person perspective, as if each party in the relationship was speaking his or her commitment to these principles to the other party.

Wednesday, August 28, 2019

Oreos and Milk Done Right

For far too long, I've held an absolutely essential piece of knowledge—a life skill that every person should have—and I've failed to share it with the world.  Today I repent of that, beg your forgiveness, and offer reparation by sharing with you now this critical information.  Today, I want to tell you the proper way to eat Oreos with milk.

It goes without saying that in order to accomplish this, you'll need Oreos, milk, and a cup or mug to contain the milk.  But lest we assume too much, let me clarify some things.
  • These instructions assume you can eat an entire Oreo in one mouthful.  If you can't, you're clearly not built for eating Oreos and should probably take up Veggie Straws or something else instead.
  • Don't use a cup or mug that's too small.  You need at least a depth of milk sufficient to completely submerge the cookie.  And you need enough width in your container to do the same.
  • Don't use skim milk.  The higher the fat content of the milk, the better.  I strongly suggest whole milk.  And don't use warm milk.  You want your milk as cold as possible.  If, when you pour your milk, it looks like Elmer's white glue and chills the hand that holds your cup or mug, that's a good sign.
  • Don't use fake Oreos.  Seriously.  I'm all for generic brands of most things, but ... no.
Okay, on to the life-changing instructions.

First, grasp an Oreo cookie between your thumb and forefinger, with each making contact on one of the Oreo logos on either side of the cookie.  (If you don't see an Oreo logo, you're using fake Oreos.  And I literally just told you not to do that.)  Put some real pressure on the cookie with your fingers—not enough to crush it, but pretty close to it.  Now, submerge the Oreo completely in the milk while maintaining this pressure.  Yes, your fingers are going to get wet—deal with it.

All this might sound pretty obvious, but as any seasoned Oreo-milk-dunker knows, the trick is figuring out how long to keep the cookie submerged.  And you might be wondering why must we maintain this solid finger pressure on the cookie.  After all, they hardly weigh anything and are unlikely to attempt to escape our grasp on their own.

The answer lies in the sheer importance of getting these two seemingly incompatible foods—one a natural byproduct by which nearly all mammals are initially nursed; the other a completely unnatural, highly processed junk food—to unite properly at or near the molecular level[*].  If your Oreo is in the milk for too short a time, then what was the point?  You're merely eating a damp Oreo.  But to linger for too long will have you watching your disintegrating cookie's disparate parts sinking out of sight into the milky white abyss.

As it turns out, the pressure you're putting on those Oreo logos gives you all the tactile feedback you need to know exactly when to remove the cookie from the milk.  As soon as that logo begins a crush a bit under your firm-but-non-damaging bit of finger pressure, the time is right.  Remove the cookie from the milk, shove it into your awaiting mouth, and rejoice as you've never rejoiced before.

Once again, this is not for those who lack a certain degree of fortitude.  Your thumb and forefinger will get wet with milk.  They will also pick up the debris of the crushed Oreo logos.  You'll have to open your mouth a bit wider than high society might advise.  Sometimes, doing things properly involves some risk-taking.  This is such a time.

Now, there's no need to e-mail me your thanks.  It's my great pleasure to serve my fellow man in this way, sharing the results of my years of experimentation in this field.  My hope is simply that you'll do the same.

Oh!  But I nearly forgot the final step in the instructions:  grab another cookie and repeat!

[*] No real scientists were consulted while authoring this article.

Wednesday, August 31, 2011

The emotional sine wave of church volunteerism

Tonight was one of those nights. Not universally grand; not universally challenging. Just back and forth between those extremes at a break-neck pace.

4:04pm: Leave home to head to church.

4:12pm: Hear a loud pop and see an unknown object fly out from behind my car.

4:13pm: Arrive at church, get music stuff setup for adult worship practice.

4:16pm: Begin moving drums, etc. over to the youth building for youth worship. Notice that my passenger side rear tire is completely flat.

4:35pm: Adult worship practice. My timing is way off this afternoon. Bummer.

5:10pm: Move self, guitar, and youth ministry laptop to youth building for youth music practice.

5:12pm: Youth ministry laptop has crashed. Now in an endless boot loop. No time to fix it—need to practice youth worship music with the others.

5:56pm: Youth worship practice was good, but we have no way to project song lyrics. Move guitar back to worship center for adult worship tonight. Arrange to borrow netbook from Pastor for youth music tonight.

6:02pm: Slam down a quick dinner. Encouraging comment from a church member about recent worship song selections.

6:15pm: Pastor delivers netbook. Download slides (which I'd fortunately stuffed onto a remote server before the youth ministry laptop died), carry to youth building, and setup for projection.

6:25pm: Back in worship center, ready for adult worship. Shoot! Forgot something on the netbook. Head back to youth building.

6:28pm: Final tweaks on netbook. Back to the worship center.

6:35pm: Help lead adult worship. (Great singing tonight, congregation!)

6:45pm: Back to youth building.

7:02pm: Help lead youth worship. (Great participation here, too. Sweet!)

7:30pm: Return netbook to Pastor. Change tire on my car with a friend.

7:42pm: Store guitar and music away.

7:46pm: Start cleaning up youth building music stuff. (Why did somebody leave a cooler with water in it in the youth room? Mildew experiment?)

8:24pm: Head home. Me, my sons, and my donut-sporting car.

Net emotional state, when it was all said and done: Quite positive. Stuff happens. Computers fail at the worst possible time—count on it. Tires blow. Schedule contention happens. And yet I was able to experience not just one group of people singing praises to God tonight, but two! That's enough to make it all right for me.

Special thanks to: Josh, for the extra hand with tire; Erica, Emily, and Camden, for the lovely youth music tonight; Jim, for the encouragement; John, for the netbook save; Mary and Sharon, for working around my schedule tonight; and Barbara, for keeping the whole lot of us sane.

Wednesday, November 25, 2009

Reflections of a Newbie Youth Soccer Coach

This past weekend, my sons' youth soccer seasons ended. My oldest practiced and played in a division for 5- and 6-year-old kids, and I assisted his head coach. My youngest practiced in a division for 3- and 4-year-old kids, and I was the head coach of his team. I wanted to write up some thoughts about the seasons from a coach's point of view. As you read these, if they sound more like parenting advice, there's a reason for that: many times over the course of the season, I noticed (and noted to others) parallels between coaching to parenting. I found that many of the basic principles commonly applied in one role remain valid and useful in the other. Mind you, I'm certainly no expert coach. Not by a long shot. (For that matter, I'm no expert parent, either.) But these are some of my observations, and I'm hoping that perhaps something here resonates with other folks who — like me at when this year began — have never coached at all.

Teams are best built atop friendship

An observation I made at during the Spring soccer season was that by the middle of the season, the players on the team I was helping to coach (which, as in the Fall season, consisted of 5- and 6-year-old boys and girls) still didn't know each others' names. This bothered me deeply, because at a minimum it meant that the players couldn't communicate effective to or about each other. But it also meant that somewhere between showing how to dribble a soccer ball and how to perform a proper throw-in, we as coaches had overlooked the simple fact that children are social beings. My son has a distinct “cautious observer" personality type. Until he's comfortable around his peers, he'd rather just watch to see if it's safe to engage. Not even knowing your peers' names does not encourage comfortability.

This season, we as coaches worked to remedy this problem up front. A helpful parent took a team photo, and we labeled it with each child's name, had Wal-mart print up enough copies for everyone, and distributed them. During practices we often encouraged the players to cheer for each other by name. The result was noticeable (to me, at least). There was much more of a team spirit on the field and off, and sometimes it was actually difficult to get my son away from the fields because he was having so much fun playing stuff other than soccer with his friends after practices and games.

What's my point? People matter — more so than winning, more so than ball control skills, more so than anything else at all. (Unfortunately, I fail to remember this critical truth myself sometimes — both on and off the field of play — much to my own embarrassment and the detriment of valued relationships.)

"Fundamentals" begins with "fun"

The assistant coaches on my youngest boy's team were amazing. One of them was introduced to me as a guy with a ton of soccer-related creds. Quite honestly, I was a bit intimated by this fact. But if there's one thing that he and the other coach taught me this year, it was that if the kids aren't having fun, it doesn't matter how well they can kick and throw a ball. What good is teaching good dribbling if at season's end the kids say, "Soccer's a drag — count me out"? For kids at this age, fun is closely tied to many things:

  • avoiding repetition — no child can tolerate doing the same thing for long periods of time. Mix it up a bit, Coach.
  • avoiding down-time — It only takes a few moments of waiting in line before a young child times out. You can almost watch as their attention span threshold is reached, and then away their little minds go, off to La-la Land. If you can, avoid line waits and repetition by splitting the team into smaller groups at various stations of differing activities.
  • simple rewards, oft-given — I was introduced last season to these little 1" iron-on motivational patches with pictures of soccer balls in various colors, stars, etc. We gave each kid that showed up at practice and stayed for the duration one of these patches. Kids respond positively to the promise of even simple rewards like that, or the promise of playing a favorite game at the end of practice. As it turns out, they don't mind trying harder when trying harder is fun.
  • team spirit — This season the teams were allowed to choose their own team names. My oldest boy's team chose the "Soccer Monsters". I wasn't so thrilled by the name, but nonetheless spent a few evenings designing a team logo just for kicks. The other coaches and parents loved it, and by the end of the season that logo showed up on 3" iron-on embroidered patches, stickers, a vinyl signboard for the parental cheering section, and even a sheet cake! Everyone loved the "brand" we built around the Soccer Monster name. And repeatedly the coaches and parents reinforced not just the value of individual contributors, but also the value of the team as a whole. The stereotype of the coach's kid who gets all the attention was completely absent — every child took his or her turn on the bench in every game; every child got a chance to play every position on the field over the course of the season; and every child gracefully dealt (most of the time) with being asked to do something that wasn't their favorite thing because it would benefit the team.

I owe a deep debt of gratitude to the other coaches and parents who routinely helped to make soccer fun for my kids and their peers.

Never underestimate a child's potential

If you had told me what I would be seeing some of my 5- and 6-year-old players doing at game time at the beginning of the season, I would have laughed in disbelief. While many other teams were playing "bunch ball" (all the kids swarming around the ball like so many angry bees), ours entered even their first games with an understanding of the various positions, their roles in those positions, and the importance of performing in their roles instead of just roaming around the field without a purpose. By season's end, I was finding that the kids could handle some game play maneuvers that I thought were pretty complex, such as one defender falling back to help the goalie when the other needed to head off an approaching attacker. I found myself often saying in disbelief things like "But these kids are only six years old!" and "But this is his/her first season of soccer!"

One of the other teams had a kid who, despite being one of the smallest players in the division, had amazing ball control and the sweetest little slide tackle you ever saw. And you didn't see many, because I think he's the only kid who attempted them in this age group. Every time he did (our team played against his team twice) I smiled a huge smile and thought (or said aloud) "That's awesome!" His dad was his coach, too, but when asked him about his kid's skill, he indicated that it was self-developed. Call me naïve, but that's amazing to me.

Now maybe these are just exceptionally talented children. But I have to believe that the key to this phenomenon is to never stop asking more of the players. At any given moment, a particular player is going to have a great grasp of some concepts and skills, a pretty good approach to others, be relatively weak at still more, and have never been introduced to the rest. Keep a sliding window of instruction with those kids so that they are always trying stuff they are likely to fail at along with the stuff that they do with grace and ease. What other self-developed skills are hiding inside our children just waiting for us to affirm them into the mainstream? What other skills are they ready to learn but can't because we underestimate their chances of success? This leads me to my next point.

Failure can be the best instruction

Instruction is extremely important. There is always something else to learn, develop, or improve, so ideally instruction never stops. The Harrisburg Youth Soccer program is a decidedly instructional league, favoring instruction to competition in an attempt to develop well-rounded players who love the game enough to play competitively at older ages (when they can emotionally handle serious competition). But instruction without the freedom to try and fail is stifling.

If every time one of my sons reaches for a glass of water on the table I criticize how fast he's reaching, whether he's planning to use one or both hands, whether he looks to be picking up the glass or sliding it between all the other obstructions on the table surface, and so on — if I micromanage his every move, he learns exactly one thing: the way Dad wants stuff done. Not taught in those moments is the most valuable lesson of all: why Dad prefers that approach. My son doesn't understand that it's Dad's experience with the physics of our Universe that leads him to prefer a particular approach to drinking from a glass. And he never will until he experiences some of that physics himself.

Now, I'm not saying that there's no value in that type of instruction. Certainly the opposite extreme of never sharing your own experiences with kids and leaving them to learn solely from their own experiences is just an abdication of parental responsibility — inefficient, unloving, and sometimes downright dangerous. But an absolutely critical aspect to any learning situation is experience, and specifically experience failing. Kids don't need protection from everyday failures because everyday failures teach some of the strongest lessons more quickly and more thoroughly than constant hand-holding ever can. Kids need a safe place to experience those failures, reassurance that in failing at a task they haven't failed as people, and encouragement to get up and try again.

By the end of our soccer season, the majority of our kids knew how to perform nearly any action that would likely be asked of them during a game. Early in the season, we hand-held. We did our jobs as coaches and taught them the finely detailed mechanics of these actions. But as the season progressed, we gradually shifted to a model of letting the kids make their own decisions and deal with the consequences. And if one of them messed up and did something incorrectly, both the player and the attempt were affirmed as valuable.

In the free software world, this is similar to way that new project members are often brought on board. First, a would-be project member submit patches for the software — technical descriptions of how the software should be changed to add a feature or fix a bug. The patches are reviewed by existing project members for accuracy and efficient, for attention to the rules of the project, and so on. If the patch meets the standards, it is committed (by an existing member) as a change to the software itself. If it doesn't, the patch is sent back with recommendations on doing it better. Over time, a talented developer will submit better and better patches the first time around, earning the trust of his or her mentors. And at some magical point, the mentors realize that it's no longer worthwhile for them to pay both the cost of reviewing the work and of then actually committing it on behalf of the patch submitter when instead they could let the submitter commit his or her changes first and then receive review afterwards. As coaches, our goal should be to progressively transition each child from a model of pre-emptive review (at significant cost in valuable time) and into one of post-facto review (which is far more efficient and allows the kids to celebrate victories they've earned for themselves).

Friday, November 13, 2009

Name-dropping Jesus

Don't you just love it when you personally benefit just by knowing someone else? Maybe (just maybe) you're considering an order of some trophies for your eldest son's soccer team, and one of the other dads on your youngest son's soccer teams says, "Oh, you should check out Awards Express — I always get my stuff from them. They turn around high-quality orders quickly and professionally. Tell 'em Tray sent you!" And instantly, you feel like some kind of V.I.P., empowered to trade on someone else's good name and reap the benefits of their relationships with a mutual contact.

That's kinda the way prayer works for Christians. I was thinking tonight about how I was taught that prayers are supposed to end. You know, some variation of "In Jesus name, Amen." This isn't merely the result of some ancient meaningless ritual passed down through the generations. It's the way Jesus told us to pray. In John 14:12-14, He tells us that after He returns to His Father (which, if you haven't noticed, He already did), He will do whatever we ask in His name. We find similar statements in John 15:16 and later again in John 16:23-26. Basically, Jesus is hearing our complaints and concerns and needs and desires, and He tells us, "Hey, I know exactly who you should talk to about this stuff. My Father is the best in the business. He can hook you up. Tell him I sent you."

Now, if ever there was a name worth dropping, the Son of God's is the one. But sometimes I wonder if the following happens when I pray:

[Tinkling sounds of bells rapping against the closing door.]

God: Yes, can I help you?

Me: Uh, yeah. I'm looking for solutions to some of Life's problems.

God: Oh, well then you've come to exactly the right spot. I designed Life — nobody knows how it works better than I do. Now, I could take a small bit of offense that you would claim the product is flawed. I can assure you that it isn't. But as it turns out, I'm also really good at forgiving, so let's just move past that. What did you have in mind.

Me: Well, I was kinda thinking that maybe you could cause X to happen. That would really work out well for me.

God [clearly uncomfortable]: Hrm. Well, that's not really how I had things planned for you, but...

Me: Yeah, I know. See, something tells me that there's a purpose for my life that's bigger than just me, but I really, really want to just get X. I just think that makes the most sense for me.

God: You seem pretty confident about this request. Are you sure you've come to the right spot? I'm usually pretty picky about making sure that the work I do is for everyone's benefit.

Me: Oh, yeah, I'm sure. Your Son sent me; told me you were the best in the business.

God: Oh! You know my Son?! Well that changes everything. You two are close? Good friends? Maybe you guys work together?

Me: [clearly uncomfortable] Well ... I wouldn't exactly say we're close, really. I met Him some years ago, and we see each other from time to time. He's good friends with my wife's grandparents, so, you know, practically part of the family, sorta, I mean, not that we ask Him over for Thanksgiving or anything, but...

[Extended silence. Awkwaaaaard.]

Maybe I should strengthen my friendship with Christ before using His name for my gain, huh?

Go back and read John 15:16. Better yet, check out some more of the context by looking at John 15:14-17:

14 You are my friends if you do what I command. 15 I no longer call you servants, because a servant does not know his master's business. Instead, I have called you friends, for everything that I learned from my Father I have made known to you. 16 You did not choose me, but I chose you and appointed you to go and bear fruit — fruit that will last. Then the Father will give you whatever you ask in my name. 17 This is my command: Love each other. — John 15:14-17 NIV (emphasis added)

Think my fictitious scenario above exaggerates too much? I'm not so sure. See what Jesus says in Matthew about folks trading on his good name without the fruit to justify it:

18 A good tree cannot bear bad fruit, and a bad tree cannot bear good fruit. 19 Every tree that does not bear good fruit is cut down and thrown into the fire. 20 Thus, by their fruit you will recognize them. 21 "Not everyone who says to me, 'Lord, Lord,' will enter the kingdom of heaven, but only he who does the will of my Father who is in heaven. 22 Many will say to me on that day, 'Lord, Lord, did we not prophesy in your name, and in your name drive out demons and perform many miracles?' 23 Then I will tell them plainly, 'I never knew you. Away from me, you evildoers!' — Matthew 7:18-23 NIV

Are you just name-dropping Jesus? Man, sometimes I do. I've witnessed the power of prayers made in His name and in a spirit of obedience, but I confess that many times my name-dropping is just bogus. I need to work on that — need to work on my friendship with Christ, need to work on my obedience to His commands, need to work on bearing fruit, and need to work on loving my neighbor — because I definitely don't want to experience any awkward encounters with God. How about you?

Thursday, May 14, 2009

Green

Everywhere I look I see the green. It's Spring, so my green lawn needs a bi-weekly whacking with my John Deere green lawn tractor (which is complicated by the low-hanging green-leafed limbs of some of the trees on our property). But if that was the only green I was seeing, that'd be okay. Unfortunately, it isn't.

"Going green" or "being green" or "living green" almost wholly consumes the mass media and the consumer marketplace. Right now, over half of the top results from a simple Google search for a word as common as "green" are about environmentalism, eco-friendliness, and so on. Green is the new black, or something like that.

Climate change (née global warming), carbon offsets, renewable energy, reduce/reuse/recycle, are worthy topics all. And as a Christian who believes that mankind was entrusted with wise stewardship of God-created, God-provided resources, I don't think I or anybody else holds a get-out-of-responsibility-free card. But I detect two big, green problems with much of the hype:

Man sees green — in financial opportunity. I honestly do not know who to turn to for trustworthy information about the state of the world; its climate and related trends; which problems are real, predicted, or flatly imagined; which solutions are viable; and so on. Part of the problem is that there's too much money in the eco-this-that-or-the-other trend right now. Do I really believe that every producer of goods is concerned about the world when they release some fascinating new eco-conscious version of their product? Hardly. Seems sex is getting a run for its money in the "marketing tools" arena these days.

God sees green — with envy. We have a jealous God who demands that all things be done for His glory. Not mine, not yours, and not Earth's, but God's glory. I think far too many people have traded being caretakers of creation (as a form of worshiping the Creator) for worship of the creation (Earth, humanity, Self, money, ...). That's busted.

There must be a better, more divinely-inspired way of exploring this problem space and its solutions, because being green — that is, naïve — enough to worship this rock or anything or anyone on it is a horrific non-starter.

Thursday, March 26, 2009

I am a worship leader. (And so are you.)

While contemplating God's love letter to artists, and directly on the heels of a message at church last night about the ways in which Satan attacks Christians, I find myself staring directly into the eyes of some of the same old insecurities that have haunted me over the past few months. I'm ready to 'fess up about those now.

I have some musical talent. I think I can even offer a pretty objective evaluation of that talent:
  • I sing, but my voice is thin in higher registers and can suffer pitch control problems in lower ones. And, probably due to vocal abuse, the clean tone I could produce ten years ago is giving way to something more crackly.
  • I play guitar, but am self-taught, and have never invested enough into learning either the acoustic or electric guitars to move beyond competence and into proficiency.
  • I'm not such a fine songwriter. I'm lyrically uninspired, and melodically challenged. But I'm really good at taking another person's song foundation and enhancing it (with neat arrangements, harmonies, counter-melodies, motifs, and so on).
  • I can wield digital audio software skillfully, and have even developed some pretty neat sonic "tricks" that have served me well. But I can't seem to produce output that sounds quite like I envision. (A recent attempt at something Counting Crows-ish was referred to — behind my back, mind you — as "yacht rock", with an apparent Air Supply influence. Ouch.)
I think it's healthy for folks to be able to recognize what they truly can and can't do. Wouldn't you agree?

Then here come the demons. "Why, again, are you helping to lead worship at yet another church? You don't fit the mold. Real worship leaders have hip haircuts; wear trendy clothes; are 10 lbs. underweight (instead of 20 lbs. over); have at least eight stomp boxes and a sound engineer devoted solely to their rockstar groove; sing with perfect pitch, tone, and timbre; and can spew God-honoring utterances while ripping fingers-of-fury blazing guitar solos. With their eyes closed and both hands raised to the heavens. You are no worship leader. You are, at best, background noise."

Oh, man, that stuff stabs. Plunge. Twist. Gush. (It hurts even now, just thinking about it.) But that's okay — I figured out some time ago how to protect myself from those barbs. See, I've dealt with this in the past by simply denying that I was (or was attempting to be) a worship leader. I was "just trying to help with the music program", or something like that. After all, the Enemy can't beat me in a race I refuse to run, right?

Sadly, I was wrong: I am defeated because I refuse to run. My responsibility as a created being — the tax on my very existence — is to worship the Creator. But my responsibility as a human is to lead (by encouragement, example, or otherwise) my fellow humans to do the same. My roles as a husband and father, especially, demand this service to my wife and children. And how can I be seeking loopholes in the Covenant when I've failed to lead those who I would consider some of my closest friends to worship God with me? No, whether I accept the label of "worship leader" or not, the responsibility is mine. God's will begins with thanksgiving and worship.

I appreciate the perspective Geoff Janes provides on the search for God's will at http://geoffreyjanes.blogspot.com/2009/03/what-is-gods-will-for-my-life.html. I should consider myself fortunate to have discovered — through the talents God has given me and the discernment of trustworthy others — a piece of God's extended will for me at this time: demonstrating that thanksgiving and worship with a guitar in hand at Providence Baptist Church. It may only be for a season — that is not mine to know. But at any cost, I must therefore seek only to do that will, and waste neither energy nor emotion chasing the unattainable stereotype constructed by the Enemy. My skills are not worthy of renown. Fortunately, they weren't fashioned for that purpose.

So today, I reject as invalid the notion that leading worship isn't my job. I accept as valid criticism that I've not been particularly good at this in the past. I apologize to my family and friends for not living a life that consistently and convincingly compels you to worship, too — love demands better than that. And as for that background noise I'm ever-so-capable of? I'm cool with that. But may it be a joyful noise from this day forward.

Monday, March 16, 2009

Heaven and hell

I came across the following joke today in the comments section of a particularly good post on Jon Acuff's Stuff Christians Like blog. (Thanks Helen, whoever you are.) It's … er … something to chew on.

A man spoke with the Lord about heaven and hell. The Lord said to the man, "Come, I will show you hell." They entered a room where a group of people sat around a huge pot of stew. Everyone was famished, desperate and starving. Each held a spoon that reached the pot, but each spoon had a handle so much longer than their arms that it could not be used to get the stew into their own mouths. The suffering was terrible.

"Come, now I will show you heaven," the Lord said after a while. They entered another room, identical to the first - the pot of stew, the group of people, the same long-handled spoons. But there everyone was happy and well-nourished.

"I don't understand," said the man. "Why are they happy here when they were miserable in the other room and everything was the same?"

The Lord smiled, "Ah, it is simple," he said. "Here they have learned to feed each other."

Thursday, March 5, 2009

Today, I feel like a successful husband

Determining if you are succeeding as a husband probably involves some pretty unruly psychological calculus, but today I feel like a successful husband. Why? Did my wife express her love and devotion in some particularly convincing way? Was I presented a trophy etched with "Best Hubby 2009"? Is the Internet community hanging on my every tweet to find some sage advice on being an ideal mate? Not hardly. It's for much less obvious reasons that I feel this way.

Last night, as Amy and I left church, she had a huge smile on her face and she said, "I think I've found my place".

This was the first Wednesday evening service we've attended at our new church. After the service last night, Amy and I participated in practice sessions with the church's music team for the first time. The music director and pastor have graciously agreed to let us try to work to bring a slightly more contemporary flavor to the worship music of the church. So I added my guitar to the piano and keyboard sound already present, and Amy is donating her voice to the praise music and to the choir. It was the participation with the choir that had Amy so thrilled last night.

What has Amy's happiness as a musician to do with my success as a husband? Everything. I can rest well at night knowing that I have encouraged her to serve the church in any capacity she desires and feels gifted to serve. I have worked to arrange meetings with the pastor and music director so we can research this area of service. And I have consistently recognized, praised — and even constructively criticized, when necessary — Amy's wielding of her God-given musical talents. And someday, when God blesses her obedience and service to Him in this matter, I will be able to both share in her joy (three-point shot, nothing but net) and claim some of it for myself (the assist).

Could success as a husband really just boil down to using unconditional love to guide my wife toward the likeness and service of Christ?

Sunday, February 15, 2009

The year change came to America

[If you think this post is about Barack Obama, you'll be sadly mistaken. This is my blog, by golly; Barack has his own.]

For Christmas, I got Amy something I'd wanted to get her for years: a couples devotional guide. We've each had our private times of Biblical study and prayer, but had never really formally had a dedicated daily time of joint reflection and discussion. So she was as thrilled as I expected when she unwrapped Moments Together for Couples (by Dennis and Barbara Rainey). This is a 365-day devotional. The entries are short — one page per day — with suggested discussion topics and a prayer guide. That seemed to me to be just about the right amount of effort to keep us interested without exhaustion, especially knowing that it would be at day's end when we'd likely be reading this thing.

On January 1, 2009, we read the first entry together. When we got to the suggested discussion topic, we got a lot more than we bargained for. What resulted was a two-hour long conversation that was really hard to have, but ultimately uncovered hidden expectations, disappointments, and wounds that we had no idea were present in our marriage.

Amy and I have always had a great marriage, but somewhere over the course of the past eleven years, small fissures had begun to form in the foundation of our relationship. The added weight of parenting and relocating from Chicagoland and stress caused by our church situation had exacerbated the problem. Fissures were becoming cracks of the worst kind — the kind that can't be immediately recognized on the surface. I don't believe we were at that moment at risk of catastrophe, relationship-wise. Our commitment to one another is non-negotiable and permanent. But it's a terrible thing to settle for "I do" or "I will" when "I will, and I really really want to" is within reach.

And so on January 1, 2009, the healing that comes from honesty, from openness, and from renewed devotion to one another and to God came to my marriage and, by extension, to America. I am having the very best year of my entire life. I feel like an entirely new man. I have immeasurably lower levels of stress, higher allotments of patience, and am finally learning to love as God wants me to love. I'm learning to trust God in ways I've never been able to before. And all those in my sphere of influence reap the benefits, too! How awesome is that?

Amy and I have faithfully attended to our devotional book every day of this year. We learned quickly that if we read and discussed immediately after putting the boys to bed (instead of just before we planned to go to sleep), we were much more likely to have enough energy to engage the discussion topics. We actually look forward to this time of our evening — it's one of the highlights of our daily routine.

Are there fissures, cracks, or full-fledged crumbling in the foundation of your marriage? I urge you — no, I beg you as a firm believer that a strong family is a strict prerequisite of a strong world — to invest dedicated attention to that problem. Talk to your spouse. Don't be afraid to lay everything on the line; to be completely vulnerable. Read books. Watch movies (such as the surprisingly fantastic Fireproof). And if your spouse won't talk to you, then talk to someone who truly understands the seriousness of the marriage commitment and can help you repair yours.

Sunday, January 18, 2009

Experiencing God at Southbrook:Monroe

Today my family visited Southbrook Church's Monroe campus (where our friend Geoffrey Janes is campus pastor). They've got a great thing going on down there, and I'd urge you to check out that church if you're in the area. It's a video campus, which I thought would be kinda weird, but honestly it really works well there. The live house band is an incredibly talented group of guys and gals — wow! We truly had a neat visit there.

The visit ended in a very strange way, however. As we were leaving the service, I felt for my wallet and found it missing. Now, on the way to the church, we'd stopped by the Dunkin' Donuts drive-thru for breakfast, and I remembered that I'd put my wallet into the console between the front seats of our car. I was a little nervous about having left my wallet in the car unattended, but, trusting that all would be well, we didn't bother to rush out of the church. We took our time, picking up the kids from the child care area, chatting with Geoff and his wife, Nancy, and so on. In fact, we were one of the last folks to leave the building that day.

On our way out to the car, I used the remote entry fob to unlock the doors from a distance. When I got to the car, my wallet was not in the console. Now, because I'd used the remote entry device, I couldn't tell if the car doors had been locked or unlocked throughout the church service. Had I left the doors unlocked, and my wallet in plain sight? We looked around the car for signs of anyone having rummaged through it — nothing. We looked around the car for my wallet — nothing.

I went back into church to see if maybe the wallet had dropped out of my pocket inside somewhere. Again, no luck. I spoke with Nancy and Geoff to see if anyone had reported a found wallet — no dice. After giving up on the search inside, I returned to the car. Amy and the boys had been continuing to search for and pray about the wallet. They looked under and around seats, in the glove compartment and console, under the console, around the car, and so on. Everywhere that could be searched, they searched.

I want to pause here to mention something that merits mention. Throughout this entire ordeal, I was perfectly calm. Anyone who knows me well will assume that either I am lying about that, or that I simply don't know what "perfectly calm" even looks like. I can't explain why (in psychological terms, anyway), but I was just confident that God would see us through this mini-crisis.

Anyway, as I got back to the car and heard from Amy that nothing had been found, I grabbed my cellphone to contact banks and credit card companies and start blocking card numbers. While thumbing though the address book, I asked (somewhat naively) if Amy had looked under the car seats. She said she had, showing me that — multiple times, even — she had looked right … what?! There it is! My wallet was sitting, pretty as you please, almost in plain view to the right of the console!

Clearly, some rejoicing and prayers of thanksgiving were in order. Once we finally calmed down, I drove the car over to the entrance of the church (which, by the way, we — and only we — had passed through three times in the past five minutes or so). I asked Amy to hop out and run inside to tell Nancy the good news about my wallet. As she stepped onto the sidewalk, I saw Amy bend down and pick something up. Can you believe it? There was a dollar bill lying in the middle of that white sidewalk! So not only did she get to tell Nancy the good news, but she was able to donate an extra dollar towards to the ministry of that facility! What an incredible, incredible experience it all was.

Monday, January 12, 2009

From the "duh" department...

My wife asked me this morning if I'd ever read — really read — her Suave shampoo bottle. Turns out I hadn't. I mean, not really, anyway. And in that act of utter negligence, I had overlooked an amazing claim that Suave makes about their product:

Cleans and conditions hair in one simple step — for less than more expensive brands.

That's funny stuff, or at least funnier than less funny stuff.

(Thanks, Amy, for keeping our marriage light-hearted. And full of extra body and shine.)

Thursday, December 18, 2008

Dear Wal-mart, Welcome to the Digital Age

A week or so ago, I finally got my family to sit still in our living room long enough to snap a quick family photo for use on Christmas photo cards we planned to send out this year. After editing the image just a bit to fix some weird shadows, adjust the colors, and try to fake some depth, I called Amy up to inspect the results. She was pleased: "It looks good. It almost looks like a professional photograph." So, I uploaded the image to walmart.com, selected the photo card layout I wanted, and ordered a bunch of them. Here's the photo:

I got a call a couple of hours later from the local Wal-mart Photo Lab:

"Hello, Mr. Pilato?"

"Yes I am."

"We're sorry, but we can't print your photo cards unless you bring us a release form."

"But ... but ... I took the picture myself with my little Canon S410!"

"We've been looking at the picture for a while, and it really looks professionally done."

There ensued another few minutes of hassling here, some of which revealed that if our fireplace had been black instead of gold, it wouldn't have looked so much like a faux matte background. Finally, the Wal-mart employee gave up some critical ground:

"Mr. Pilato, if you could just make a release form giving yourself permission to print the image, we'll do it. We just have to cover ourselves. I'm sure you understand."

"Wait. You want me to what? You know what — nevermind. I'll do it. Thanks."

I hung up the phone, paused for a moment to verify that I wasn't dreaming all of this, and fired up OpenOffice Writer. The following is the release letter I took with me when I picked up the photo cards the next day:

Even though I find it completely ridiculous that I have to do such…

I, C. MICHAEL PILATO, do hereby grant unlimited printing release to MYSELF for the following:

One (1) photo of my own family (Mike, Amy, Gavin & Amy), taken by myself with my own Canon Powershot S410 Digital ELPH camera (serial number **********) in my own living room, with the camera set to use the 10-second shot timer while sitting on a 6-inch mini-tripod atop one of my TV stands, in front of my fireplace – which is gold even though my wife wants it to be black (because that's what the previous homeowners liked, we suppose) – and Photoshopped on my wife's computer to crop the original image, brighten the photo, adjust the colors a little bit, and fake some depth by slightly blurring everything in the image except the human subjects in the foreground.

This release is fully transferable by the above named FOR ANY REASON WHATSOEVER, and a copy of this document should be considered adequate proof of release.

Note for printer: While I am not a professional photographer, I am a pretty darned good image editor, and pride myself on making photos taken with a sub-professional, non-SLR camera look as if they were taken by more advanced equipment. However, if further information or verbal confirmation is needed per your company policy, please do not hesitate to call me at ***-***-****.

I guess this bit of sarcasm is on file somewhere at Wal-mart now, protecting them from the threat of a copyright-related lawsuit.

Tuesday, October 21, 2008

"...there's just something about that name."

A most peculiar thing happened in and around me on the flight back from Germany last Friday. I was pretty tired when I settled into seat 35C of Lufthansa flight LH428 from Munich to Charlotte. In fact, I fell asleep before the plane was pushed back away from the gate, and woke nearly an hour into the flight. As I was waking, a young child was just settling into her Daddy's lap for a nap in the seats to my right (and back a little ... a half-row offset). The family in seats 35D-35G was comprised of a man, woman, and two beautiful little girls of maybe 3 and 6 years of age. The youngest girl was the one nodding off as I woke. After taking in my surroundings (since my sleepy head clearly missed the chance to do so when I boarded the plane), I turned my attention elsewhere.

A couple of hours later, the little girl woke, whining. The whining turned to crying tinged with the occasional "Owie", and then the whole bit transformed into outright screaming. She was obviously in pain, not merely unhappy. My guess was that her ears were bothering her. She continued quite loudly expressing her pain for at least five minutes, during which she was passed from her father to her mother. Many in the cabin were rubbernecking to see what was going on, and when the mother was asked directly about the child's problem, I overheard the response: "She has an ear infection."

If there's one thing I knew at that moment, it was how painful flying with ear issues can be. On a recent return flight from California, both of my ears refused to "pop", and I was tormented for a half-hour by the nearly unbearable pain that results. It can be a bit like having nails driven into your ears, if you haven't experienced it. I tried everything at the time—drinking water, yawning, chewing gum, forcing high pressure into my ears. Nothing worked.

As I recalled that pain from just a few months ago and imagined what that precious little girl was going through, I realized something: my cheeks were cold, with trails of tears coming down them. Some may say it isn't "manly" to cry. I say it isn't manly to be so self-consumed that you risk not caring for the suffering innocent. And so I did the only thing I could do at the time: I prayed.

Now, I don't consider myself a prayer warrior by any stretch. I don't lay claim to any of supernatural spiritual gifts so celebrated in charismatic congregations today. I'm guilty of slapping the old "inJesusnameAmen" at the end of my utterances, and usually with nary a thought as to who Jesus is and why in the world we pray in his name, anyway. But the seeming injustice of a little girl in pain on this airplane was overwhelming to me at that moment, and so I prayed for her relief. And because I've been taught that there is power in the name of Jesus, and because at that rare moment I was able to believe wholesale that God could and would spare this child, I prayed specifically in the name of Jesus Christ for this relief to occur.

Now, if there another thing I knew at that moment, it was about waves of warmth. I take a medicine that can cause flushing incidents—basically, your body feels like it's on fire on the inside, your skin turns splotchy red, and for a couple of hours everything that touches you feels like it's made of straight pins. I also know that when I get emotional—especially when I'm angry—a wave of heat passes over my body and I'm a sweaty mess in three seconds flat. But at the very moment that I invoked the name of Jesus in my prayer, I felt something like that wave of heat pass over me, but without the typical tell-tale sweaty results. Almost immediately, the screaming girl in row 35 began to calm down, and soon was asleep in her father's lap again.

In the name of full disclosure, I noticed that at about the time I was praying, the parents were administering an oral medication. Maybe that stuff is powerful enough to dissolve that kind of pain in thirty seconds flat. I can only speak to the situation as I perceived it, and to the extent that I was involved.

To the family in row 35 of flight LH428 on Friday, October 17, I hope your little girl heals quickly. You as parents showed an incredible amount of patience in what could have been a stressful and embarrassing situation, and are to be commended for it. And while I'll never be able to say for sure whether God intervened in this situation, I am confident of two things: He is a just God who cares for people, and for once I did in faith exactly what I was supposed to do.

Wednesday, October 1, 2008

Mistrials in the Court of Public Opinion

Last night, Amy and I watched an hour-long preview of the DVD release Obsession: Radical Islam's War Against the West. (I'm not sure how you can call an hour-long movie a "preview" when the full version is only 17 minutes longer, but I digress.) We got the DVD from a friend who lives in Charlotte, who had gotten it via its inclusion in a recent edition of The Charlotte Observer. We were in the mood for a movie, but it was getting late and we didn't want to invest in a two-hour romantic comedy, so we popped this disk in instead.

As a piece of documentary, it was interesting. Not the most exciting thing in the world, but definitely interesting. The film begins with a pretty clear explanation that it is talking exclusively about a particular minority subgroup of the Muslim population that promotes and engages in acts of violence, not about the majority of Muslims who are peaceful, law-abiding citizens. Most of the film consists of footage from Iranian and Arabian television broadcasts, with bits of commentary from a handful of folks (a former PLO terrorist, the daughter of a suicide bomber, an anti-Semitism expert, an ex-Hitler Youth officer, etc.) between clips. The television footage — especially the stuff showing children passionately reciting jihadist poetry and huge assemblies of people chanting "Death to America" — are intriguing enough. But the commentators serve to add the "personal touch" plea for awareness and action by all people (Muslim or otherwise).

After the film was over, Amy and I were both of the same frame of mind. You might assume we were angry at Islam or something. You'd be wrong. Our mindset was one of sadness on behalf of the children taught to hate and kill in the name of Allah. We had brief discussion about the movie, then turned off the lights to go to sleep. But just as we were doing so, Amy wanted to know more about the folks who produced the film. I had noticed that the copyright on the disc was for 2006, which seemed odd as I was seeing it for the first time in 2008. I had even rhetorically asked Amy earlier, "Why is this just now coming out, seven years after 9/11?" And we both wondered if the Observer was the only newspaper that participated in this distribution. So we got back out of bed to hover around the computer.

The movie's website wasn't able to quickly answer the question about which newspapers participated in the distribution of the DVD, so we started Googling around. (We later found some of that information on the movie's Wikipedia page.) We visited a handful of top results in our Google searches, and every site we found was criticizing the film, its producers, or the recent distribution. But what turned our mood from sadness into frustration was that none of the criticism was about factual inaccuracies in the film, but about tangential issues. Most of what we saw was one of the following:

  • Complaints from Muslim groups saying that the film enforces a negative stereotype of all Muslims and would encourage hate crimes against Muslims. I dunno. The movie does carry the disclaimer I mentioned at the beginning of the film, carries video footage of Tony Blair echoing the same sentiments in person at the end of the film, and everywhere in-between the commentators are careful to speak about "radical Islamists" or "jihadists" and appealing to the peaceful majority of Islam-dom to decry the violence of the radical wing thereof. I guess I don't see how this piece of film could possibly affect the Muslim stereotype more than is already done every time one of the Islamic terror groups gets mentioned on the evening news for perpetrating their violence d'jour.
  • Complaints that the film is clearly a political piece promoting a particular candidate for the U.S. Presidency. But I don't recall the movie or its packaging ever mentioning any such candidates or political parties. Unless I'm mistaken, the only times you see American political figures in the film is in radical Muslim propaganda footage portraying George W. Bush as evil (which is pretty common in American media, too). The claim is apparently that the film's backers are decidedly pro-McCain, anti-Obama. But that sentiment is simply not present in the film itself. You'd need out-of-band information to draw that conclusion, the most influential of which is the viewer's already-formed opinions about a particular candidate's ability and willingness to respond to the described threat.

In other words, what we quickly found by Googling around was the online equivalent of a mistrial.

To the Muslims concerned that documentaries on radical Islamic jihadists will enhance negative stereotypes of all Muslims: It is certainly disappointing that that's probably true for some viewers. Every documentary about Death Row enforces negative stereotypes of black males in some folks' minds. Every documentary about gang violence enforces negative stereotypes of the ethnic groups represented in those gangs. Every documentary about The Crusades or Christian abortion clinic bombers enforces negative stereotypes of Christians like myself, too. (Sheesh, the media tends to negatively portray even peaceful, law-abiding Christians, for that matter.) I think people cling to stereotypes because we all inherently like to categorize stuff, and stereotypes are the intellectually easy way to do that categorization. The questions that all folks who are victims of unfair stereotypes must ask of themselves is, "What am I doing to correct or refine that inaccurate stereotype?" Are you and I and the Jew and the black man and the Latino and the [insert stereotyped person here] supporting our respective stereotypes with our lives, or do we daily disprove that we are what the weak-minded claim we are? Do we speak out against the crimes committed by people "like us", or does our silence allow folks to assume we support those crimes?

I don't know if there's some political agenda behind the recent distribution of this film. My heart tells me there probably is. But if that's the point that everyone is dwelling on, am I alone in thinking that's sorta bad? Is the documentary a giant lie? If so, discredit it with the truth. But if it isn't — if, in fact, radical Islam is as the DVD suggests a historical recurrence of the pattern last seen in the ethnic cleansing perpetrated by Nazi Germany — does it ultimately matter why the documentary was distributed? Would not the terrorism itself be considered a somewhat more high-priority issue than who paid what to inform us about it and why they did so? One would think so.

Thursday, September 25, 2008

Righteous war: snapshot of a five-year-old's mind

My five-year-old son, Gavin, just came upstairs to my office — a pint-sized bundle of tornadoesque energy and noise. Today "the good guys" and "the bad guys" are flying fighter jets (which look, ironically, exactly like the ASL handshape for "I love you"). Now, I'm still not terribly comfortable with my kids embracing imaginative play involving weapons. On the one hand, I know that boys — especially at my boys' ages, and unlike their female counterparts — need rough and tumble play with strong male role models as part of proper gender identification. On the other hand, I don't want my little guys desensitized to unnecessary or unlawful violence (though I'm fighting an uphill battle against the entirety of mainstream media in this, it seems). So I decided to interrogate Gavin about his play today.

"What makes the Bad Guys bad?" I asked.

"The Bad Guys are the ones doing bad things, Daddy."

"Okay, but sometimes you do bad things, too. So do I. So does Mommy. So do your Good Guys, I'm sure."

"But my Bad Guys are the ones with the guns."

"Your Good Guys have guns, too, though. I dunno, Buddy — I can't see any difference between your Good Guys and your Bad Guys."

At this, Gavin paused. You could almost smell the grease in his mental gears as they warmed into steady rotation. Finally, he asserted, "But the Bad Guys are using their guns to hurt other people, and the Good Guys are trying to help those people."

"Well done, son. Have fun playing."

Saturday, September 13, 2008

Mission accomplished. Well, mostly.

My wife's computer is now running Ubuntu Linux 8.04 (hardy heron). She no longer has any dependency on Microsoft software. I didn't think it was possible, but I might have fallen just a little bit more in love with her.

Actually, the sad truth is that for now I'm the one that still has a couple of Windows dependencies. (Those would be easily remedied by a conversion to Apple products, but that's never struck me as worthwhile maneuver.) I maintain a personal wiki page that tracks the pieces of software I need to be available (and not awful) on Linux before my dependency is broken, and over the years progress has been steadily made in that space. So, if you're a FOSS junky and you work on multi-track audio software, multi-track video editing software, DVD authoring software, or a good Microsoft Money/Quicken clone, you have my undivided attention!

Wednesday, August 27, 2008

Flooding in Harrisburg

My town of Harrisburg, NC — and indeed the entire region — has been in a state of moderate drought for the past, I dunno, fourteen months or so. So when we got a solid day of rain yesterday, Amy and I were thankful for it. Who wouldn't be? As helicopters hover over my head right now, I'll tell you who wouldn't be: our neighbors down the street.

Our house is on one of the higher pieces of ground in a neighborhood that is bordered on one side by a creek prone to occasional flooding. So we were blissfully unaware until a few hours ago, as we went about our morning, that just 200 yards away were several homes whose first floors were under water! Amy had left the house to take the boys to Romp n' Roll for some activities, but called my cellphone shortly thereafter saying she was coming back home — she couldn't go anywhere without hitting flood waters.

From our neighborhood, the rest of the world is accessible (by road anyway) only via Stallings Road. To the west, Stallings Road was flooded across some low-lying cow pastures; to the east, it was flooded at the bridge over that creek that borders the neighborhood. Our neighborhood and the one just west of it are now effectively on an island! It's an island full of people who couldn't get to work today. And, sadly, it's an island not quite big enough (or high enough) to hold all the houses in the neighborhood.

We took a walk down the street to see the damage and find out if there was anything we could do to help. Here are some photos I snapped while there. You can see in some of the photos how high the water line was before we even got down there to take the pictures.

I was told that one of the houses now under water was for sale, set to close today. And while the potential buyers are probably glad they didn't sign yesterday on the place, the sellers have certainly had their world turned upside down. My mother called to tell me that in her neighborhood across town (which is bordered by another creek), the water level rose by over ten feet. Apparently, there are crews acting there in boats to get people out of their homes. And another section of the same creek that runs by my mom's neighborhood flooded over yet another key road, according to the Lathams.

My neighbors appear to be in good spirits, and helping each other. I imagine that elsewhere in Harrisburg, NC, folks are doing the same for their neighbors. And that's just … Right.

Monday, August 4, 2008

Q4H: Why does God allow suffering?

I was reminded this morning of a question I think most theists — and many atheists, when in let's-just-suppose mode — ask at least once in life: Why does God allow suffering? What's the deal with all the floods, earthquakes, volcanoes, tsunamis, tornadoes, and so on? I certainly have asked this question of Heaven myself.

Some time ago I was pointed to an online audio clip of an NPR interview with John Piper, a pastor at Bethlehem Baptist Church in Minneapolis, Minnesota. You can listen to the interview yourself at http://www.desiringgod.org/ResourceLibrary/Interviews/1678_The_NPR_Tsunami_Interview/. I think Piper's responses throughout the entire interview are amazing — his mastery of Scripture and natural ability to deploy it as needed are incredible. But two threads in this interview really stuck with me:

  1. God is sovereign. Not only can He do anything, He rightly and justly may.
  2. God is always mingling judgment and mercy, both of which are useful for bringing people back to Himself.

Judgment and mercy. The Flood and the Ark. The sweeping through Egypt of the Death Angel and the passover sacrifice. The wages of sin (death) and the gift of God (eternal life through Jesus Christ).

What brought this interview to mind today was a bit from this morning's Bible reading. I'm in the book of Job, now. If you don't know Job's story, it runs something like this:

Once upon a time, there was an extremely wealthy and extremely righteous man named Job. Job had a wife, kids, and crazy amounts of livestock and servants. Job pleased God.

One day, Satan and God were chatting, and God asked Satan if he'd noticed what a good, righteous guy Job was. Satan replied, "Well, of course he's righteous. You've given him everything he could possibly want and more. He only loves you because you're good to him." So God granted Satan permission to do whatever he wanted in Job's life, so long as Job himself was granted immunity. Satan used his temporarily extended leash to kill all of Job's children and most of his servants, and to have his livestock stolen by raiders.

Job was shellshocked, but remained faithful to God (a fact that God bragged about to Satan). Satan said to God, "Yeah, yeah, okay, so he passed the test. But that's only because you didn't let me touch his body." So God fed Satan a few more feet of tether, and Satan struck Job with terrible sores over his entire body.

Thirty-five chapters' worth of (really poetic) dialogue fly by. Job's bummed but still faithful, his wife isn't offering much by way of help ("Just curse God, die, and get it over with already!"), and he has three friends who've come by to cheer him up but seem to offer more mouth than mind. Finally, God Himself comes[1] to speak to Job and his buddies, to set the record straight, and ultimately to restore Job's wealth and rebuild his family. And they all live happily ever after.

Anyway, while reading about Job this morning, I noticed this bit from Job 12:13-15:

To God belong wisdom and power; counsel and understanding are his. What he tears down cannot be rebuilt; the man he imprisons cannot be released. If he holds back the waters, there is drought; if he lets them loose, they devastate the land. [emphasis added]

Why do we — why do I — find it so easy to assign credit (blame) to God for the holding back of good things, yet routinely fail to assign credit (praise) to Him for holding back the bad stuff, too? God may let many problems come our way, but just think about the ones He didn't let come. Two things routinely taught in Christianity are that mankind has a supernatural adversary (Satan) who seeks our ultimate destruction, and that Satan has been given dominion over the earth. How long do you suppose we'd survive if those were the only two factors at work here? So why do we remain? Mercy.

Job had it right. After Round One...

At this, Job got up and tore his robe and shaved his head. Then he fell to the ground in worship and said: "Naked I came from my mother's womb, and naked I will depart. The Lord gave and the Lord has taken away; may the name of the Lord be praised." In all this, Job did not sin by charging God with wrongdoing. [Job 1:20-22]

...and then after he was bodily afflicted:

[Job] replied [to his wife], "You are talking like a foolish woman. Shall we accept good from God, and not trouble?" In all this, Job did not sin in what he said. [Job 2:1-3]

[1] By the way, I love how God enters the scene here in Job 38:1-3: "Then the Lord answered Job out of the storm. He said: 'Who is this that darkens my counsel with words without knowledge? Brace yourself like a man; I will question you, and you shall answer me.'"