Cultural Bloggers Interviewed Book Launch

Cultural Bloggers Interviewed

On the first day of PICNIC we celebrated the book launch of Cultural Bloggers Interviewed. In April 2009 Annette Wolfsberger interviewed me for this book about my blogging practices and experiences. The book explores the role of blogging in the cultural sector and includes cultural bloggers like We Make Money Not Art‘s Régine Debatty and Neural‘s Alessandro Ludovico.

Cultural Bloggers Interviewed

The book launch consisted of a Q&A with Annette Wolfsberger, me and Michelle Kasprzak from Curating.info. We shared our thoughts on the role and practice of blogging within the cultural sector. Reading back my own interview from almost 1,5 years ago it is a nice documentation of trying to find my way between blogging and using other social media like Twitter.

Cultural Bloggers Interviewed

Download the book as a PDF from the Lab for Culture website for free!

Life is a beta: Google Buzz’ disruptive privacy settings

What Would Google Do?

What Would Google Do? by Jeff Jarvis

I just finished reading What Would Google Do? by Jeff Jarvis and was rather disappointed. I saw Jeff Jarvis speak at the Next Web 2009 and he is an excellent speaker and certainly knows how to entertain his audience with stories. However, as a writer I am not so impressed. The book is filled with numbers and figures of revenue, clicks, marketshare etcetera. On top of that it doesn’t read like a coherent argument.

The Next Web

Jeff Jarvis at The Next Web 2009

Please note that this is not a book review but a collection of notes of everything that I got out of this book for my research. I tried a new notetaking system for my research: Evernote. Instead of underlining passages I took pictures of relevant paragraphs with my Google phone, the Nexus One (the pictures in this blog post are taken with my Nikon D90) and directly uploaded them to Evernote. Evernote makes my notes available everywhere and it applies text recognition to everything that I upload so my pictures become searchable.

Evernote text recognition

Life is a beta

In both the Perceived Freshness Fetish and Identity 2.0 I describe the web 2.0 culture as a beta culture. I would like to argue that web 1.0 was always ‘Under Construction’ while web 2.0 is always ‘In Beta.’ The main difference is the disruption of the updates for the user or visitor. Websites that are ‘Under Construction’ are unfinished or are in the process of being updated. They bear signs of inaccessible construction sites that depict roadblocks. It is a disruptive update process. Services such as Google’s products that are in a perpetual beta state are invisibly being updated. Platform updates do not go unnoticed to users (as can be seen in the case of privacy settings in Facebook and Google Buzz), but it does not immediately disrupt their webflow. Updates are less disruptive because they are being performed in the backend instead of the frontend.

The term beta is also a social construct in the Google world similar to the Under Construction signs indicating “I’m sorry” or according to Jeff Jarvis a way of not having to say sorry:

“Beta” is Google’s way of never having to say they’re sorry. It is also Google’s way of saying, “There are sure to be mistakes here and so please help us and fix them and improve the product. Tell us what you want it to be. Thanks.” (Jarvis 2009: 91)1

Google’s products often start in Google Labs before they graduate for public use. The next step is usually a few years in beta which in Google terms means that the product is mature enough for public launch but that it may come with flaws. In the summer of 2009 Google decided to remove the beta label from its major products:

Today we’re paving the road. We’re taking the beta label off of Gmail, Google Calendar, Google Docs and Google Talk to remove any doubt that Apps is a mature product suite. (Rahen 2009)2

Recent Google experiments are launched in Google Labs or labelled with a Preview label instead of a Beta label, as in the case with Google Wave. Beta, as Google’s way of not having to say sorry, seems to have disappeared. However, the introduction of Google’s new service Google Buzz forced Google to publicly say sorry to its users. The service, similar to Twitter, was introduced overnight without the infamous beta/preview logo. It just appeared as a new feature within/on top of Gmail. Its default privacy settings revealed a list of contacts of “people you email and chat with most.” After complaints from users about the sudden publication of their contactlist Google admitted the ‘Buzz social network testing flaws‘ to BBC News. Products are usually extensively tested with friends/family or a relatively small set of users in a private beta. Buzz was launched without these tests and users immediately pointed to its privacy flaws. While Google considers our life to be a beta where experimentation is key, Google Buzz showed that its users base is not quite ready or interested in living life as a beta.

 What Would Google Do?

Life is a beta

  1. Jarvis, Jeff. What Would Google Do? New York: Harperluxe, 2009).[]
  2. Sheth, Rajen. “Paving the road to Apps adoption in large enterprises.” Official Google Enterprise Blog 7 Jul 2009. Web. 26 Feb 2010.[]

Remember What You Want to Forget

Remember

Review: Software Studies a Lexicon Edited by Matthew Fuller

This review of the Software Studies Lexicon was written in June 2007 after Matthew Fuller was kind enough to send me a sneak preview pre-publication copy. I sent the PDF of the Software Studies Review to Fuller to which he replied with some insightful remarks on my suggestion for a digital working environment, see update below.

