[…] In previous posts on this site (1, 2) , I have outlined some of the basic proposal for Critical Code Studies (CCS), and the fullest articulation appears in the electronic book review, here. Last year at MLA and more recently at SLSA, I offered more of the fundamentals and met many who expressed interest in or affinities for the project. Here, I am announcing a new blog that will be a hub of CCS work, known as CriticalCodeStudies.com. […]]]>
[…] [This post follows up on two previous posts on WRT. Here are the original posts ( 1, 2 )and a follow-up post by Jeremy.] Critical Code Studies first began as an inspiration here on WRT. This December marks the formal launch with the publication of “Critical Code Studies” in the electronic book review and with Rita Raley’s “Reading Code” panel at MLA 2006 in Philadelphia. What is Critical Code Studies? […]]]>
I must say that beyond the code of bots is the code of any online or digital work. Whenever I review or explore an online work I check the code and do a web-suck (I use Internet Researcher software) of all the sites associated with it. I find out the sites that are meant to be surprises, but for me that is part of a ‘game’. I get to outsmart the author but have the joy of seeing how the sites are integrated into the work. This sneaking around, or jumping the gun, is what ‘gamers’ who follow ALG (Alternate Reality Games) games do: the ‘detective’ urge to discover what happens moves beyond the ‘inside the skull’ deduction to ‘outside the skull’ hacking. Designers of such games anticipate and encourage these ‘hacks’: leaving clues and messages in the source code. Where do we draw the line then: what is really metadata and what isn’t? Critical Code Studies says all data is relevant and pivotal to the ‘reading’. Or does it?
Over to you…]]>
I see great potential in the commentary on potential code (code not yet put into application). In terms of “commentary,” I want to emphasize that this would be an interpretive process rather than a proscriptive or descriptive process. You would read something out of the code rather than map out its features. Or better said, this approach would see all code as signifying more than its functions.
Re: scriptons. If I follow your question, yes– as a performance (although this word may have a certain hermeneutic specificity that I don’t want to limit CCA to just yet.
N. Katherine Hayles seems to perfrom CSA regularly and perhaps “Lexia to Perplexia” suggests that the lins between science and creative, code and text, is dotted at best. I’m sure there are others: Bolter, for example? Perhaps all of us New Media types. But I’m not sure I’ve seen the approach articulated as a methodology, as a critical approach. Jeremy?]]>
Fascinating stuff Mark. Perhaps add ‘visualisation’ to the list of objects to study in CCS? I’d like to tease out more about CCS — so the analysis errs on the side of experience with applying it? What about analysis of code you haven’t used? I guess this is like reviewing a book you haven’t read! But aren’t there 2 levels to code analysis: commentary on an approach (that you may or may not have tried) and commentary on the actual code (which is rampant in developer lists)?
And by scriptons — does this mean code is studied as a performance of sorts too?
And CSS is a methodology that someone somewhere must have broached. I’d love to find out…Anyone?]]>