William Turkel’s lecture “The Hands-on Imperative”, his subsequent talk to our DHpraxis class and then workshop had me thinking about a number of different things, specifically the issue of space, the issue of tenure portfolios that contain fabrication and physical experimentation projects, and how failure is something to embrace and not fear.
His discussion of space and the need for a place to make things, to play and create resonated with me. In a blog post “A Few Arguments for Humanistic Fabrication” on his blog “Digital History Hacks 2008” Turkel said
“The limitations of our physical spaces can be more difficult to circumvent. Most of the teaching and research environments available to humanists at my university are designed to support solitary or small-group office work. These spaces are almost comically unsuitable for the kinds of things I try to do with my students: soldering, mold-making and casting, building and lighting physical exhibits, programming in groups, creating displays or signage.”
One really has to always be aware of space and how and why a space is being used.
As a librarian I’ve always been aware and concerned with the physical space and layout of a library and how the space affects people’s use of the library. If the space is not inviting, if it doesn’t match what people are using a space for it can be a real hindrance, stifling creation and education. The fact that humanities spaces in academia are not set up for play and creation of physical objects does not surprise me at all. We need to be able to break out of the confines we find ourselves in but many times in academic or corporate spaces we are not allowed to break out. Trying to convince administrations to permit a space in an academic department where you can vent fumes, use power tools etc. is not going to be easy, I mean we aren’t even allowed to pick a different wall color to paint our student lounge. If we cannot even personalize the color of the walls of our own student lounge, how can we expect to create a space where we can have “high ceilings, natural light, plenty of ventilation, cement flooring, workbenches on casters, locking cabinets, big blank walls where you can hand things on. No carpeting, no beige cubicles, no coffee tables with plants.”
Another hot topic in DH, which we have been reading and talking about in class, which Turkel’s talk and workshop had me thinking about were issues of tenure and how DH building projects and work relate and are counted towards an academic’s tenure portfolio. In Stephen Ramsay and Geoffrey Rockwell’s chapter “Developing Things: Notes toward an Epistemology of Building in the Digital Humanities” in the book Debates in the Digital Humanities the authors ask “how do we” and “can we” count the work of builders, hackers, coders as scholarship? How is work on and about XML, XSLT, GIS, R, CSS and C counted and evaluated? Is it scholarship? How will it be evaluated and can it lead to promotion and tenure? Lev Manovich believes “a prototype is a theory.” Stan Rueker and Alan Galey say that “the creation of an experimental digital prototype [should] be understood as conveying an argument about designing interfaces” and that digital artifacts themselves, not just their surrogate project reports should stand as peer-reviewable forms of research, worthy of professional credit and contestable as forms of argument. “It is the prototype that makes the thesis, not discursive accompaniments like white papers, reports and peer-reviewed papers.” My question is – are these beliefs truly occurring in practice in academia today? Can a faculty member truly include the objects they make using Max 6, Phidgets, Arduino or Makey Makey in their tenure portfolio and have it count in a meaningful way towards tenure? Are academic departments and institutions willing to accept this type of work as scholarship and worthwhile of tenure? And if not then what does that mean? Should we stop making things or should we continue to make things even if they are not counted? How can we work to ensure that this type of work is considered scholarship?
Finally, Turkel talked about failure and what can be learned from failure. He talked about how some of the best students in his class are those who have no training in programming or shop classes and therefore have no preconceived notions of what can and cannot be done and are not afraid to fail. At various library jobs I had, where I had staff, I would tell them not to be afraid of making a mistake when working on the library catalog. I would tell them to be inquisitive and to explore the program and to ask questions. I assured them I set it up so that they couldn’t destroy the catalog and that their exploring and using the system was how they and I would learn. I try to follow this philosophy myself when setting up database interfaces and catalog systems. However, it is not always easy. Fear of failure and the consequences of that failure on job security (and sometimes grades) are real fears. I think it is great that Turkel is able to assure his students that they will not fail his class if their projects fail but in many instances, in many jobs, this is not a promise one is given. I always joke that the only job where you can be wrong all the time and fail and not get fired is weather person. I say it jokingly but it is somewhat true. In academia or in corporate culture, having a project fail is not always looked upon in a positive light. As the people feeling the heat from the Federal Government Affordable Care Act Marketplace web site can attest to, people do not seem to think the current problems are “learning experiences.” How do we then promote inquisitiveness, willingness to take chances and possibly fail in the projects we work on in DH without the fear of the consequences of our failure?
“I’ve missed more than 9000 shots in my career. I’ve lost almost 300 games. 26 times, I’ve been trusted to take the game winning shot and missed. I’ve failed over and over and over again in my life. And that is why I succeed.” — Said by Michael Jordan in a Nike ad, written by Jamie Barrett. http://youtu.be/GuXZFQKKF7A
II totally agree with you about the space and tenure issue but they are even worse than you describe. The graduate center is gradually eliminating any collective “lounge” space as if it was secondary to education and creating funding that means graduate students are rarely in the building. But creating a face-to-face community is essential to academic life from my point of view and that requires both of the above. The tenure issue rings true to my experience but even more so. Most departments won’t give you credit for any collaborative work even if it is the traditional writing. I was urged to write papers under individual authorship even though I also worked in collaborative groups. I didn’t do it and fought to get my tenure (which I did) but it wasn’t easy. Alternates to traditional forms of expression are discouraged.
I keep having this niggling feeling when certain questions have been asked in this class. Amy, you bring them up in relation to space and to making: “Can a faculty member truly include the objects they make using Max 6, Phidgets, Arduino or Makey Makey in their tenure portfolio and have it count in a meaningful way towards tenure? Are academic departments and institutions willing to accept this type of work as scholarship and worthwhile of tenure? And if not then what does that mean? Should we stop making things or should we continue to make things even if they are not counted? How can we work to ensure that this type of work is considered scholarship?”
Is the concern about scholarship and tenure? Or is the concern about what the digital humanities can do for students?
I’m going to explore this more in my blog post on the pedagogy readings, but I’ve been thinking a lot about the questions that are raised by DH, and so far they have seemed to focus on scholarship, tenure and research – which are all very academy-centered things. It’s a small percentage of students that stay within the university system. What does DH do for them?
Jacky – I agree that issues of DH should be looked at from many different aspects and angles. For someone doing DH who works in academia questions of scholarship, research and tenure are very important. For someone who is a teacher (whether in K-12 or higher education) questions of DH deal with scholarship, tenure, research and pedagogy. Are the DH tools being used worthwhile and helpful in teaching students, in imparting information or are they just shinny objects? How, as a teacher, are you to learn how and when to use these various DH tools? For people studying DH who are not in academia and are not teachers, what are their concerns? Do they have the same concerns about what benefit play has in their education and what they are going to do with the DH they have learned?
Your other musing “is the concern about what the digital humanities can do for students?” was very relevant to today’s class conversations and readings. What can digital humanities do for us, the students in this particular course? What DH tools would be helpful to all of us to learn DH? We have this public class blog and private class forum but what other DH tools would be helpful in this introductory course?