softwarestudies Fuller, Matthew. Software Studies: A Lexicon. Cambridge, USA: The MIT Press, 2008.

334 pp. $28.00 USD. ISBN-10: 0262062747

Reviewed by Anne Helmond. June 2007, University of Amsterdam

Software Studies, a forthcoming lexicon edited by Matthew Fuller, consists of thirty-nine entries from mostly different authors. The title refers both to the object of study and the form of the project consisting of numerous short studies. Each of the “software studies” in the book stands on its own and Fuller celebrates the multi-disciplinary diversity of the authors. They come from different fields of study including art and design, literary theory, computation and free and open source software. Fuller has not gone as far as to attempt to start a new field of study but instead Software Studies calls for new theorizations of software from areas that “have not historically ‘owned’ software” such as media studies. The fields that are currently concerned with culture and media could contribute to a new approach to software with their critical perspectives on politics, society and matter.

Fuller states that he has chosen the form of a lexicon because it is provisional, scalable and contains pathways. It is provisional because it serves for the time being because software is not a static object and is therefore hard to pin down. Relations in and around software are constantly changing and a lexicon can serve as a temporary overview. Unlike a dictionary a lexicon is scalable and it does not strive to be complete and this incompleteness is “a virtue” according to Fuller.  The entries can be seen as different pathways into software that do not strive to depict a whole. Connections between these pathways are made by the various authors but can also be constituted by the reader itself. In short, both software studies and the Software Studies lexicon can be seen as a specific approach whereby each entry is a pathway into thinking about software.

This approach does not seem to have a shared methodology except for creating new pathways into software. This could be due to the different backgrounds of the authors who all contribute to the discourse of software studies from their own perspective and paradigm. This is both the strength and weakness of Software Studies: at times the lexicon seems uneven with an overemphasis on computing which is a neglected aspect of software according to Fuller. However, in order to bring back this neglected aspect too many entries fall in the lexicon back on Turing et. al.

Software Studies builds on Fuller’s previous works Behind the Blip and, to a lesser extent, Media Ecologies. Behind the Blip consists of several essays on the topic of the culture of software. In the opening essay of Behind the Blip Fuller argues for a “software criticism” that moves authors writing about computers away from the performance of software towards a more critical approach. This new critical approach is not concerned with detailing the functionality of a particular piece of software but is rather concerned with the question how software consists of different elements that are embedded in a dynamic web of relations.

An excellent example of this critical approach is the essay ‘It Looks Like You Are Writing A  Letter’ that critiques the popular word-processing software Microsoft Word revealing that “software constructs sensoriums, that each piece of software constructs ways of seeing, knowing and doing in the world at once contain a model of that part of the world it ostensibly pertains to and that also shape it every time it is used.” Fuller argues that software can be seen as a synthesis, a form of amalgamation or assemblage, of different layers that do not imply a static whole. This dynamic synthesis is also the subject of Fuller’s book Media Ecologies that uses a materialistic approach to identify three forces of objects in media ecologies: affordances, material substrates and memes. In a sense, software is described as having a vitality; it derives its energy from these forces that cause collision, (dis)connection and interaction underwriting their unstable and dynamic nature.

Lev Manovich previously addressed the importance of studying software in The Language of New Media in 2001. He states that media have become programmable and that we need a new field of study to address the issues that arise from this turn in our culture. Not only has software quietly penetrated our daily life but it has also become invisible. The ubiquity and so-called transparency of software renders it invisible but at the same time it points out the importance of studying it. Manovich has studied software from a formalist approach by taking terms and categories from computer science and applying them to new media that have become programmable.  According to Manovich five principles distinguish new media from the older media  namely, numerical representation, modularity, automation, variability and transcoding (27-48). These principles point to the relation that new media and software have with code.

Adrian Mackenzie takes issue with Manovich with an interesting take on code and software in Cutting Code: Software and Sociality (2006) and notes that software is a very mutable object that is entangled in a web of relations. Mackenzie sees software as a social object and process that is intrinsically linked to code as a material and practice. He points to the problems of Manovich’s formal analysis because it abstracts software from practices and contexts surrounding coding and reduces it to “relations and operations (such as sorting, comparing, copying, removing) on items of data.” (Mackenzie 2006) These relations and operations are seen as quite stable forms and are often directly transferred from the field of computer science. Instead of abstracting and formalizing software Mackenzie argues for an ontology of software that deals with its mutability. This mutability arises from the agential relations indexed by code of the social web that software weaves. Mackenzie, as one of the authors of the Software Studies lexicon, contributes to software studies by arguing that we should render software visible and notice the agency it provides, generates and distributes:

At stake here is an account of software as a highly involuted, historically media-specific distribution of agency. This account diverges from a general sociology of technology in highlighting the historical, material specificity of code as a labile, shifting nexus of relations, forms and practices. It regards software formally as a set of permutable distributions of agency between people, machines and contemporary symbolic environments carried as code. Code itself is structured as a distribution of agency. (Mackenzie, 19)

