Free beta access. 50 free AI tokens each week. Optional top-ups available. See what is included
Opening Word document…

Only a software based analysis can provide a better understanding of technology in the world

Frabetti 14 (Federica Frabetti PhD - MRes and PhD in Media and Communications at Goldsmiths, University of London, “Software Theory”, Rowman and Littlefield International Ltd, Pages xv-xix, 2014, MG)

This ambivalence—one could even say, this circular movement—between the technical and the social seems to me to characterize the whole field of software and code studies. Individual academic contributions can choose to privilege one term over the other, but ultimately they turn to the technical in order to explain the social, and then revert to the social in order to explain the technical. Representative of a stronger emphasis on the technical aspects of new technologies are studies such as Nick Montfort and Ian Bo- gost’s 2009 book on the Atari video computer system, entitled Racing the Beam, which has been positioned as the inaugural text of platform studies. Overlapping with software studies, platform studies pays particular attention to the specific hardware and software systems on which ‘expressive computing’ (another name for Manovich’s ‘cultural software’—that is, software applications for video games, digital art, and electronic literature) is based. Montfort and Bogost recommend ‘delving into the code’ and giving ‘serious and in-depth consideration [to] circuits, chips, peripherals and how they are integrated and used’ in order to make sense of new media.22 Also intent on the functional unpacking of technology is the classical work of Alexander Galloway, Protocol (2004), which offers a welcome counterargument to the widespread discursive use of digital networks as metaphors of horizontal connectivity and intrinsic political empowerment. By unpacking the hierarchical workings of ‘real’ networks, which are functionally based on layers of software that ‘wrap up’ the contents of communication, Galloway also unpacks and critiques the rhetoric of freedom that surrounds digital networks. For instance, he demonstrates how protocols incorporate (‘embed’) censorship and other mechanisms of distributed control, and how these technical characteristics embody a logic of governmentality which he ultimately associates with the military origins of the Internet. ‘Distributed networks’, Galloway states, ‘are native to Deleuze’s control society.’ 23 In sum, for Galloway, discovering the control mechanisms which found the technical functioning of networks is a way to complicate the political discourse on networks inside and outside the academy. Although Galloway’s approach remains very important and politically meaningful for the cultural study of software, it also runs the risk of positioning the technical as the ultimate truth, as showing what ‘truly’ lies behind any discourse on technology (celebratory or otherwise). In the end, this approach rests on a strategy that draws on technical explanation as a way to reach a ‘deeper’ understanding of technology—an understanding supposedly located ‘behind’ or ‘beyond’ the social.

This ‘quest for depth’ in the analysis of software, which positions software as the truth of new technologies while also intertwining software with issues of ‘power’ (or ‘biopower’), ‘control’ and ‘governmentality’, is also present in more socially orientated studies of software, such as David Berry’s 2011 book, The Philosophy of Software. For Berry, in order to understand the way in which one experiences software today and to develop a ‘phenomenology of software’, software studies need to ‘unpack’ software, to understand what it ‘really does’, to reach a technical grasp of it.24 Yet, again, this process of unpacking leads to the analysis of the practices of production, usage, and consumption that shape and are shaped by software. Importantly, according to Berry, such a deeper understanding of software—which, for instance, unmasks the decisions made by big corporations such as Google with regard to their software—is ultimately an emancipatory practice, because it leads individuals to better-informed political decisions. An analogous emancipatory aim characterizes Robert Kitchin and Martin Dodge’s book, Code/Space (2011), which investigates the way in which software shapes social space by enabling ‘forms of automation, the monitoring and controlling of systems from a distance, the reconfiguring and rejuvenation of established industries, the development of new forms of labor practices and paid work, the reorganization and recombination of social and economic formations at different scales’ and many other innovations.25 Kitchin and Dodge develop the idea of ‘automated management’ in order to explore how software enables a whole new range of movements and transactions across space while also automatically and systematically capturing and storing data on these transactions, thus bringing about new opportunities for personal and collective empowerment which are also new possibilities for regulation and control.

