Feminist in a Software Lab

Feminist in a Software Lab: Difference + Design begins with a practical problem: does feminism merely use software to communicate critical content, or can it transform software’s form? Tara McPherson draws on more than a decade with USC’s Vectors Lab, its online journal Vectors, and the multimedia publishing platform Scalar. Digital humanities becomes an institution made of design, programming, editing, funding, and maintenance—not a neutral toolkit.

The first part revises the field’s origin story. Rather than begin with canonical text computation, McPherson juxtaposes 1960s art-engineering collaboration, urban computing, UNIX modularity, and civil-rights struggle. She does not claim that a code structure caused racial segregation; she asks why the same era valued separable, encapsulated, noninterfering modules across domains. In academic projects, race and gender can then become modules added later rather than relations constituting the system.

Designing for difference is therefore not adding diverse figures to a finished interface. It means considering from the data model, classification, navigation, and user path which knowledge relations can exist. Conventional databases favor stable objects and hierarchies, whereas memory, trauma, migration, and identity may be multitemporal, contradictory, and relational. Vectors projects made form part of argument so that image, sound, space, and interaction produced knowledge rather than illustrating prose.

The second part works as a lab ethnography, preserving emails, sketches, meeting notes, designers’ statements, and failed plans that reveal the collaboration usually erased behind digital work. Authors, designers, programmers, and editors translate across expertise for months, preventing authority from residing in one byline. Feminist making concerns not only what a product says, but who can speak, who performs emotional and maintenance labor, how conflict is resolved, and how institutions evaluate unconventional scholarship.

The transition from highly customized Vectors projects to the more sustainable open-source Scalar platform exposes a real tension between difference and standardization. Unique design can enable radical forms but resist maintenance and reuse; a general platform can survive while constraining expression. Early projects lost to plugins, servers, and browser change demonstrate that preservation, documentation, and long-term care are not administrative tasks after technology. They are part of design ethics.

The book also invites criticism. Analogies between software modularity and social classification sometimes outrun specific evidence about archives, labor, or users. A well-resourced US university lab is difficult to reproduce in underfunded or non-Anglophone settings. The account does not replace analyses of supply chains, platform labor, disability access, or surveillance. Feminist software must still answer to the people who use and maintain it.

For FemRes, the central lesson is that critique and making cannot be delegated to groups unable to understand one another. Radical content does not make a project feminist if classification is rigid, interfaces exclude, credit erases collaboration, or maintenance costs fall on people without power. The book leaves concrete questions: when does difference enter design, are failures documented, can relationships alter data structures, and who cares for a work after its grant ends?