Good Dog

A plate of food will reveal everything about the character of a dog that you need to know.

A man has a dog in a leash at his side. The dog is hungry – it’s supper time. The man brings out a bowl of food, filled with the dog’s favorite meal, and he sets it on the ground in front of the dog. How does the dog respond?

Some dogs will immediately strain at the collar – lurching forward, maybe barking or whining. They can think about nothing other than their fierce hunger and that enticing dish. That’s a normal dog. That’s his nature – his character.

But there are other dogs who are better trained. They will sit, quietly, obediently, faithfully. They won’t fight or strain. They will wait. But notice the eyes. Where are the dog’s eyes? Their eyes will be fixed on the food.

And then there is the most noble dog of all. The dog who has been well-trained by a loving master. A dog whose character exceeds all the others. A rare dog, indeed. This dog will notice the food immediately (he is hungry after all). He’ll look at the food, he’ll see it, and he’ll wag his tail. But then .. and this is the key to everything… his eyes will return to the face of his master, and there his focus will remain until the master releases him.

~~~~

Lord, there are many blessings in my life, and many more that you have whispered to me about – blessings that are to come, but have not yet arrived. For all of these I am deeply grateful. But train my eyes, dear Lord. Teach me to fix my eyes on you, the Author and Perfector of my faith. Let me set my mind on things above, not on things of this earth. Let me see you, loving master. Let me see only You.

Theolagile Programming

[This post might be better suited for my programming blog: MoterDev, but it is more akin to the thoughts on this blog. I suppose in the future, it will be harder and harder to distinguish between the two.]

Software developers over recent years have been increasingly gravitating toward a development methodology known as “Agile Programming.” This highly collaborative approach to software engineering emphasizes non-traditional strategies such as rapid development cycles (“sprints”), test-driven development, “pair” programming, and cross-functional teams, among  others. The growing popularity of this new trend is testimony to its success in environments where flexibility and robust engineering are valued. I can personally testify to the effectiveness of many of the Agile tenets in my own programming endeavors.

But, while the Agile methods are useful, in my experience I have found that they do not go far enough. I learned years ago that I am a much more effective and productive contributor when I base my efforts on the principles of Scripture. The “life-verse” for my career as a programmer has been 1 Cor 10:31: “So whether you eat or drink or program, or whatever you do, do it all for the glory of God.” (slightly paraphrased). This is echoed in Eph 6:7: “Work with enthusiasm, as though you were working for the Lord rather than for people.” And so, in the spirit of true theologically-grounded productivity, I’d now like to share with you some of strategies that I have embraced in my own career. I like to call this “Theol-agile Programming”.

1. Trust-Driven Development

In a “test-driven” approach, the programmer starts every project by building a suite of (failing) automated tests, then writes code until the tests no longer fail. I prefer to start with a different mindset. I believe that I personally am guaranteed to fail unless and until I seek the power and blessing of God on my work. “Unless the Lord builds the code, those who build it labor in vain” (Ps 127:1a; my paraphrase). Whenever I forget this principle, I invariably wind up stuck and stressed. The magnitude of my own inadequacies quickly overshadows my efforts and leaves me wringing my knuckles in anxiety.

Thankfully I have discovered that there is a much more enjoyable way to code. Trust-driven development asserts that there is One Expert who already knows all about my program. He understands the intricacies of every programming language and every operating system library. He has descended into dll-hell and proclaimed release to the captives. He knows all my bugs and how to fix them, and He simply asks me to trust Him. Trust Him because He is utterly faithful. That doesn’t mean He’ll whisper debugging suggestions from a burning desk shrub, or that He’ll miraculously write my code for me. It simply means that I no longer have to worry about those incessant challenges. I can rest peacefully in any storm with the confidence that He will be faithful to lead me and guide me like a good shepherd to a verdant resting-place. To God, it’s never about the product; it’s always about the process. His goal is to make me a man of faith, no matter how many scrum-iterations it takes. A man who doesn’t cry out to Him, “Lord! Don’t you care if we drown?” but who has learned to enjoy the ride, even when the waves loom large.

2. Prayer-Programming

Now, I must admit, I have never been a strong adherent to the XP “Pair Programming” strategy where coders are encouraged to work side-by-side at the same computer, taking turns with the keyboard. I have participated a few times and I have found that, while it can be fun and effective in certain circumstances, it really requires a well-matched set of partners.

A far more effective tool in my utility-bag is prayer programming. This principal follows directly from the previous one. If I knew that my scrum-master knew exactly how to fix my broken code, and had an open-door policy with all the time in the world, how foolish would I be to stay locked up in my office desperately trying to hammer it out all on my own? But that is exactly what I do all too often. I drift from the TDD described above, and I end up stuck and stressed.

I recently stumbled across Andrew Hare’s blog. He skillfully addresses many of these ideas and more – check it out!

[More to come…]

This I Believe (Essay contribution)

Contributed to NPR's "This I Believe" Essay compilation:

I believe…
that technology can never save us. And I’m sure that most people would nod assent, in tacit agreement. “Of course! Who ever said it could? How silly!” And then they will continue on down the road in their computer equipped cars, with a computer in their pocket and another attached to their hip, speeding to work where, more likely than not, they will stare at some kind of computer or another, for most of the day, only to slip home at the end of the day to watch digital tv served up from a computer storage device, sipping microwave-heated tea.

If you haven’t noticed: the computers have arrived.

I’m sure that everyone would agree that the computer is a pretty clever piece of machinery. A fascinating toy, an indispensable tool – it is indisputably the work of genius. But in all my years of undergrad and graduate studies in computer science, what impressed me the most was all the countless layers of genius that lie below the surface.

