Yesterday was Day of DH, when self-styled DHers live-tweeted and blogged their activities. Among the questions inspiring this event, the most important is “what is digital humanities?”

This popular tweet captured the extremely self-conscious nature of the exercise:

It’s funny because it’s true.

Personally, I spent much of the day glued to the #dayofdh Twitter reel. All those tweets
did shed some light on the main question at hand; meanwhile, they raised some other
issues. Here, I want to comment on one—namely, the issue of non-digital work. Is it DH
to read a book? Is it DH to check email or attend meetings? Where do ‘traditional’
humanities activities end and DH activities begin? What about teaching?

“No Actual DH”

“I didn’t have a #dayOfDH”

“Traditional librarianship” vs. “#dh duties”

“That counts, right?”

I don’t mean to pick on these tweeters; there is nothing wrong with any of these posts, on
their own terms. I did pretty much the same thing when I decided that I should work on
something “digital”
for the event. And besides, I have a sneaking suspicion there was some irony in one or two of them.

What troubles me here is the silence. That is to say, some people may have felt that their ‘traditional’ humanities-related activities, teaching and so on, weren’t worth tweeting about. I think this is likely, and such silence may serve to obscure the DH work which is not all about coding or metadata.

Whatever one’s definition of digital humanities, I think there is, and there ought to be, plenty of room for the humanities part of things (in spite of certain famous invectives against close reading). To wit, a tweet from my colleague:

Indeed, close reading and DH make sense together.

Here is another take on the larger issue:

It’s worth reading her full blog post: “DH without DH.”