It looks like you're new here. If you want to get involved, click one of these buttons!
Before we begin code critiques, we have to find the bodies of code worth investigating. Over the past ten years, we’ve looked at a wide range of code. For example,
It turns out one of the most productive intellectual contributions you can make to critical code studies is to identify a body of code worth considering. That activity, of identifying an object worth analyzing, launches the investigation and incites exploration.
Why is this activity so important? Primarily because to call out a body of code as worthy of exploration is to say this artifact has significance. While CCS contends that all code has significance beyond what it does, for a scholar to turn a spotlight on a piece of code is like choosing a book for a book club or perhaps more significantly to present a work on on display in a museum. In the same way the Code Critiques do, that act of curation gives the rest of us a chance to walk around and consider various aspects -- and we can help find snippets worth exploring further.
Let us begin this thread with a call for codebases -- a call for you to identify programs or entire pieces of software worth exploring. These could be in repositories or merely a single file -- as long as the code is publically available for collective exploration.
So we put out the call to you? What codebases do you want to identify?