The intertwining between digital technologies and power is also at the core of the articulated analysis of software offered by Wendy Chun in her recent book, Programmed Visions (2011). Chun argues that computers, and particularly software, ‘embody a certain logic of governing or steering through the increasingly complex world around us’, which she calls ‘the logic of programmability’. 26 Programmability gives users a sense of empowerment by ultimately incorporating them into the logic of a machine that they do not fully understand but feel somewhat in control of. In other words, we feel empowered by software because we feel in control of something we do not have a grasp of. In fact, Chun argues that our fascination with software resides precisely in the fact that we do not understand it. Instead, we view it as something hidden, obscure, difficult to pin down, and generally invisible, which nevertheless generates visible effects in the world (for instance, lights flickering on a screen or the functioning of telecommunication networks). Rather than aiming at dispelling the mysteriousness of software, she analyzes how software functions as a ‘metaphor of metaphors’ in a number of discourses and fields of knowledge precisely because of its relative obscurity. She writes: ‘[Software’s] combination of what can be seen and not seen, can be known and not known—its separation of interface from algorithm; software from hardware—makes it a powerful metaphor for everything we believe is invisible yet generates visible effects, from genetics to the invisible hand of the market; from ideology to culture.’ 27 Although critical of those approaches of software studies that view knowing software as ‘a form of enlightenment’, in her own analysis Chun still combines historical-cultural narratives (for instance, the history of programming languages) with technical explanations (for instance, the exposition of how digital circuits work) in order to complicate her cultural account of technology and particularly of software.

This political commitment with the analysis of software has been taken further by a number of studies on software which draw on neomaterialism, media archaeology, and object-oriented philosophy.28 In their quest for thinking software as a material entity or process which spreads into economics, politics, and—again—the whole logic of control society as an ‘immanent’ force understood in a Simondonian and Deleuzian sense, these studies tend to ‘ontologize’ software as the condition of possibility of contemporary life, and to privilege software studies as a master discourse capable of making visible the foundational but otherwise invisible, hidden, embedded, off-shored, or forgotten nature of software and code. And yet, one could ask: To what extent can software and code be privileged in this respect? On what basis can they be said to constitute the conditions for revealing the truth of human life or society?29

So, to recap, not only is the number of existing studies of software still relatively limited, but these studies also give an account of software that is based on the analysis of the processes of software production, reception, and consumption combined with the technical exposition of how software ‘really’ works (either as a technical artefact or as the all-pervasive logic of control societies). Although I recognize that the above perspective remains absolutely relevant to the political and cultural study of technology, I suggest that this approach should be supplemented by an alternative, or I would even hesitantly say more ‘theoretical’, and yet more ‘direct’, investigation of software—although I will raise questions for both these notions of ‘theory’ and ‘directness’ later on. As I have suggested above, in order to understand the role that new technologies play in our lives and the world as a whole we do need to shift the focus of analysis from the practices and discourses concerning them to a thorough investigation of how new technologies work, and, in particular, of how software works and of what it does. And yet, in Software Theory I propose an investigation of software that takes historical-cultural and technical narratives as a starting point, rather than as a final one, and I suggest that these narratives should be problematized rather than treated as explanatory. Such an investigation of software will help me to problematize the intertwining of the technical and the social aspects of software which currently preoccupies Software Studies. At the same time, I will refrain from making any sweeping ontological claims about what software is and will instead engage in a critical examination of the alleged relations between ‘software’/’code’ on the one hand and ‘ontology’ and ‘materiality’ on the other hand, as conceptualized by cultural theorists of computation such as Katherine Hayles. This is why earlier on I suggested that the title of this book, Software Theory, hints at a different engagement with theory from what Lev Manovich had in mind.30 Let me now explain how such an investigation of software can be undertaken.

Sign in to recut, update, or save this card.