Critical Code Studies: initial(methods) (Software Studies)

**An argument that we must read code for more than what it does--we must consider what it means.**Computer source code has become part of popular discourse. Code is read not only by programmers but by lawyers, artists, pundits, reporters, political activists, and literary scholars; it is used in political debate, works of art, popular entertainment, and historical accounts. In this book, Mark Marino argues that code means more than merely what it does; we must also consider what it means. We need to learn to read code critically. Marino presents a series of case studies--ranging from the Climategate scandal to a hactivist art project on the US-Mexico border--as lessons in critical code reading.Marino shows how, in the process of its circulation, the meaning of code changes beyond its functional role to include connotations and implications, opening it up to interpretation and inference--and misinterpretation and reappropriation. The Climategate controversy, for example, stemmed from a misreading of a bit of placeholder code as a "smoking gun" that supposedly proved fabrication of climate data. A poetry generator created by Nick Montfort was remixed and reimagined by other poets, and subject to literary interpretation.Each case study begins by presenting a small and self-contained passage of code--by coders as disparate as programming pioneer Grace Hopper and philosopher Friedrich Kittler--and an accessible explanation of its context and functioning. Marino then explores its extra-functional significance, demonstrating a variety of interpretive approaches. "Critical Code Studies (CCS) names a set of methodologies for the exploration of computer source code using the hermeneutics of the humanities. Like "10 PRINT CHR$ (205.5 + RND (1)); : GOTO 10," Mark Marino's Critical Code Studies treats code not as merely functional but as a text, one that can be read, and misinterpreted, by non-programmers. As the author notes, code's "meaning is not determined entirely by the programmer's intention but also by how it is received and recirculated. That is not to argue that code can be taken out of context or that code means whatever people say it means but rather that the meaning of code is contingent and that code is subject to the rhetorical triad of speaker, audience (both human and machine), and message." It is time to develop methods of tracing the meaning of code. Computer source code has become part of our political, legal, aesthetic, and popular discourse. Code is being read by lawyers, corporate managers, artists, pundits, reporters, and even literary scholars. Code is being used in political debate, in artistic exhibitions, in popular entertainment, and in historical accounts. As code reaches more and more readers and as programming languages and methods continue to evolve, we need to develop methods to account for the way code accrues meaning and how the readers and shifting contexts shape that meaning. We need to learn not only to understand the functioning of code but the way code signifies. We need to learn to read code critically. Critical Code Studies offers a CCS "starting kit," a set of techniques that scholars and other interested parties can use to interpret code in a non-computational context"-- Résumé de l'éditeur "Critical Code Studies (CCS) names a set of methodologies for the exploration of computer source code using the hermeneutics of the humanities. Like 10 PRINT CHR$ (205.5 + RND (1)); : GOTO 10, Mark Marino's Critical Code Studies treats code not as merely functional but as a text, one that can be read, and misinterpreted, by non-programmers. As the author notes, code's "meaning is not determined entirely by the programmer's intention but also by how it is received and recirculated. That is not to argue that code can be taken out of context or that code means whatever people say it means but rather that the meaning of code is contingent and that code is subject to the rhetorical triad of speaker, audience (both human and machine), and message." It is time to develop methods of tracing the meaning of code. Computer source code has become part of our political, legal, aesthetic, and popular discourse. Code is being read by lawyers, corporate managers, artists, pundits, reporters, and even literary scholars. Code is being used in political debate, in artistic exhibitions, in popular entertainment, and in historical accounts. As code reaches more and more readers and as programming languages and methods continue to evolve, we need to develop methods to account for the way code accrues meaning and how the readers and shifting contexts shape that meaning. We need to learn not only to understand the functioning of code but the way code signifies. We need to learn to read code critically. Critical Code Studies offers a CCS "starting kit," a set of techniques that scholars and other interested parties can use to interpret code in a non-computational context"-- Provided by publisher An argument that we must read code for more than what it does--we must consider what it means. Computer source code has become part of popular discourse. Code is read not only by programmers but by lawyers, artists, pundits, reporters, political activists, and literary scholars; it is used in political debate, works of art, popular entertainment, and historical accounts. In this book, Mark Marino argues that code means more than merely what it does; we must also consider what it means. We need to learn to read code critically. Marino presents a series of case studies--ranging from the Climategate scandal to a hactivist art project on the US-Mexico border--as lessons in critical code reading. Marino shows how, in the process of its circulation, the meaning of code changes beyond its functional role to include connotations and implications, opening it up to interpretation and inference--and misinterpretation and reappropriation. The Climategate controversy, for example, stemmed from a misreading of a bit of placeholder code as a "smoking gun" that supposedly proved fabrication of climate data. A poetry generator created by Nick Montfort was remixed and reimagined by other poets, and subject to literary interpretation. Each case study begins by presenting a small and self-contained passage of code--by coders as disparate as programming pioneer Grace Hopper and philosopher Friedrich Kittler--and an accessible explanation of its context and functioning. Marino then explores its extra-functional significance, demonstrating a variety of interpretive approaches.