<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
      <title>2022 General — CCS Working Group</title>
      <link>https://wg.criticalcodestudies.com/index.php?p=/</link>
      <pubDate>Sat, 11 Apr 2026 14:07:54 +0000</pubDate>
          <description>2022 General — CCS Working Group</description>
    <language>en</language>
    <atom:link href="https://wg.criticalcodestudies.com/index.php?p=/categories/2022-general/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Introduce Yourself 2022</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/102/introduce-yourself-2022</link>
        <pubDate>Fri, 14 Jan 2022 22:02:16 +0000</pubDate>
        <category>2022 General</category>
        <dc:creator>markcmarino</dc:creator>
        <guid isPermaLink="false">102@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Welcome, everyone. Please, introduce yourself here. Be sure to give us a sense of what brings to the Working Group.</p>
]]>
        </description>
    </item>
    <item>
        <title>A Critical Code Studies Syllabus</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/128/a-critical-code-studies-syllabus</link>
        <pubDate>Sun, 06 Feb 2022 17:23:56 +0000</pubDate>
        <category>2022 General</category>
        <dc:creator>markcmarino</dc:creator>
        <guid isPermaLink="false">128@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>During our LIVE session on Friday, <a rel="nofollow" href="https://wg.criticalcodestudies.com/index.php?p=/profile/SarahCiston">@SarahCiston</a> brought up the question of what a Critical Code Studies syllabus would look like.  This year we are featuring several threads for books that would fit perfectly in such a course.  What are books and assignments or even a structure for such a course given student cohorts of different makeups (majors, level of education, experience with programming).  Also, if you've taught such a course, please, share anything you'd like here.  We can also move resources from this list onto a page at criticalcodestudies.com or haccslab.com.</p>

<p><strong>Initial texts:</strong><br />
* <em>Critical Code Studies</em>, Marino<br />
* <em>Aesthetic Programming</em>, Soon and Cox<br />
* <em>Exploratory Programming</em>, Montfort<br />
* <em>Poetic Operations</em>, cárdenas<br />
* <em>10 PRINT CHR$(205.5+RND(1)); : GOTO 10</em>, Montfort et al.</p>

<p><strong>Looking for:</strong><br />
* Book recommendations<br />
* Assignments<br />
* Course outlines<br />
* Any other materials that might prove useful</p>
]]>
        </description>
    </item>
    <item>
        <title>Bulletin Board: Other Announcements &amp; Opportunities</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/133/bulletin-board-other-announcements-opportunities</link>
        <pubDate>Tue, 08 Feb 2022 21:45:08 +0000</pubDate>
        <category>2022 General</category>
        <dc:creator>Zach_Mann</dc:creator>
        <guid isPermaLink="false">133@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>If there are any open calls, CFPs, or opportunities that you think your fellow working group members might be interested in, related to Critical Code Studies, please include as a comment below.</p>
]]>
        </description>
    </item>
    <item>
        <title>First time at CCSWG? New to CCS? Start here!</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/115/first-time-at-ccswg-new-to-ccs-start-here</link>
        <pubDate>Sun, 23 Jan 2022 01:25:29 +0000</pubDate>
        <category>2022 General</category>
        <dc:creator>markcmarino</dc:creator>
        <guid isPermaLink="false">115@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>If this is your first time here, I'd like to welcome you.</p>

<p>If you're brand new to CCS, you should know:<br />
Critical Code Studies is an emerging field of study exploring the extra-functional significance of computer source code.  "Extra" does not mean outside of the function, but growing out from.  Code is the means of a discussion, rather than the ends, the entry point into a discussion of technoculture. CCS is not so much an approach but a growing collection of methods and discourse.</p>

<p>To orient yourself, consider reading</p>

