<?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>2026 General — CCS Working Group</title>
      <link>https://wg.criticalcodestudies.com/index.php?p=/</link>
      <pubDate>Sun, 12 Apr 2026 07:15:38 +0000</pubDate>
          <description>2026 General — CCS Working Group</description>
    <language>en</language>
    <atom:link href="https://wg.criticalcodestudies.com/index.php?p=/categories/2026-general/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Introduce Yourself (2026)</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/185/introduce-yourself-2026</link>
        <pubDate>Sat, 10 Jan 2026 18:49:15 +0000</pubDate>
        <category>2026 General</category>
        <dc:creator>markcmarino</dc:creator>
        <guid isPermaLink="false">185@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Welcome!</p>

<p>Please reply here with a brief introduction of yourself and your interests in Critical Code Studies. Some of us are first-timers, others have been attending since 2010. In addition to your general profile, consider briefly sharing new publications or projects, new ideas in progress, or simply new questions.  Feel free to also give us a preview of a code critique you plan to post.</p>

<p>The "Introduce Yourself" thread is a great tradition of this Working Group. For a sense of everyone who has come before, browse the self-introductions from <a rel="nofollow" href="https://wg.criticalcodestudies.com/index.php?p=/discussion/143/introduce-yourself-2024/">2024</a>, <a rel="nofollow" href="https://wg.criticalcodestudies.com/index.php?p=/discussion/102/introduce-yourself-2022/">2022</a>, <a rel="nofollow" href="https://wg.criticalcodestudies.com/index.php?p=/discussion/50/introduce-yourself-2020/">2020</a>, and <a rel="nofollow" href="https://wg.criticalcodestudies.com/index.php?p=/discussion/10/introduce-yourself-2018/">2018</a>....</p>
]]>
        </description>
    </item>
    <item>
        <title>2026 Bulletin Board and Call Sheet</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/194/2026-bulletin-board-and-call-sheet</link>
        <pubDate>Sun, 11 Jan 2026 21:56:12 +0000</pubDate>
        <category>2026 General</category>
        <dc:creator>markcmarino</dc:creator>
        <guid isPermaLink="false">194@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Know of any upcoming opportunities that might interest your fellow working group members? Please post / link to them in comments here.</p>

<p>calls for papers / CFPs<br />
job calls<br />
grant programs<br />
projects<br />
events<br />
...or anything else that might interest members of the Critical Code Studies Working Group!</p>
]]>
        </description>
    </item>
    <item>
        <title>Cliff Shaw's Early AI Archive at the Smithsonian JUST Accessed (like two hours ago!)</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/216/cliff-shaws-early-ai-archive-at-the-smithsonian-just-accessed-like-two-hours-ago</link>
        <pubDate>Thu, 29 Jan 2026 19:05:00 +0000</pubDate>
        <category>2026 General</category>
        <dc:creator>jshrager</dc:creator>
        <guid isPermaLink="false">216@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Coincidentally (that is, having had no intentional scheduling coincidence with CCS), I (more precisely, my collaborator in DC) did our first exploration into the the Smithsonian archives of Cliff Shaw this morning. Shaw was the lead engineer on the world's first AIs: Shaw, Newell, and Simon's chess program, the Logic Theorist (which I've discussed in a separate thread), and GPS, the General Problem Solver -- the world's first general AI! These were all written in the 1950s and early 1960s, mostly by Shaw, mostly in IPL-V, a precursor of Lisp that was the world's first AI programming language (again, I've discussed this in the other thread).</p>

<p>I don't have permission yet to share everything we found publicly, but I'm pretty sure that no one's going to sue me for sharing a taste among colleagues:</p>

<p><a href="https://drive.google.com/drive/folders/12RW7YzunHcuAB4PvQPCOtVQdMCGvoqY8" rel="nofollow">https://drive.google.com/drive/folders/12RW7YzunHcuAB4PvQPCOtVQdMCGvoqY8</a></p>

<p>Cheers,<br />
'Jeff</p>
]]>
        </description>
    </item>
    <item>
        <title>First time in a CCSWG? Start here (2026)</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/193/first-time-in-a-ccswg-start-here-2026</link>
        <pubDate>Sun, 11 Jan 2026 21:49:59 +0000</pubDate>
        <category>2026 General</category>
        <dc:creator>markcmarino</dc:creator>
        <guid isPermaLink="false">193@/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>

