We Are All Managers

When my wife attended an orientation session for her first post-college job, the human resources representative supplied helpful tips for developing “manageatorial” career skills. This felicitous neologism — it wonderfully conjures the image of a janitorial executive — has provided a reliable punch line for two decades; Daniel Allington’s recent jeremiad against digital humanities offers yet another opportunity to trot it out.

For someone who’s adamantly not a digital humanist Allington certainly seems to know quite a bit about these soulless managers. He writes, for example, “Humanists today are less likely to be technologists than managers of technologists. Why do something for yourself when what you will be rewarded for is having found the money to pay someone to do it for you? And how can you find time to learn a programming language anyway, when your core competence is fluency in the language of grant applications?”

To highlight just a few of his specious claims:

  • He fantasizes that digital humanities project budgets are artificially inflated to be “conveniently expensive” and that we willfully ignore opportunities to reduce costs.
  • He imagines that humanities funding serves as a university profit center, when unlike in the sciences it’s particularly likely to come from private foundations which typically don’t contribute a cent in indirect costs back to the university administration.
  • He characterizes DH technical staff as casual labor akin to adjunct faculty or worse, when vast majority of our developers and staff at my institution and at peer DH centers are salaried university employees who are not fired when a contract runs out (and in fact can’t be). The few contract developers we have are not regular employees by their own choice.

The whole post was so off-base I initially dismissed it as sour grapes, thinking he was simply feeling left out of what he imagines is a club of “successful players of the funding game.“1

After reading his extensive followup exchange with Stephen Ramsay, however, it became clear that Allington is writing from within a framework that digital humanists understand all too well from the other side of the fence, with their (often self-congratulatory) rhetoric of collaboration. And it is this aspect of his argument that deserves the closest scrutiny, and not because it marks Allington as an outsider, as he would like us to believe. Allington doesn’t appear to be antagonized so much by digital humanities in particular as by the notion that individual humanists should be dependent on anyone other than themselves. In response to pointed questioning from Ramsay about higher education’s essential vast array of human infrastructure arrayed to support professors like Allington, Allington declares, “What I disagree with is your assertion that these people are managed on my behalf. They aren’t.” In a later comment he adds, “Absolutely none of them acts at my behest – not because there’s anything democratic about the whole organisation but because each of us is contracted to provide a service. I provide one service, they provide others.”

Allington not only denies that DH is collaborative: he effectively denies that collaboration exists anywhere in academia across the faculty/other divide. Any relationships that span this divide are, by his definition, managerial, perhaps because Allington cannot imagine a relationship where the “humanist” (professor?) is not the boss of the programmer.

Allington thus declares himself unambiguously as not just an outsider in a system with interests utterly unaligned with his own, but someone who works above this system. To engage with that system is to dirty the hands and become manageator… er, managerial. Whether or not this system exists anywhere outside Allington’s imagination is irrelevant: the key point is that these interests have nothing to do in particular with digital humanities. He’s simply using a very big club (“managerial” academia is bad) to attack a very small problem (digital humanities is irritatingly “trendy”). I thought that the Enlightenment had freed us to start valuing the hands as well as the mind, but maybe it was just the pretext for totalitarianism. It’s easy to get confused.

Of course no scholar, humanist or otherwise, works wholly independently. What threatens this sense of independence isn’t really the oversight of project staff, it’s the dependence on outside funders, academic administrators, publishers, etc. Becoming a mere link in a Great Chain of (Scholarly) Being can never appear as gratifying as imagining oneself an academic hermit cultivating genius in exalted isolation.

Ultimately the fatal flaw in Allington’s argument isn’t that he dislikes digital humanities; it’s that he positions himself as if he is in the aggrieved minority, under ferocious assault from the grant wizards of DH and their administrative masters. And yet the collective experience of anyone who has ever undertaken any digital academic research points overwhelmingly in the opposite direction, that is to say that traditional scholarship is rewarded while digital work is universally undervalued or misunderstood. One can certainly sympathize with Allington’s irritation with the grandiloquent promise of the digital humanities, but there’s a very wide gulf between the echo chamber of Twitter and the backroom shenanigans of tenure and promotion committees. The latter, to date, are certainly more likely to find themselves in Allington’s camp than anywhere else.

  1. We meet on Thursdays. []

