[Cross-posted from the Re:Thinking blog at CLIR, the Council on Library and Information Resources, where I'm honored to be serving as Distinguished Presidential Fellow. Check out all the great content at CLIR! (and see the Scholars' Lab's announcement, too).]
This is a belated follow-up post to last autumn’s “How We Learned to Start/Stop Speaking in Code,” in which I described the motivation for us, at the UVa Library Scholars’ Lab, to host a two-day summit on the scholarly and social implications of tacit knowledge exchange in digital humanities software development. But the timing is good!—because today, the Scholars’ Lab is releasing a web-based toolkit that any group can use to host a similar gathering. We also want to make the community aware of some venues in which distributed discussions of the social and theoretical side of DH software development can continue online: using the #codespeak hashtag on Twitter, and at the #speakingincode channel on IRC.
“Speaking in Code” was generously supported by the National Endowment for the Humanities and the University of Virginia Library, and it brought together 32 competitively-selected, advanced software developers with expertise in humanities applications of computing, for an extended conversation about the culture and craft of codework in DH. The group that met in Charlottesville last November paid special attention to knowledge and theoretical understandings that are gained in practice yet typically go unspoken—embodied in systems, techniques, interfaces, and tools, rather than in words. This is a brand of humanities work that can seem arcane and inaccessible to scholars, or worse: because its methods and outcomes are not always broadly legible, it is easily assumed to be devoid of critical thought and contextual (historical, theoretical, or literary) understanding. To quote my last post:
Communications gaps are deep and broad, even among humanities-trained software developers and the scholars with whom they collaborate. Much (not all) knowledge advances in software development through hands-on, journeyman learning experiences and the iterative, often-collaborative development of built objects and systems. Much (not all) knowledge advances in humanities scholarship through fixed and fluid kinds of academic discourse: referential, prosy, often agonistic. Read the rest of this entry »