Lucid Green

Matt Ward has written a very nice article over at Smashing Magazine examining some of the similarities between code and poetry. It is an excellent article, but I must respectfully disagree. There are similarities between code and poetry, as Matt and others have seen, but these do not make code poetry (as claimed by WordPress’ famous tagline). Here are two reasons why:

A Categorical Difference

Following the ancients, we must distinguish between Craft and Art. Both are skillful endeavors that require mastery to do well, but they differ in purpose. Arts are pursued for their own sake, while crafts are pursued for the sake of utility.

Craft is done for the sake of some other goal. An excellent shoemaker, for example, is a craftsman because he creates shoes to be worn, and we judge a shoe’s excellence based on how well it serves its function. We never purchase a shoe just to hang on our wall. No, a great shoe is one that is comfortable, wears well, and looks great. A craft’s value and excellence lies in its utility.

Art, on the other hand, is done for its own sake. An excellent painter creates his paintings to be enjoyed in-and-of-themselves. There is no other purpose for his art. We judge a paintings excellence not on how well it sells beer (that would be commercial art, a craft), rather we judge its excellence based on how much we enjoy looking at it. In other words, an excellent painting is an enjoyable painting.

Code is craft. No one writes code so that the code itself can be enjoyed. It is written to perform some job. That is not to say that code cannot be beautiful. There is a distinct difference between beautiful and ugly code, but at the end of the day code is judged based on how well it performs its job. In fact, beautifully structured code that doesn’t work is worse than ugly, difficult to maintain, code that does. We can even say that beautifully structured code that doesn’t work isn’t actually “beautiful” at all, for the simple reason that it is flawed and doesn’t do what it’s suppose to do. The very question of what it means for code to be beautiful is bound up in the question of whether or not it fulfills it’s purpose.

Poetry is art, at least good poetry is. It is written to be enjoyed in its own right. Its beauty does not rest in utility but in itself.

The question of meaning

Code and poetry differ in many other more specific ways as well. But I want to deal with only one that Matt perceived to be a similarity: meaning. Matt argued that just as poetry has multiple levels of meaning, so code can impart varying meaning to content. He attempted to compare a poem’s literal and figurative meaning to some code’s semantic value.

He gave these two examples of HTML code to illustrate code’s ability to imbue content with different meanings:

<p>The Wasteland</p>
<h1>The Wasteland</h1>

I agree with Matt’s basic contention about this code: the displayed text is the same on both lines but the “meaning” is different. Obviously the first is paragraph text, and the second is a top-level heading. But these two lines are distinctly different lines. The one does not imply the other. One does not “figure” the other. Strictly speaking, considered as code, the content of each line is not the same. Each line can mean one and only one thing and it is different for each.

If this were not the case then code would be useless. Ambiguity in code is deadly. Just imagine the nightmare of trying to debug code in which a single line could be interpreted in 2 (or heaven forbid more) ways at the same time in the same context! But ambiguity is a strength in poetry. Ambiguity is poetry. The poet’s ability to give the same words multiple meanings at the same time is what makes a good poem good! Ambiguous figurative language is poetic language.

just look again at the example of poetry Matt provided. He quoted the following lines from Robert frost:

The woods are lovely, dark, and deep,
But I have promises to keep.
And miles to go before I sleep,
And miles to go before I sleep.


We could unpack the meaning of these lines for hours. What do the woods signify? Why are they lovely, but also dark and deep? Does sleep refer to death, or to the comforts of home, or both? We cannot derive the same joy from the lines of HTML code quoted above, nor would it be good if we could.

Code is not poetry. It can be excellent, beautiful even, but its beauty must be judged by a different standard than the beauty of poetry. Code is craft, poetry is art. Excellent code is certainly worthy of pursuit, laudable to master, but it will never be art. Speaking as one who loves to code, but hates to debug it, I’m thankful that is so.

After reading this post about Google’s “suggest” feature, I was inspired to do a little experimentation of my own. What I found was very intriguing.

You are probably already familiar with Google’s suggest feature. As you type anything into Google’s search box, it automatically suggests completions based on the most popularly searched phrases. For example, type in “how to”, and Google will helpfully suggest “how to tie a tie“, and “how to kiss“. Clearly there are a lot of men who need to know how to impress their date!

Instead of questions, however, I wondered what would happen if I started typing in numbers? So I started with “1″ and just kept going. Try it yourself, but be aware that there is often a big difference between just the number (i.e. “1″) and the number with a space after it (i.e. “1 “). Be sure to do them both as you go along.

What I found interesting is that somewhere between the number “4″ and the number “11″, the phrase “X weeks pregnant” begins to show up every time. By number “13″ or “14″ that phrase is near the top and stays there until you hit “41″, especially when you insert a space after the number. Around the number “26″ you start seeing other issues concerning pregnancy, such as “weight gain”, and “what to expect”, or “fetal pictures”. This is a fascinating insight into what concerns women when they are pregnant. The closer you get to “40″ you can almost sense the desperation set in, it’s surreal.

I haven’t systematically worked through the 3 digit numbers, but I didn’t immediately discern any trends between 42 and 100. Most of the 3 and 4 digit numbers appeared to be address searches, and of course, 5 digit numbers tended to be zip code inquires.

The address results are interesting. Why are some addresses searched enough to make it on this list? Try “3837″ for example. For me it returned addresses from California, Texas, and Illinois. What is so interesting about “3837 bayview circle concord ca”? Google maps doesn’t list any businesses near that address. In fact, it’s a relatively normal looking house; you can see it on street view. Who lives here, and why is he so interesting?

Have you found any strange numerological insights or quandaries in Google’s “suggest” feature? Let me know in the comments