To Code or Not To Code?

Tuesday, February 22, 2011
12:30-1:45 pm
Graduate Conference Room 0005B
Strozier Library

To Code or Not To Code?

For the next session of the Digital Scholars reading and discussion group, we will take up two related questions about programming: as something to learn and as something to study.

First, should humanities students learn to program? A handful of prominent scholars and humanities technology staffers think so. Some argue that you cannot be a digital humanist without knowing how to code.  In this session, we will consider the current debate about the necessity of coding, programming, or building—a debate that recently flared at (and after) the 2011 MLA convention.

Second, how might humanists study code? What does “critical code studies” or the cultural studies of code look like? How do its methodologies and assumptions relate to our more familiar engagement with the semantic and material codes of language and texts?

  • Noah Wardrip-Fruin, “Introduction.” Expressive Processing: Digital Fictions, Computer Games, and Software Studies. Cambridge, MA: MIT Press, 2009. 1-21. [on Blackboard]
  • Critical Code Studies blog. Browse, especially reflections on MLA 2011 panel “Close Reading the Digital.”

2 thoughts on “To Code or Not To Code?

  1. This is a topic I’ve been thinking on for some time now. I am coming to the belief that yes, to call oneself a scholar/technologist in digital humanities, one should be competent in code. I say this because as Tom Scheinfeldt points out in this recent post, “Most of the most successful digital humanities projects are those done by scholar/technologists not those imagined by scholars and implemented by technologists. Likewise, the most successful digital humanists are scholars who know the technology, often those who are self-taught, not ones who seek a client-vendor relationship with technologists.”

    Digital Humanities = DIY and DIY is code.

  2. Pingback: “Black at Bryn Mawr” and Technologies of Recovery | FSU Digital Scholars

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s