So what is next for the field of software studies? After having finished reading Software Studies it has not become quite clear what is to be done since it does not provide a unified approach or methodology. However, the lexicon is an excellent starting point for those who wish to be introduced into software studies. But what about those who wish to contribute? Even though a lexicon is provisional, scalable and offers pathways, in a printed form it still implies some kind of a finished whole. Software as a shifting nexus of relations is in a constant flux and pathways into software may disappear, change or be added. The print form is not fit to adjust to such changes because once the text has been printed there is no way to adjust it. Revising is a possible solution for this problem. Recently, the famous lexicon Keywords by Raymond Williams has been revised by several editors resulting in New Keywords: a revised vocabulary of culture and society. Original entries of the lexicon were updated and new entries were added twenty five years after the original publication.

A more fitting solution for Software Studies would be supplying a digital environment in which changes in entries can be made without losing the original entry and can be tracked. Such environments are currently known as wikis which might be an ideal work form for software studies. Like software, wikis are often seen as a shifting nexus of relations that contain provisional, scalable pathways into other topics. A wiki, or another hypertextual environment might render the different pathways into software and their connections more visible thus expanding the knowledge about software and its relations. To perceive a better understanding of software we need to create more pathways. Would software studies benefit from using software to create these pathways and write about its studies?

References

Fuller, Matthew. Behind the Blip: Essays on the Culture of Software. Brooklyn, USA: Autonomedia, 2003.
Fuller, Matthew. Software Studies: A Lexicon. Cambridge, USA: The MIT Press, 2008.
Mackenzie, Adrian. Cutting Code: Software And Sociality. New York, USA: Peter Lang Pub Inc., 2006.
Manovich, Lev. The Language of New Media. Cambridge, USA: The MIT Press, 2002.

UPDATE
Matthew Fuller replied to my critique on the somewhat stale format of the book in contrast to a wiki that a wiki tends to homogenize the authors’ voices. On top of that academic publishing in the form of a book is a good way to ‘register’ ideas within a certain set of discourses embedded in the book. During the SoftWhere 2008: Software Studies Strategy Round-Table Doug Sery from MIT Press announced that they were interested in publishing a series and MIT Press officially approved the Software Studies book series in July 2008.

While I was in San Diego in May at the Software Studies Institute the first bits of a digital collaborative working ground were being built. The goal is to make a Software Studies portal where current research is on display, to find researchers and to bring researchers together. This portal is still “under construction” but anything tagged with ‘software_studies’ will very likely be picked up in the near future.

Review: Cutting Code. Software And Sociality – Adrian Mackenzie

Cutting Code: Software And Sociality (Digital Formations)Peter Lang, New York, NY, USA 2006
216 pp. Paperback, $31.95 USD
ISBN 0-8204-7823-7
Buy at Amazon

Cutting Code addresses the subject of software that has previously been marginalized due to its invisibility. Software is a very mutable object that is entangled in a web of relations. Mackenzie thus sees software as a social object and process that is intrinsically linked to code as a material and practice. Software has previously been studied from a formalist approach by Manovich. The problem with such an approach is that software is abstracted from practices and contexts surrounding coding and reduced to “relations and operations (such as sorting, comparing, copying, removing) on items of data.”1 These relations and operations are seen as quite stable forms and are often directly transfered from the field of computer science. Instead of abstracting and formalizing software Mackenzie argues for an ontology of software that deals with the mutability of software and its web of relations. Code is at the core of this web that software weaves:

[...] it treats the sociality of the software, the relations that obtain in its neighborhood, as mutable, involuted agential relations indexed by code.2

Mackenzie contributes to the emerging field of Software Studies with an interesting take on code and software. We should render software visible and notice the agency it provides, generates and distributes:

At stake here is an account of software as a highly involuted, historically media-specific distribution of agency. This account diverges from a general sociology of technology in highlighting the historical, material specificity of code as a labile, shifting nexus of relations, forms and practices. It regards software formally as a set of permutable distributions of agency between people, machines and contemporary symbolic environments carried as code. Code itself is structured as a distribution of agency.3

  1. Mackenzie, Adrian. Cutting Code: Software And Sociality. Peter Lang Pub Inc, 2006. p. 4 []
  2. Mackenzie, Adrian. Cutting Code: Software And Sociality. Peter Lang Pub Inc, 2006. p. 19 []
  3. Mackenzie, Adrian. Cutting Code: Software And Sociality. Peter Lang Pub Inc, 2006. p. 19 []

The networked book: GAM3R 7H30RY & Code Version 2.0

Lessig Code 2Writing a book online and facilitating a discussion around it seems to be very popular these days. McKenzie Wark is working on GAM3R 7H30RY which will be published by Harvard University Press in April 2007, and it will contain contributions from readers of his site. Readers are discussing and participating in the writing process and the networked book is born. The Institute for the Future of the Book is concerned with issues around “the book’s reinvention in a networked environment.”1

Read More…

  1. IFB []