Before & After Media (DAC at UCI)

Ian Bogost and I just gave a talk on platform studies at UC Irvine’s Center for Computer Games and Virtual Worlds. We talked about our book on the Atari VCS, Racing the Beam, and about the platform studies concept more generally. A nice crowd came out on the rainy Friday afternoon and engaged us in some good discussion afterwards. Although we’ve both talked about the book and platform studies in several different places, this was the first talk we’ve given together. I think it worked well, but I guess writing a book together is good preparation.

We’re giving another join talk at Digital Arts and Culture (“After Media”), which starts this evening and then runs for three days of panels (which include scholarly and artists’ talks) and more unlikely presentations in the evenings. Besides my paper with Ian on platform studies misconceptions, I have another co-authored paper with Alex Mitchell on interactive fiction development systems, a “solo” paper on minimal poetry generators (the ppg256 series), and a reading at the DAC Literary Arts Extravaganza. I’m looking forward to seeing a slew of digital media folks and to enjoying the program, the company, and the Southern California environment – even if it keeps raining.

One Reply to “Before & After Media (DAC at UCI)”

  1. Great presentation. I have so much more respect for the AVS. So much can be learned about video games by studying the AVS. Really opened my mind to all the different factors that contribute to why video games are what they are and how they came to be in the first place. Thanks for coming to UCI!

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.