DH Strangelove or: How I Learned to Stop Worrying and Love the Digital Humanities

DH Strangelove or: How I Learned to Stop Worrying and Love the Digital Humanities

Disclaimer: I’m not trying to equate the Digital Humanities with Weapons of Mass Destruction. Just in case I needed to clarify my Kubrick reference…

The start of a new academic (and fellowship) year prompts some introspection to establish goals and objectives for the year to come. Since I was new to the world of digital humanities (DH) when I began my tenure as a Digital Fellow last year, I spent a fair amount of time figuring out what DH is and how it fit into my life as a scholar. Now that I have a better sense of the field, theory, tools, and practices of DH, it seems like an opportune moment to briefly meditate on my understandings of DH from the perspective of a “non-digital humanist,” both to hone my goals for the current fellowship year, as well as for the sake of other non-digital humanists who find themselves curious about the digital humanities.

My use of the term “non-digital humanist” requires some explanation, lest I imply that I don’t use, do, or believe in the digital humanities. By non-digital humanist, I mean that at present, and unlike many (most?) of my Digital Fellow colleagues, my scholarship does not pertain to, nor does it incorporate, DH methods or theory (without getting into the debates about what constitutes either). Even though there are questions I could be asking in my research that would fit nicely with DH methods, I’ve made the conscious decision not to pursue that path. But by the same logic, there are questions I could be asking in my research that would fit nicely with ethnographic or quantitative social science methods, and which would doubtlessly provide meaningful results, but at the present, I’m neither an ethnographer nor a quantitative social scientist, putting aside completely the debates about the boundaries between the social sciences and humanities. And yet, as a social scientist I have those tools available to me, just as I have the tools of DH available to me for when the inspiration strikes to set off on a project for which those tools, methods, questions, etc. are more relevant. And this understanding is at the heart of what I’m trying to get at.

Debates about who “counts” as a digital humanist are probably as old as institutional funding for DH scholarship. This post isn’t an intervention into that debate (http://dhdebates.gc.cuny.edu/debates/), although be sure to check out my note about it at the bottom of this post. Depending on who’s asked, there’s a strong case that I fit the label of “digital humanist” since I’ve been involved in projects that utilize digital technologies in the making, coding, and broad audience sharing of humanities and humanistic social science scholarship. But that’s not really my jam. And I assume that for many other scholars who keep hearing chatter about (and countless CFPs, jobs, and funding opportunities for) The Digital Humanities, but aren’t really familiar with it, “convinced” by it, or actively engaging it, the label non-digital humanist is probably appropriate. I fit into this camp of non-digital humanists, and this post is some initial thoughts about the digital humanities for, and by, a non-digital humanist.

One of the easiest ways to jump in to the digital humanities, which in some ways is also the hardest, is by tapping into the mindset behind much of the digital humanities community. I’m referring specifically to ideas about open access, collaboration, sharing, making, playing, and failure. As we all know, academia, in the form of the “edu-factory”, has a tendency to instill a culture of isolation, perfectionism, and counter-constructive criticism. Many scholars critical of the siloing of knowledge within the academy already engage in practices to combat these tendencies, such as interdisciplinary collaboration, mentoring, colloquia, trade unionism, and horizontalism. But let’s face it, the doctorate-tenure-promotion pipeline (labyrinth?) works against this type of scholarship at every turn.

Taking seriously the push from within DH communities to promote those DH mindset ideas mentioned above is certainly another way to reinforce the push back against the ivory tower. Many non-digital humanists probably already engage in practices and are invested in some of the ideals promoted from within this “DH mindset.” So it’s probably worthwhile for non-digital humanists with an interest in these sorts of ideals to further familiarize themselves with some of the low-risk DH practices such as allowing open access to scholarship through the use of easily redistributable digital mediums, or “tinkering” with data or new tools without fear of failure. Keeping an eye on emerging practices that fit within this DH mindset and a willingness to try some of them out has been one of the most accessible and digestible ways to get into DH for myself and those with whom I’ve worked over the past year.

One of the challenges for me in embracing the whole DH mindset has been collaboration. At times, and depending on the task, I am great at collaborating, from planning to communicating to execution to evaluation. But in many situations, I’m absolutely horrible at it, especially when I think it’s easier and quicker to just do it myself. In a previous life as an engineer, I had to delegate work and manage personnel, then review and sign off on the job. As a graduate student, almost all of my writing and research is either done independently or in a small research group where everyone has their specific jobs and areas of specialization. It has been far from a smooth transition back from isolated scholar to team member—or at the very least, Digital Fellow who’s not afraid to ask others to (meaningfully) collaborate on a project. So this year, one of the things I want to work on as a Digital Fellow is figuring out ways to effectively work with others on projects where we communicate regularly (instead of emails once every few weeks) and where tasks get delegated or divvied in such a way that we have a sense that we’re building it together and can share ownership over the process. In a way, this is simply project management. But in an environment where we are all on an academic’s schedule with writing, researching, or coursework as our priority, project management is a whole different beast—a digital humanities beast.

When I initially began drafting this post, I set out to provide a short review of several different aspects of the digital humanities from a non-digital humanist perspective, with the mindset or culture of DH being just the beginning. There will be more to follow, including, I suspect, the ways and means of DH tools and DH praxis. Hopefully these posts help demystify the digital humanities and help others have the same realization that I’ve had over the past year, that there’s a tremendous benefit to any scholar (whether within or without the academy) in engaging with the digital humanities. And ultimately, regardless of our research focus, methods, or skills (e.g., coding), many of us “non-digital humanists” are, actually, already digital humanists in that we align ourselves in small—or maybe even large—ways with what DH boosters have been cheering for all along, even if we don’t think of what we do as the digital humanities.

This brings me to my final point: injecting myself into the debate about the digital humanist label, even though I lied in the third paragraph above and said I wasn’t trying to intervene. There are certainly arguments for why maintaining labels and establishing boundaries around the digital humanities is important, but I’m pretty sure most of those involve institutional structures, funding, hiring, and promotion. These are not trivial matters that are simply dismissible as bureaucratic cruft. They *are* about policing disciplinary structures—the multiple meanings of the term academic *discipline* are not coincidental. But for polemical and pedagogical purposes, encouraging non-digital humanists to see themselves as already engaged in the digital humanities is an important maneuver. It is like telling someone to keep an open mind about their scholarship; to take risks; to play. And isn’t that what we all keep saying the digital humanities is supposed to be about?

Keith Miyake is a graduate of the Earth and Environmental Sciences Program at the CUNY Graduate Center. His work crosses the fields of political economic geography, environmental justice and environmental governance, critical race and ethnic studies, American studies, and Asian American studies. His dissertation examined the institutionalization of environmental and racial knowledges within the contemporary capitalist state.
Need help with the Commons? Visit our
help page
Send us a message
Skip to toolbar