Submit Comment

show all (0)
There are no comments. Click the text to your left to make a new comment.
1 0

//Week 4 Summary
//Heres what CCSWG members should know about Weeks 4 and 5
#includeiostream.h

2 0

int future (week5, thread editor)
{
coutIn Week 5, Stephen Ramsay will be presenting his live commentary on live coding.  Weve debated code as performative, now we examine coding as performance.;

3 0

//Were still looking for one more thread editor. Please contact Mark Marino if interested.
cin editor;
return 0;
}

4 0

int main (week4)
{
coutWendy Chuns exciting chapter from her forthcoming book provided members with numerous topics for discussion this week. Starting with Derrida-style logocentrism and Chuns idea of code as fetish, CCSWG charted new territory with intriguing conversations that ran parallel courses all week. Chun and the working group members exchanged thoughts about various aspects of the 82-page chapter, ranging from an exploration of the gendered and militaristic beginnings of the modern computer industry to a new look at the quintessential ;
coutHello, World!;
cout code snippet. As with previous weeks, this thread will remain open for further discussion. Members are encouraged to continue engaging in conversations of weeks past.;
cin morediscussion;
return 0;
}

5 0

int statistics (CCSWGtotals)
{
codecritiques = 27;   //Members should be aware of the fast-approaching end of the discussion, and be sure to post code snippets in the critiques section that theyd like for the group to examine.  And if you havent introduced yourself, times wasting.

6 0

week4replies = 41;
week3replies = 64;   //The code critique from week 3 included 85 footnotes, although that wont be used in this calculation since were looking at discussion replies
week2replies = 51;
week1replies = 73;
totalreplies = 229;
coutIn only four weeks, the CCSWG has amassed an impressive totalreplies replies!;

7 0

totalmembers = 109;   //Members should also be cognisant of the fact that the CCSWG discussions will be posted on electronic book review, so they should be sure to join in the conversations in order to be included in the publication.
return 0;
}

8 0

int Future_of_CCSWG
{
coutWeve started a new thread for discussing future venues for CCS, including:;
future.variable1 = CCS_conference (date) //a one-day CCS conference at USC;
future.variable2 = ACM (hypertext) //an opportunity to present at ACM HT10;
future.variable3 = collecting essays in an edited publication;
future.variable4 = creating a code critiques section on the CCS blog;
return 0;
}

9 0

int ACM (hypertext)
{
coutWe have an opportunity to put together a workshop for ACM Hypertext 2010 (Toronto, 13-16 June). Interested parties should contact Mark Marino.;
return 0;
}

10 0

int CCS_conference (date)
{
possibledate1 = 7.23.2010;
possibledate2 = 8.6.2010;
coutAlthough our online discussion will come to an end in a few short weeks, the Critical Code Studies community is gearing up for a conference to take place this summer. More information to follow.;

11 0

return 0;
}

thesis writing service