10 PRINT in enculturation

I don’t seem to have linked to this yet, but there’s a thorough review, by Chris Lindgren, of my and my nine co-authors’ book 10 PRINT CHR$(205.5+RND(1)); : GOTO 10 in the journal enculturation. Here are the final sentences of it:

>The book is a rich example of what a possible fusion of theory and techn? might look like in future academic scholarship. In the conclusion, the 10 argue that “reading this one-liner also demonstrates that programming is culturally situated just as computers are culturally situated, which means that the study of code should be no more ahistorical than the study of any cultural text” (262). Code is a text, but, as the 10 indicate, it also operates and “can be representational” of cultural ideals, people, and things. “10 PRINT,” they conclude, “is not just a line of code; it defines a space of possible variations” (266). This insight is perhaps the most useful, since the 10 themselves produced this “assemblage of readings” from a cast of diverse scholars and scholarship. For me, as a rhetorician who is interested in literacy and the fostering of computing cultures, this assemblage also serves as a potential baseline blueprint for the means, processes, and types of cross-disciplinary relationships necessary to build an infrastructure in which Kemeny and Kurtz’s BASIC vision can come to fruition.

4 Replies to “10 PRINT in enculturation

  1. Thanks, Owen. Somehow the link to the review was cut out of the original post. The link that was there originally, and is still there as the second link, leads to a freely downloadable PDF of our book.

  2. My! Thanks for that — I’m the one being annoying, and I appreciate your pointing out problems with the link (or lack of link). Back in the day, when blogs were blogs, I used to actually check to see that the links I put in worked. And I also had a lot of fellow bloggers, and we could fix things like this for each other if we saw the problem.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax