CriticalSoftwareThing

Critical Software Thing

Critical software thing is a collective of artists/practitioners/researchers interested in thinking 'thing' from the perspective of Software Studies. The group of PhDs and post-docs emerged from Transmediale art events held in Hong Kong (2014) and Berlin (2015), and began as a series of discussions and shared set of interests around the notion of “execution” and a question of what exactly execution is and where something like a computer program might be understood to execute. We meet regularly, both online and offline, for example during the Click Festival (2015), having readings groups, discussing works in progress, editing collaboratively and organising workshops and symposia related to the main theme. This event (*.exe ver0.1) is the first in a series of events/activities which focus on execution as explored through practice and theory. It will be followed by an event (*.exe ver0.2) held in Malmö in April 2016. The group is working on a book project going under the provisional title of Executing Practices/Executing Things (as part of the Data Browser series).

For more details on members and their contributions please see http://softwarestudies.projects.cavi.au.dk/index.php/CriticalSoftwareThing

These are the events that are in our roadmap:

• Workshop in Click Festival, Denmark on 16 May 2015
• *.exe (ver0.1): PhD Masterclass, open workshops and open seminars in Aarhus University, Denmark on 3-4 Dec 2015. Organized by Critical Software Thing / Aarhus Team: Winnie, Audrey, Lea, Thomas and Fran
• *.exe (ver0.2): Open workshops and open seminars in Malmö University, Sweden on Apr 2016
• *.exe (ver0.3): Tentatively on Jul, 2016
• *.exe (ver0.4): Tentatively on Jan, 2017

The members of Critical Software Thing are:

Academics/Artists/Practitioners/Researchers

Name	Affiliation	Based	Abstract idea
Audrey Samson	City University of Hong Kong	Montreal, Québec	The execution in transmission
Eric Snodgrass	Malmö University, Sweden	Sweden	the site of execution
Helen Pritchard	Goldsmiths, University of London/ Queen Mary, University of London, UK	UK	Toxic Execution
Fran Gallardo	Queen Mary, University of London, UK	London, UK	The Tongue as a radical site for execution
Lea Muldtofte Olsen	Aarhus University, DK	Denmark	execution as enunciation
Linda Hilfling	Malmö University, Sweden	Berlin, Germany	executed critique
Magda Tyzlik-Carver	Aarhus University, Denmark	UK	Executing their role: participation as algorithmically defined requirement or the human contagion
Thomas Bjørnsten	Aarhus University, Denmark	Aarhus, Denmark	1980s datasette game-execution
Winnie Soon	Aarhus University, Denmark	HK/DK	Draft: Live Execution: The temporality of buffering in distributed networks, Draft 2: At the time of execution:throbber.start()

Critical Software Thing also collaborates and works with other researchers and practitioners:

Academics/Artists/Practitioners/Researchers

Name	Affiliation	Based
Christian Ulrik Andersen	Aarhus University, DK	Aarhus, Denmark
Geoff Cox	Aarhus University, DK	Aarhus, Denmark
James Charlton	Transart Institute and Plymouth University	Auckland, New Zealand
Gottfried Haider	Institute of Network Cultures	Netherlands
Søren Pold	Aarhus University	Aarhus, Denmark
Cornelia Sollfrank	artwarez	Berlin, Germany
David Gauthier	Universiteit van Amsterdam	Netherlands
Brian House	Brown University	USA
Marie Louise Juul Søndergaard	Aarhus University	Denmark
Kyle McDonald	Brooklyn, NY	US
Molly Schwartz	Malmö University	Sweden

Meeting Agenda (record)

see all the past records here

notes on Assigned Reading

• Luciana Parisi & Beatrice Fazi, "Do Algorithms Have Fun? On Completion, Indeterminacy and Autonomy in Computation"
• Turing, "On computable numbers, with an application to the Entscheidungsproblem"

Suggested Reading

• Bolter, J D. 1984. Turing's Man: Western Culture in the Computer Age. //the book mentions fetch and execute that i found extremely interesting. it explains the operation of computational execution. I am also thinking turning back to Turing machine, might help to understand more on machine operation.
• Chun, W. 2011. “On Sorcery and Source Codes” chapter in Programmed Visions. MIT Press.
• Dufrenne, M. 1973. The Phenomenology of Aesthetic Experience.
• Esposito, Elena. 2014. Virtual Contingency – Digital Techniques of Remembering and Forgetting. video
• Wikipedia, “Execution (computing)”
• Hayles, K. Cognition Everywhere: The Rise of the Cognitive Nonconscious and the Costs of Consciousness, Volume 45, Number 2, Spring 2014.
• Kirschenbaum, M. 2007. Mechanisms. MIT Press.
• Kitchin and Dodge. 2011. Executive Code. < Kitchin, Rob and Dodge, Martin. CODE/SPACE: Software and Everyday life (Massachusetts Institute of Technology, 2011).> //the book is about spatiality in relation to code and they use the term executive code.
• Laughlin, R. B., et al. 2000. The Middle Way
• Kafka, Franz. 1914. In the Penal Colony.
• Mackenzie, A. ”Opening code: Expression and execution in software”, in: Cutting Code (Peter Lang International Academic Publishers, 2006), p. 21-42.
• Marino, M. Field Report for Critical Code Studies 2014 by Mark Marino //think is more an overall of the development of the field critical code studies.
• Nakamura, L. 2011 “Indigenous Circuits: Navajo Women and the Racialization of Early Electronics Manufacture”
• Parisi L. (2013) Contagious Architecture: Computation, Aesthetics, and Space, MIT Press.
• Parisi, L. In Fun with Software: Do Algorithms Have Fun? On Completion, Indeterminacy and Autonomy in Computation Luciana Parisi and M. Beatrice Fazi pp.109 - xxx here
• Turing, A. (1936) "On Computable Numbers, with an Application to the Entscheidungsproblem" (http://www.cs.virginia.edu/~robins/Turing_Paper_1936.pdf)
• Harold Abelson and Gerald Jay Sussman with Julie Sussman, Structure and Interpretation of Computer Programs (2nd ed.) here “The pc register determines the sequencing of instructions as the machine runs. This sequencing is implemented by the internal procedure execute. In the simulation model, each machine instruction is a data structure that includes a procedure of no arguments, called the instruction execution procedure, such that calling this procedure simulates executing the instruction. As the simulation runs, pc points to the place in the instruction sequence beginning with the next instruction to be executed. Execute gets that instruction, executes it by calling the instruction execution procedure, and repeats this cycle until there are no more instructions to execute (i.e., until pc points to the end of the instruction sequence).” (section 5.21 - The Machine Model)
• Schuppli, S. 2014. Deadly Algorithms: Can Legal Codes hold Software accountable for Code that Kills? Deadly Algorithms: Can Legal Codes hold Software accountable for Code that Kills?
• Stengers, I. Ecosophical activism - between micropolitics and mesopolitics
• Stengers, I. History through the Middle: Between Macro and Mesopolitics