Bethany Nowviskie

a kit for hosting Speaking in Code

Tags: , ,

[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 »

asking for it

Tags: , , ,

A report published this week by OCLC Research asks the burning question of no one, no where: “Does every research library need a digital humanities center?” The answer, of course, is of course not.

Of course, I’m being rude. The click-bait question, as posed, had a foregone conclusion — but there’s much to recommend in the report, even if it fails to define a “DH center” in any clear way, makes an unwarranted assumption that “DH academics” and librarians exist in mutually-exclusive categories, and bases too much of its understanding of faculty and researcher perceptions on the inadequate sample of some conference-going and a couple of focus groups (however carefully convened and accurately reported).

The chief value of the report may lie in its stated and implied purposes: providing library directors with a set of options to consider (stated) and an easy citation — a bit of OCLC back-up — (implied) for the local arguments they must formulate in the event their provosts or presidents catch Library-based DH Center-itis and seem completely unwilling to entertain a model customized to the needs of the institution. Wait a minute. That will never happen.

Okay, the chief value of the report is in its clear reinforcement of the notion that a one-size-fits-all approach to digital scholarship support never fits all. Read the rest of this entry »

how we learned to start/stop “speaking in code”

Tags: , ,

[UPDATE: #codespeak is over and was a smashing success. See a post on outcomes, including a kit for hosting similar gatherings, here. This entry is 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!]

Here’s a consummation devoutly to be wished: digital humanities research and practice becomes its best self, and finds scholars and technology staff engaging as peers in mutually intelligible conversation. It sounds like a modest hope, until you reflect on how far we are from achieving that vision.

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. A real division exists in style and practice, even when the subjects and objects of humanities inquiry are the same. What might bridge a gap like that? And can we move past an historical moment in the academy, in which the onus is almost entirely placed on archivally and theoretically trained humanities scholars to become tech-savvy digital humanists—to build a concomitant sense of momentum, responsibility, and opportunity in our community of DH software engineers? Can we build greater community itself, just by making a space in which such problems are addressed? Read the rest of this entry »

Creative Commons License
Work at http://nowviskie.org by Bethany Nowviskie is licensed under a Creative Commons Attribution 3.0 Unported License.
This site runs a heavily modified version of Bryan Helmig's Magatheme. I designed the falling letters circa 1998, and never get tired of them.