See the Pen liberation by Andrew Aquino (@dawneraq) on CodePen.

This is my first crack at code poetry. It was an Art & Code & Interactivity assignment, so naturally, the requirements were few and highly open to interpretation:

  1. It must be “code”
  2. It must be a “poem”
  3. It must run, which implies that it may need to compile, further implying instructions may be necessary

In fact, I consider this our most enigmatic assignment. For context: our professor Shawn tasked each of us with having a friend select a random chapter to read from Italo Calvino’s Cosmicomics. Pretty surreal stuff.

But how does one write code poetry?

One example procedural implementation of printed a slightly different poem based on the value of randomly generated numbers, a kind of choose-your-own adventure poem where the compiler chooses the adventure for you. Going a little deeper, instead of random numbers deciding the outputted poem, you could generate poetic output from a knowledge graph of philosophical boolean conditions, e.g. if (youDidYourBest) today = 'good';.

At first I was lost. I didn’t feel very inspired by the example poems we saw in class, until Shawn showed us, a collection of a dozen unique code poems. One that stuck out to me in particular was titled bark.png:


Hatcheting the bark
Her red hands blister
The rotten wood falls away

The image encodes assembly instructions to print out the above haiku using an esoteric programming language called Piet. Dude, what?! Let that sink in for a moment. Piet is a Turing-complete language, so it can do anything from approximating pi to telling someone you love them. bark.png’s author Daniel Holden has an in-depth explanation at his site of how the image was made. Piet is one hell of a rabbit hole into which I will someday dive…

Anyway, I got really hooked on the visual aspect of things, but I didn’t just wanna copy Daniel’s idea. (If you read the explanation, you’ll also see that requires a jaw-dropping attention to detail that I just did not have time for.) I was still lost, until suddenly something clicked. Similarly to when I stopped using LaTeX to write my resume, I realized that I already know how to arrange and style stuff using HTML and CSS. As for making those two languages more human-readable and hopefully more poetic, I’d learned how to use the SASS CSS preprocessor in the previous semester, and its HTML equivalent Pug over the summer. So I had execution covered.

All I needed now was an idea.

A post shared by 𝔞𝔰 𝔞𝔟𝔬𝔳𝔢 𝔰𝔬 𝔟𝔢𝔩𝔬𝔴 (@tremulant_) on

I eventually found inspiration from this photo taken by a friend of mine. Dagger through a smartphone? Seems like an interesting logo. Some minor digging revealed it to be that of a brand called KILL YOUR GOD. I admit some of their edgy black merch looks kinda dope. But I couldn’t help but feel it was somewhat pretentious too. I’ve heard the urgent cries from (some former) tech giant employees about how the addictive nature of social media is creating a dystopia, but come on. The header on KILL YOUR GOD’s landing page is an invitation to consume more social media. It’s almost as if supporting this brand’s message requires buying into the very things their image is against. Obviously these guys don’t want you to literally stab your smartphone. How could you, right after following them on Instagram and Facebook?

A bit of research on CSS-animated flames later, and voila. I’m not anti-anti-smartphone. They’re important communication tools that can sometimes suck us in a little too much. South Park season 20 already illustrated what it’s like to overdramatize quitting social media. Think of liberation as a simpler cautionary tale.

Andrew Aquino

Andrew Aquino

Frontend developer + UX designer

rss facebook twitter github youtube mail spotify instagram linkedin google google-plus pinterest medium vimeo stackoverflow reddit quora flickr