We usually see only the top level – the user interface. Those who delve a little into programming begin to see some of the inner workings of the programs, or perhaps get a glimpse of the underlying libraries and drivers. They may even peer into some of the layers of the registry or the operating system. Perhaps they open the black box itself and ponder the mother board or gaze with not a little bit of awe at that metropolitan map carved inexplicably into a fingernail-sized piece of silicon. And deeper it goes, and deeper. Every layer deftly and intricately crafted and intertwined with all that lay beneath it, and each one boasting the extraordinary brilliance and genius of its creators and designers.

For me, uncovering and admiring all of those layers was like looking down through the center of a giant spiral staircase, gazing through floor after floor of a might tower (a library perhaps), and then, beyond ground level, deep into the chasms of a multi-floor basement, and on into the darkened depths into which not even grad students descend. It was an amazing realization for me, to behold the phenomenal depth of the genius of the computer.

So why do I believe that the computer can’t save us? Is it because of some fatal flaw? Some Turing-Church thesis that categorically proves the inherent limits of the machine?

No. What convinced me that the computer can never be our savior, was the realization that all of the mind-boggling brilliance of the computer -- every bit of the genius in its chips – was placed there, just so, by its creators. It was the vast intellect of the designers that bestowed such awe-inspiring complexity to the computer. Giants, on the shoulders of giants, on the shoulders of still more shoulder-riding giants, whose collective intelligence has dared to erect the most daunting structure in history. Energized by dreams more lofty than anything since the architects began drawing up plans for the Tower of Babel, these geniuses are the true masterminds. Even if someday the computers themselves begin to create even more computers, it will always be the brilliance of the original designers that will be on display. Only genius could unleash such genius.

And so, perhaps, at the end of the day, we must ask: is it the giants themselves that will be our saviors? Is it our own genius that will save us?

And as I ponder that question, I am forced to admit that it can not be so. Despite all the weight of the arguments to the contrary, I simply cannot escape the logic that all the genius in our chips – the brilliance in our collective brains – did not spawn itself (the result of some infinite chain of accidents) but was placed there, just so, by its creator. And so with overwhelming awe and wonder I am led to the inescapable conclusion, that the uncharted genius in our race is simply a dim, fingernail-sized reflection of the incomprehensible brilliance of our Designer.

And that is why I believe, that we can never be saved until we finally discover, like the builders of that Babylonian Tower did so long ago, that we simply can’t save ourselves. We need a Savior.

Golf-ball Godliness

"Let us throw off everything that hinders...."

If I read that right, that means we are to:

1. "*THROW* off the hindrances."
Not just set them aside or hide them where we can reach them when we want, or rearrange them on our desk. We need to remove them as far from us as we can. THROW 'em!

2. "Throw off *ALL* the hindrances."
EVERYTHING that hinders. I pray that God would scour my life with his spotlight and reveal anything and everything that would keep me from running the race. I don't just want to get rid of the obvious and onerous things, but everything that could possibly slow me down. EVERYTHING.

3. "Throw off everything that *HINDERS*."
That's the word that really gripped me. We're not just called to get rid of the sin (that so easily entangles), but anything that even hinders us in any way from being the men of God He designed us to be. Just because it's not sinful doesn't mean that it doesn't have to go.

I watched an interesting scientific documentary last night for a half hour or so. At one point in the show they went to a golf ball factory in which a golf ball hitting machine demonstrated the difference between a smooth golf ball and a dimpled one. The two balls were identical in all ways except for the dimples. The one that had all those little craters in it went TWICE as far as the smooth one. I won't bore you with the aerodynamic principles, but what struck me was that in order to make a champion ball, the golf ball maker had to painstakingly scrape out every little hindrance that would hold that ball back.

My prayer is that God would not stop with just removing the sin from our lives but that He would make us golf balls: that He would carve out everything that would impede our flight. And I realized that it may not be one or two major amputations, but perhaps instead just several dozen "little" things.

Lord, reveal to me every hindrance that has to go!

Manifest Presence

Perhaps one of my earliest and most momentous spiritual revolutions came as I read these words of A.W.Tozer. He compared the true purpose of the Christian life to the experience of a Hebrew priest in the tabernacle. The tabernacle, of course, was God's chosen location (in the Old Testament) to manifest Himself in palpable, experiential presence. Tozer describes what a worshipping priest would have experienced in that Holy Place:

Though the worshipper had enjoyed so much, still he had not yet entered the Presence of God. Another veil separated him from the Holy of Holies where above the mercy seat dwelt the very God Himself in awful and glorious manifestation. While the tabernacle stood, only the high priest could enter there, and that but once a year, with blood which he offered for his sins and the sins of the people. It was this last veil which was rent when our Lord gave up the ghost on Calvary, and the sacred writer explains that this rending of the veil opened the way for every worshipper in the world to come by the new and living way straight into the divine Presence.
Everything in the New Testament accords with this Old Testament picture. Ransomed men need no longer pause in fear to enter the Holy of Holies. God wills that we should push on into His Presence and live our whole life there. This is to be known to us in conscious experience. It is more than a doctrine to be held, it is a life to be enjoyed every moment of every day.

--"The Pursuit of God", AW Tozer

These last words refer to Hebrews 10, where the "sacred writer" invites us -- indeed, urges us -- to boldly enter into that very Presence -- the Manifest Presence of God. What an extraordinary privilege!

Brudda Lawrence

"Our purpose in living -- our only business -- is to love and delight ourselves in God. The end we ought to propose to ourselves is to become in this life, the most perfect worshipers of God we can possibly be, as we hope to be through all eternity."

Brother Lawrence, Practicing the Presence of God