<p><a rel="nofollow" href="https://electronicbookreview.com/essay/critical-code-studies/" title="The Original Manifesto">The Original Manifesto</a><br />
<a rel="nofollow" href="https://criticalcodestudies.com/intro.pdf" title="The Introduction to_ Critical Code Studies_.">The Introduction to_ Critical Code Studies_.<br />
</a>This analysis of <a rel="nofollow" href="http://www.digitalhumanities.org/dhq/vol/7/1/000157/000157.html" title="the Transborder Immigrant Tool">the Transborder Immigrant Tool</a><br />
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 publicly. The previous ones were closed to participants only. However, you can read previous discussions from the first Working Group in electric book review, where this year's weekly discussion was held.</p>

<p><a rel="nofollow" href="https://wg.criticalcodestudies.com/index.php?p=/categories/2024-ccswg" title="2024 Critical Code Studies Working Group">2024 Critical Code Studies Working Group<br />
</a><a rel="nofollow" href="https://wg.criticalcodestudies.com/index.php?p=/categories/2022-ccswg" title="2022 Critical Code Studies Working Group">2022 Critical Code Studies Working Group</a><br />
<a rel="nofollow" href="https://wg.criticalcodestudies.com/index.php?p=/categories/2020-ccswg" title="2020 Critical Code Studies Working Group">2020 Critical Code Studies Working Group</a><br />
<a rel="nofollow" href="https://wg.criticalcodestudies.com/index.php?p=/categories/2018-ccswg/" title="2018 Critical Code Studies Working Group">2018 Critical Code Studies Working Group<br />
</a></p>

<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>CFP: Retro AI  (July 31, Aug 1, 2026, USC)</title>
        <link>https://wg.criticalcodestudies.com/index.php?p=/discussion/192/cfp-retro-ai-july-31-aug-1-2026-usc</link>
        <pubDate>Sun, 11 Jan 2026 21:30:09 +0000</pubDate>
        <category>2026 General</category>
        <dc:creator>markcmarino</dc:creator>
        <guid isPermaLink="false">192@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>We invite you to submit a proposal to the Retro AI symposium at USC this summer: July 31 and Aug 1, 2026.</p>

<p>Here's the full call.</p>

<h1>Retro AI</h1>

<h2>Archeologies of Artificial Intelligence</h2>

<h2>In-Person at USC: July 31, August 1</h2>

<h2>Extended Deadline: Feb 1</h2>

<p>The field of artificial intelligence (AI) has long been obsessively focussed on the next big breakthrough which would solve its defining problems. While interventions like critical AI studies are at least starting to ask the right questions of this field, their fixation on the latest innovation often misses the critical histories and genealogies of AI's past. You are invited to a two-day symposium on Retro AI at the University of Southern California (USC) to critically consider these questions and their implications for today.</p>

<p>Sponsored by the Institute on Ethics &amp; Trust in Computing, The Humanities and Critical Code Studies Lab, and the Electronic Literature Organization</p>

<p>Approaches include: Critical code studies, media archaeology, software studies, platform studies, critical AI studies, and science and technology studies</p>

<h2>Subjects:</h2>

<p>ELIZA and other early chatbots<br />
Early knowledge representation systems<br />
Ethics and early AI<br />
Rule-based natural-language dialogue systems<br />
Propositional and predicate-logic reasoning programs<br />
Pattern-matching conversational systems (e.g., ELIZA-style architectures)<br />
Early expert systems for domain-specific problem solving<br />
Early AI programming languages<br />
Classical planning and search systems<br />
Machine translation prototypes from the mid-20th century<br />
Early neural-network research and perceptron-based models<br />
Interactive fiction engines as precursors to conversational AI<br />
Algorithmic creativity systems (text, music, and art generators)<br />
Human–computer interaction studies related to early AI behavior</p>

<h2>Call for Art:</h2>

<p>We also seek digital artworks for an online exhibition on the theme of Retro AI.</p>

<h2>How to Submit</h2>

<p>For written papers, please include a 250-300 word abstract and a short bio. Artwork submissions should include a short description and a link to the work, video documentation, or other supporting materials.</p>

<p>Submit through this form.</p>

<p>Contact Mark Marino with questions. markcmarino @ gmail.com</p>
]]>
        </description>
    </item>
   <language>en</language>
   </channel>
</rss>
