What Is Digital Humanities, Anyway?

What Is Digital Humanities, Anyway?

Picture this: It's a gray Tuesday afternoon in 2019, and Dr. Sarah Thompson, a literature professor at a mid-sized university, sits at her desk staring at a spreadsheet. Not just any spreadsheet—this one contains every single word from William Shakespeare's collected works, coded and categorized by a computer program she helped design. To her left sits a cup of cold coffee, and to her right, a worn copy of *Hamlet* that she's read perhaps fifty times. On her computer screen, a visualization shows clusters of words and phrases, patterns invisible to the naked eye but suddenly blazingly obvious when rendered in colors and shapes. Something remarkable has just emerged from the data: a statistical fingerprint that suggests two scenes in *Henry IV, Part 1* might have been written by someone other than Shakespeare.

Now, what would you call what Dr. Thompson is doing? Is she a literary scholar? A data scientist? A computer programmer? The honest answer is that she's all three—and that's precisely the point. Welcome to the strange, wonderful, and occasionally contentious world of Digital Humanities, where literature meets algorithms, history shakes hands with data visualization, and the boundaries of traditional academic disciplines blur like watercolors in the rain.

Finding the Words: What Digital Humanities Actually Means

Let's start with the most basic question, the one that probably brought you to this book in the first place: what *is* Digital Humanities, anyway? If you've tried to Google a definition (and if you haven't, you will), you quickly discovered that this apparently simple question has a surprisingly complicated answer. The scholarly literature alone offers dozens of competing definitions, each emphasizing different aspects of this sprawling field. Some describe Digital Humanities as "the intersection of computing and humanities research." Others prefer to frame it as "the use of digital tools and methods to answer humanistic questions." Still others insist it's not really about the technology at all—it's about transforming *how* scholars think, regardless of what tools they use.

Rather than choosing one definition and asking you to memorize it, let me offer a more practical approach. Digital Humanities is whatever researchers do when they bring humanistic questions—questions about texts, artifacts, history, culture, language, art, music, and human meaning-making—into conversation with computational methods. These methods might include text mining, data visualization, geographic information systems (GIS), network analysis, machine learning, database design, or the creation of digital archives and exhibits. The key word here is "conversation": Digital Humanities isn't simply "technology applied to humanities" any more than a bilingual conversation is simply one language translating another. It's a genuine dialogue, where each side changes and enriches the other.

This conversational quality explains why Digital Humanities looks so different depending on where you encounter it. At a conference, you might see a medievalist using sophisticated imaging software to reveal faded text hidden in a 900-year-old manuscript. Down the hall, a musicologist might be demonstrating how algorithms can analyze thousands of folk songs to trace how melodies travel across continents. Meanwhile, a linguist in the next room uses corpus analysis tools to track how the meaning of the word "awful" shifted from "inspiring awe" (in a religious sense) to "terrible" over the course of the nineteenth century. All of these projects are unmistakably Digital Humanities, yet they share more in terms of *approach* and *attitude* than any particular methodology.

A Field Finds Its Name: The Historical Roots of Digital Humanities

Every field has a birth story, and Digital Humanities is no different. The version most scholars tell begins in the late 1940s, when a Jesuit priest named Roberto Busa began working with IBM to create something unprecedented: a computerized index of every word in the works of Thomas Aquinas. Father Busa wasn't trying to revolutionize scholarship—he was simply trying to save himself years of tedious manual work. The medieval philosopher had written millions of words across his career, and finding relevant passages was a nightmare of cross-referencing and footnote-chasing. If a computer could help locate words and phrases faster, why not use one?

What Father Busa created, over the course of three decades of painstaking collaboration with IBM engineers, was the *Index Thomisticus*—a searchable database of Aquinas's complete works that remains a landmark resource to this day. More importantly, his project demonstrated something that would take the academic world decades to fully appreciate: computers weren't just number-crunching machines designed for scientists and accountants. They could be partners in humanistic inquiry, helping scholars find patterns and connections that would otherwise remain hidden.

The next major chapter in our story takes place in the 1960s and 1970s, when humanities computing began to take shape as a distinct activity. Universities started establishing computing centers, and adventurous scholars began experimenting with early text analysis software. A project at the University of Michigan created the *Middle English Dictionary*, using computational methods to track word meanings and usage across centuries of texts. Researchers at Oxford developed tools for analyzing large bodies of literature. The Modern Language Association, that granddaddy of literary scholarship organizations, began offering workshops on computing applications. These pioneers faced enormous obstacles—computers were slow, expensive, and notoriously difficult to use—but they proved the concept: serious humanistic work could benefit from serious computing.

By the 1990s, with the rise of the internet and the personal computer revolution, humanities computing had grown from a handful of eccentric pioneers into a genuine movement. The founding of the Association for Computers and the Humanities (ACH) in 1991 gave scholars a professional home. The establishment of journals like *Computers and the Humanities* (later renamed *Humanity Text*) and *Literary and Linguistic Computing* created venues for sharing research. Most dramatically, the explosion of the World Wide Web forced everyone in academia to grapple with digital questions, even if they had no particular interest in computational methods. Suddenly, every department needed to think about what it meant to exist online.

The term "Digital Humanities" itself emerged around 2004, when a group of scholars began using it as a more modern replacement for "humanities computing." Why the change? Several reasons. "Computing" suggested something technical and specialized, while "Digital Humanities" emphasized the broader cultural transformation the field represented. The word "digital" also carried connotations of innovation and relevance that "computing" increasingly lacked. And perhaps most importantly, "Digital Humanities" sounded cool—it's hard to underestimate the importance of branding in academic movements.

The Computational Turn: How Digital Methods Transform Humanistic Research

Now that we have some sense of where Digital Humanities came from, let's talk about what it actually *does*. How, in practice, do computational methods change the way humanists work? This is where things get genuinely exciting, because the transformations cut to the heart of how knowledge gets made.

Consider the humble act of reading. For centuries, scholars have built careers on close reading—the careful, sustained attention to individual texts that reveals layers of meaning, allusion, and rhetorical strategy. A medievalist might spend years mastering a single manuscript, learning to read its scribal abbreviations, understanding its historical context, and parsing its archaic languag