Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Participants: Hannah Ackermans * Julianne Aguilar * Bo An * Katie Anagnostou * Joanne Armitage * Lucas Bang * Alanna Bartolini * David M. Berry * Lillian-Yvonne Bertram * Elisa Beshero-Bondar * Briana Bettin * Sayan Bhattacharyya * Avery Blankenship * Gregory Bringman * Tatiana Bryant * Zara Burton * Evan Buswell * Ashleigh Cassemere-Stanfield * Angela Chang * Prashant Chauhan * Lia Coleman * Chris Coleman * Bill Condee * Nicole Cote * Christina Cuneo * Pierre Depaz * Ranjodh Dhaliwal * Samuel DiBella * Quinn Dombrowski * Kevin Driscoll * Brandee Easter * Jeffrey Edgington * Zoelle Egner * Tristan Espinoza * Teodora Sinziana Fartan * Meredith finkelstein * luke fischbeck * Cyril Focht * Cassidy Fuller * Erika Fülöp * gripp gillson * Alice Goldfarb * Jan Grant * Sarah Groff Hennigh-Palermo * Saksham Gupta * MARIO GUZMAN * Gottfried Haider * Rob Hammond * Nabil Hassein * Diogo Henriques * Gui Heurich * Kate Hollenbach * Stefka Hristova * Bryce Jackson * Dennis Jerz * Joey Jones * Amy Kintner * Corinna Kirsch * Harris Kornstein * Julia Kott * Rishav Kundu * Karios Kurav * Cherrie Kwok * Sarah Laiola * RYAN LEACH * Rachael Lee * Kristen Lillvis * Elizabeth Losh * Jiaqi LU * Megan Ma * Emily Maemura * ASHIK MAHMUD * Felipe Mammoli * Mariana Marangoni * Terhi Marttila * Daniel McCafferty * Christopher McGuinness * Alex McLean * Chandler McWilliams * Todd Millstein * Achala Mishra * Mami Mizushina * Nick Montfort * Molly Morin * Gutierrez Nicholaus * Matt Nish-Lapidus * Michael Nixon * Mace Ojala * Steven Oscherwitz * Delfina Pandiani * Stefano Penge * Megan Perram * Gesina Phillips * Tanner Poling * Julia Polyck-O’Neill * Ben Potter * Amit Ray * Katrina Rbeiz * Jake Reber * Thorsten Ries * Giulia Carla Rossi * Barry Rountree * Warren Sack * samara sallam * Mark Sample * Perla Sasson-Henry * zehra sayed * Carly Schnitzler * Ushnish Sengupta * Lyle Skains * Andrew Smith * Rory Solomon * S. Hayley Steele * Samara Steele * Nikki Stevens * Daniel Temkin * Anna Tito * Lesia Tkacz * Fereshteh Toosi * Nicholas Travaglini * Paige Treebridge * Paige Treebridge * Álvaro Triana Sánchez * Lee Tusman * Natalia + Meow Tyshkevich + Kilo * Annette Vee * Malena Velarde * Dan Verständig * Yohanna Waliya * Samantha Walkow * Josephine Walwema * Shu Wan * Biyi Wen * Zach Whalen * Mark Wolff * Christine Woody * kathy wu * Katherine Yang * Shuyi Yin * Nikoleta Zampaki * Hongwei Zhou
Coordinated by Mark Marino (USC), Jeremy Douglass (UCSB), Sarah Ciston (USC), and Zach Mann (USC). Sponsored by the Humanities and Critical Code Studies Lab (USC), and the Digital Arts and Humanities Commons (UCSB).

Welcome to CCSWG22

edited January 15 in 2022 General

Zachary Mann:

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.

Two thousand and twenty-two marks the 12 year anniversary of the first Working Group, and our 7th biennial meeting,
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 & Humanities Commons at UC Santa Barbara.

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.

Jeremy Douglass:

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

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

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

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

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

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

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.

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.

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

  1. 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.
  2. Join each weekly plenary discussion
  3. Start new discussion threads related to the main topic of the week, or to Critical Code Studies in general.
  4. Post new entries to the shared Bibliography of Critical Code Studies
  5. 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.

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

Sarah Ciston:

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.

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&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.

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.

Mark Marino:

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.

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.

Sign In or Register to comment.