week4wrapup.cpp

Ξ March 5th, 2010 | → 0 Comments | ∇ test |

//Week 4 Summary
//Here’s what CCSWG members should know about Weeks 4 and 5
#include<iostream.h>

int future (week5, thread editor)
{
cout<<”In Week 5, Stephen Ramsay will be presenting his live commentary on live coding.  We’ve debated code as performative, now we examine coding as performance.”;

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

int main (week4)
{
cout<<”Wendy Chun’s exciting chapter from her forthcoming book provided members with numerous topics for discussion this week. Starting with Derrida-style logocentrism and Chun’s 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 “;
cout<<”Hello, 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;
}

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 they’d like for the group to examine.  And if you haven’t introduced yourself, time’s wasting.

week4replies = 41;
week3replies = 64;   //The code critique from week 3 included 85 footnotes, although that won’t be used in this calculation since we’re looking at discussion replies
week2replies = 51;
week1replies = 73;
totalreplies = 229;
cout<<”In only four weeks, the CCSWG has amassed an impressive ” << totalreplies <<” replies!”;

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;
}

int Future_of_CCSWG
{
cout<<”We’ve 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;
}

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

int CCS_conference (date)
{
possibledate1 = 7.23.2010;
possibledate2 = 8.6.2010;
cout<<”Although 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.”;

return 0;
}

 

CCSWG: Week 3 in Review

Ξ March 4th, 2010 | → 0 Comments | ∇ test |

 

Week 1: Critical Code Studies Working Group

Ξ February 6th, 2010 | → 0 Comments | ∇ test, CCS, conferences, fundamentals, working group |

 

On Efficiency

Ξ September 18th, 2009 | → 0 Comments | ∇ test, fundamentals |

 

Open Source Embroidery: Craft + Code

Ξ August 4th, 2008 | → 0 Comments | ∇ test, CCS, events, reviews, galleries |

 

Launching Critical Code Studies, the blog

Ξ December 20th, 2007 | → 0 Comments | ∇ test |

 

Critical Code Studies vs. Software Studies

Ξ December 7th, 2007 | → 1 Comments | ∇ test, CCS, codework |

 


About

    Critical Code Studies

    Critical Code Studies is a forum for resources, discussion, and demonstrations of the interpretation of computer code.

Related Blogs

CCS Selected Readings

Del.icio.us CCS

CCS Books

CCS Bookmarks