Press "Enter" to skip to content

Daybook Posts

A Note on Procedural Literacy

The Clearance of the Porcelain Dogs
The Clearance of the Porcelain Dogs flickr photo by mcmorgan08 shared under a Creative Commons (BY-SA) license

We don’t need no coding knowledge to read. Except

In this view, programming has almost no connection with theoretical and philosophical considerations, with concept and aesthetics, with a design focus on human action and interpretation. This attitude is often adopted by new media scholars and practitioners, including game designers and game studies scholars, who may assume that the “mere” technical details of code can be safely bracketed out of the consideration of the artifact. …

By procedural literacy I mean the ability to read and write processes, to engage procedural representation and aesthetics, to understand the interplay between the culturally-embedded practices of human meaning-making and technically-mediated processes. With appropriate programming, a computer can embody any conceivable process; code is the most versatile, general process language ever created. Hence, the craft skill of programming is a fundamental component of procedural literacy, though it is not the details of any particular programming language that matters, but rather the more general tropes and structures that cut across all languages.

Procedural Literacy: Educating the New Media Practitioner – Michael Mateas | ETC Press

Summer Reading

A few newish works of digital lit for summer.

The iPad and iPhone are closed systems so we have to wait until the artists get involved to make them do something interesting.

  • Wikipedia: The Text Adventure, by Kevan Davis. Start at a selected place and work your way … to someplace else. Source: Kevan.org

The web is an open system, but it takes an artist with programming knowledge to adapt existing content to purpose.

All three are in the same ilk as A Humament, by Tom Phillips, and work by J R Carpenter.

Daybook Disconnect

It happens to a lot of blogs. Mike Caulfield posts about it. A problem with a server or possible hack. Fixing it in this case ended up in losing track of the database. I had to reinstall WP and can’t get the new install to talk to the old database.

But I don’t see this as a problem. Stuff isn’t lost. It’s just not connected right now. It may be. Later. It’s in a trunk somewhere in an attic / basement / garage / lockup / underneath the stairs. A data horde. Bring in a detectorist.

The old install of WordPress (2005?) had a lot of cruft tangling it up, so it’s nice to see the old code gone.

And gone is the old paratext junk, too. Poor categories and tags. Trials with plugins. Bad back end decisions that need a ripping out of old structure to rebuild. Choices made naively. Bad ideas gone bust from the first. Pied type cases. Flotsam. Jetsam. Ruins shored against. Centers not holding.

Not that a restart means any further success. It just feels a little better.

So hello Daybook.