A Digital Humanities Tenure Case, Part 2: Letters and Committees

After my tenure presentation and with the unanimous vote of my department, my department’s RPT committee and our chair prepared additional letters to send the file up the food chain to the college-level promotion and tenure committee. These letters were embarrassingly favorable, and based on the excerpts they included from outside readers, those letters too offered overwhelming support for tenure. The college-level committee, however, wasn’t so easily fooled. Voting 10–2 in favor of my case, largely on the basis of my monograph in French history, here’s what the committee members had to report on the digital side of my portfolio:

The committee also recognized his considerable work at the Rosenzweig Center for History and New Media as it relates to projects such as Zotero and the substantial funds he and his collaborators have raised to help sustain them. Some on the committee questioned to what degree Dr. Takats’ [sic] involvement in these activities constitutes actual research (as opposed to project management). Hence, some determined that projects like Zotero et al., while highly valuable, should be considered as major service activity instead.

To recap: Conceive projects? Service. Develop prototype software? Service. Write successful grant proposals? Service. Write code? Service. Lead developers and designers? Service. Disseminate the results of the project? Service. I certainly hope program officers from Mellon, Sloan, IMLS, and NEH aren’t reading this post, because I suspect they would be more than a little dismayed to discover that they’ve been funding “major service activity.“
Continue reading

Hello Again, 2006: The Economics of Reference Management Software

The tiny and insular world where academia, technology, and business converge buzzed all day yesterday (and continues to do so today) about publishing giant Elsevier’s rumored bid to purchase Mendeley for $100M. TechCrunch’s dependably credulous reporter duly transcribed the leaker’s claims that publishing is “the world that Mendeley is disrupting.” But this story has really nothing to do with a “disruption” in academic publishing, and if anything what we’re seeing is a reversion to 2006 or so. When Zotero launched then, the major players were Endnote (Thomson Reuters) and RefWorks (ProQuest), each owned by a major content provider. And now in 2013 we can add to that stable of publisher-owned reference managers Papers (Springer) and, apparently, Mendeley (Elsevier).

As someone who has led a successful and sustainable project in this space for over six years, I’d like to put this rumor in perspective, because it speaks volumes about the space of academic research software, even if the Elsevier purchase never materializes.
Continue reading

A Digital Humanities Tenure Case, Part 1: “The Talk”

Is there anything that promotes introspective hand-wringing like the heady mix of tenure, promotion, and the digital humanities? The Journal of Digital Humanities recently explored this issue, and especially interesting contributions by Mark Sample and Katherine D. Harris offer retrospective looks at the role played by the digital humanities in their happily-ending tenure cases.

I’d like to go a bit further in raising the curtain on what’s unnecessarily viewed as a secretive and mysterious process, particularly when it involves digital humanities. Some of this mystery stems from the fact that there just aren’t that many people seeking tenure yet on digital grounds. But much of it is self-inflicted, because candidates are reluctant to disclose what’s happening, except perhaps after the fact like Mark. I’m going to raise the stakes by describing my case while it’s still very much unfolding. Since it would be unrelentingly dull to narrate the entire affair in real time (see timetable below), I decided to wait until now, around the halfway point, to begin posting.
Continue reading

Only a Historian

“The world needs ditch diggers too.” –Judge Smails, Caddyshack (1980)

At last week’s Digital Humanities Luxembourg (DHLU) symposium, a common refrain could be heard in nearly every presentation: “I’m only a historian.” Uttered apologetically at the beginning of a number of presentations, after two days it became the object of parody and ultimately comprised part of organizer Frédéric Clavert’s excellent concluding remarks. But despite the snickering each time it was heard, there was little investigation of what was behind this phrase. I think it actually reveals something important about the state of DH, perhaps especially in Europe but hardly exclusively so.1
Continue reading

  1. DH=digital history in this piece, though the concerns obviously have broader applicability in the digital humanities. []