<ul>
<li><a rel="nofollow" href="https://electronicbookreview.com/essay/critical-code-studies/" title="The Original Manifesto">The Original Manifesto</a></li>
<li><a rel="nofollow" href="https://criticalcodestudies.com/intro.pdf" title="The Introduction to Critical Code Studies.">The Introduction to_ Critical Code Studies_.</a></li>
<li>This <a rel="nofollow" href="http://www.digitalhumanities.org/dhq/vol/7/1/000157/000157.html" title="analysis of the Transborder Immigrant Tool">analysis of the Transborder Immigrant Tool</a></li>
</ul>

<p>If you're brand new to the Working Groups, you should know:<br />
During this biennial event, we dig deep into code and coding culture with a diverse, interdisciplinary community of artists, practitioners, and scholars.  The past two CCSWGs are available publically.  The previous ones were closed to participants only.  However, you can read previous discussions from the first Working Group in <em>electric book review</em>, where this year's weekly discussion was held.</p>

<ul>
<li><a rel="nofollow" href="http://wg20.criticalcodestudies.com/" title="2020 Critical Code Studies Working Group">2020 Critical Code Studies Working Group</a></li>
<li><a rel="nofollow" href="http://wg18.criticalcodestudies.com/" title="2018 Critical Code Studies Working Group">2018 Critical Code Studies Working Group</a></li>
</ul>

<p>The challenge is to keep the focus on code, but of course, we discuss many aspects of the programs and their contexts.  However, at this event we have an opportunity to tackle the hardest part of this interpretive and creative practice. We encourage you to start a Code Critique thread or to join in on someone else's.  Remember, you don't need to know what you want out of that discussion when you post that. Our group has enough specialties, interests, and approaches to find interesting gems in it or interesting ideas to discuss related to it.</p>

<p>But let's use this thread for any questions you have about this emerging field!</p>
]]>
        </description>
    </item>
    <item>
        <title>Welcome to CCSWG22</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/103/welcome-to-ccswg22</link>
        <pubDate>Fri, 14 Jan 2022 22:12:36 +0000</pubDate>
        <category>2022 General</category>
        <dc:creator>markcmarino</dc:creator>
        <guid isPermaLink="false">103@/index.php?p=/discussions</guid>
        <description><![CDATA[<p><span data-youtube="youtube-6a6TqBErjLQ?autoplay=1"><a rel="nofollow" href="https://www.youtube.com/watch?v=6a6TqBErjLQ"><img src="https://img.youtube.com/vi/6a6TqBErjLQ/0.jpg" width="640" height="385" border="0" alt="image" /></a></span></p>

<p><strong>Zachary Mann:</strong></p>

<p>Welcome to the 2020 Critical Code Studies Working Group, our 7th biennial. I’m Zachary Mann, and on behalf of Sarah Ciston, Jeremy Douglass, and Mark Marino, I welcome you to the premiere site of critical code studies.</p>

<p>Two thousand and twenty-two marks the 12 year anniversary of the first Working Group, and our 7th biennial meeting,<br />
with more than 140 accepted participants joining us from all over the world. The theme of this year’s working group is: “interpret, explore, and investigate.” The Working Group is Sponsored the Humanities and Critical Code Studies Lab at the University of Southern California and the Digital Arts &amp; Humanities Commons at UC Santa Barbara.</p>

<p>Critical Code Studies is more than an academic subfield; it is a way of thinking more critically about the objects we use or encounter every day. It is about taking note of the parts of our digital lives that we usually don’t think twice about.</p>

<p><strong>Jeremy Douglass:</strong></p>

<p>For the next three weeks, participants will visit the working group online forum to join in weekly plenary discussions<br />
  on four topics:</p>

<ul>
<li>Week 1: Anti-racist and decolonizing code critique</li>
<li>Week 2: Code and fibre arts</li>
<li>Week 3: Creative coding and Processing</li>
<li>Week 4: Aesthetics and Poetics as Politics in Code</li>
</ul>

<p>Our plenary discussion leaders for this working group will include: Anne Sullivan &amp; Anastasia Salter; Nick Montfort; Winnie Soon &amp; Geoff Cox; micha cárdenas; Xin Xin &amp; Fabiola Hanna; and Qianqian Ye &amp; Evelyn Masso.</p>

<p>In addition to the themed weeks, we will also be highlighting three new books that are highly relevant to our community:</p>

<ul>
<li>Aesthetic Programming by Winnie Soon and Geoff Cox</li>
<li>Poetic Operations: Trans of Color Art in Digital Media by micha cárdenas</li>
<li>Exploratory Programming for the Arts and Humanities, 2nd ed. by Nick Montfort</li>
</ul>

<p>Finally, we will also celebrate the 20th anniversary of the Processing programming language family.</p>

<p>Our first full week of this working group begins on Monday January 17th -- which, in the United States, coincides on this year with the observance of Martin Luther King Jr. Day, a federal and state holiday for participants in the U.S. We may mark this occasion by reflecting on questions of race, ethnicity, labor, civil rights, and justice, which have remained central concerns in ongoing conversations on reading code critically.</p>

<p>For some participants this is your very first time joining the Working Group. For others you are returning -- and some have been attending for a decade. Each time we have re-convene this community we are amazed at its diversity of backgrounds, perspectives, methods and goals.</p>

<p>We welcome you, and we invite you to engage with the working group in several ways.</p>

<ol>
<li>First, we ask that all participants (old and new) please add a brief post to our Introduce Yourself 2022 thread and later take a moment to go back, read, and appreciate the introductions of your amazing fellow participants.</li>
<li>Join each weekly plenary discussion</li>
<li>Start new discussion threads related to the main topic of the week, or to Critical Code Studies in general.</li>
<li>Post new entries to the shared Bibliography of Critical Code Studies</li>
<li>Finally, post one or more code critiques. Code critiques involve sharing a specific code artifact and inviting discussion and analysis from a fellow participants. Your critique may be a curio, a provocation, or a full interpretive argument with request for responses. The code may be found, or of your own creation.</li>
</ol>

<p>As in every working group, threads are slated to be published in electronic book review. We look forward to your contributions.</p>

<p><strong>Sarah Ciston:</strong></p>

<p>Critical Code Studies is an evolving interdisciplinary field centered around computer code as it is embedded in culture—including the situated significance of code artifacts and the processes by which code is written, read, and circulated. The field intersects many disciplines, methods, and conversations—including computer science, cultural studies, digital humanities, media arts, media archeology, STS, software studies, platform studies, game studies, and more.</p>

<p>As the field grows, we can continue to apply the methods of critical code studies—from the political to the poetic to the material. Two milestones since the last Working Group highlight the field’s range of applications: The Anti-Racist Critical Code Studies Working Group launched to explore how critical code studies can actively engage with contemporary issues of algorithmic injustice, as software continues to surveil and subjugate bodies. We also launched our Knit&amp;Purl discord group, examining the intersections or interweavings of code and stitchcraft giving rise to our second week’s theme. Both of these special interest groups are open for new members.</p>

<p>If you would like to get more involved, consider becoming an affiliate of the HaCCS Lab or joining our new Discord.  In addition to sponsoring guest speakers and reading groups, the HaCCS Lab also coordinates panel and paper proposals and tracks for conferences.  Also, forthcoming are special issues of Digital Humanities Quarterly, featuring past participants in Working Groups.</p>

<p><strong>Mark Marino:</strong></p>

<p>Over the past two years since our last Working Group, we have seen the emergence and expansion of kindred studies, algorithmic studies, data studies, critical AI studies, et cetera, all of which lend additional tools to analysis while redoubling the need for scholars to be able to unpack the intricacies and complexities of code.  While the number of approaches to digital objects increases, the urgent need for methods of discussing code itself has only intensified as software processes continue to extend into every facet of the world. We should not abdicate our responsibility to read code when so much code is reading us.</p>

<p>We are grateful to all of you for joining us and are eager to join in discussion with you during this working group. We are especially happy to have first-timers here. We welcome you and look forward to your contributions.</p>
]]>
        </description>
    </item>
   <language>en</language>
   </channel>
</rss>
