SIP Day 55, wearing a black tank and black cotton shorts; writing from the desk in my home office; 75 degrees outside today.
Tonite is the last class session for HIST 301, the environmental history course that I am teaching this semester. This ending feels more somber than usual, given the struggles to stay connected to students this semester. Generally I feel a strong sense of satisfaction at the end of a term, and I’m not sure that I will feel that this year, and I suspect that this feeling is shared by my students.
SIP Day 46, wearing a white cotton blouse and olive-colored skirt, writing from my home office; 87 degrees outside today
It’s the second-to-last week of classes and about this time every semester I become extremely nostalgic, knowing that the end is near and realizing how much I will miss this most recent batch of students.
This year has been so much harder in some ways–moving to fully online before I really felt that I knew my students and that we had the ease of having established class norms. It is also the first time that I haven’t had my class over to my backyard, to sit together and nibble on some garden produce and discuss weighty topics of environmental history, such as “What is wilderness?” and “What are the costs of preservation?” It’s not nearly as easy to discuss these ideas while in a Zoom session, nor did it feel that we were relaxed enough to just “talk” together due to the fact that the entire country (if not the entire globe) is in stasis due to COVID-19.
It’s my hope that the students will take away something that will stick with them long after the class is over, despite it being such an awkward semester. I know it will be one that I will never forget.
***
Finished Reading: The Nightingale. It was a bit formulaic for my taste, but still a moving story of the French resistance during WWII. Would be a good poolside or airplane book, and sucked me in and kept me interested despite the difficulty that I’ve had focusing on novels this month.
The past few days I’ve been moving to a new office space at work. The new digs are modeled on thecompletely open office concept of Facebook (fwiw, I know FB is evil, but I do think they do some things right):
I know there’s been a lot of research showing that completely open office plans can disrupt attention. However, it can also contribute to an ethos of collaboration and openness, which is what I’m seeking to create in this new space. In our division we are working to bring people into the space to experiment with technology, and want to reinforce the ideas of visibility and creativity. I believe this open-office concept is a very visual and impactful way to send that message.
For quite some time I’ve used GoogleDrive to store my course materials. For me it is the easiest way to manage the many documents that I create during a semester, and the iterations of those documents as I update them each time I teach a class. To share these documents with my students I add them as hyperlinked content on Blackboard.
However, this semester I had two unanticipated experiences from using GoogleDocs, which seemed worth sharing with others who are using this tool in the classroom.
I created a folder in GoogleDrive for each of my students to store content related to their end-of-semester research projects. For example, I created a document called “Sources” in that folder where the students were required to upload the online links (or images of book covers) for their research sources, prior to completing their writing. By having their sources all in GDocs, I was able to peruse and comment on each one, to either validate it as an appropriate source or to suggest alternatives when the source did not match the students’ research question or the parameters of the assignment. I was surprised, however, as I was navigating through these GDocs, to find that many of the students were logged into the Docs at the same time that I was leaving my comments. This allowed us to virtually “chat” through the comment stream about their sources, and was a surprisingly informal and helpful way to offer suggestions and corrections for the students. In the future I intend to experiment with holding virtual office hours via GoogleDocs, which seems an excellent way to be available for conversation with my students during times that they might not be on campus or I might not be near my office phone.
I discovered about halfway through the semester that in one of my classes where I created and linked to the stored syllabus in GoogleDocs, that they students were “chatting” on the syllabus page during class about the course material that I was presenting in class. At first I was taken aback and uncomfortable with knowing this–were they not paying attention in class and instead chatting with each other virtually, becoming something like a class snapchat account? But then I realized that it was pretty ingenious of them to use this tool that I’d given them in a way that I’d not expected. In fact, one class session where I was at a conference and had scheduled a guest speaker for the class, I jumped into the syllabus document and chatted with the students while they were in class and I was at my conference hotel. I loved that I got to “check in” with them in the moment, virtually. Their candid responses to the speaker were also helpful to me–they said that they were learning a lot from him! This assuaged any guilt that I had for not being present that day and allowed me to feel better about what was occurring in my classroom.
These experiences have cemented my interest in using GDocs in the classroom. In both intended and unintended ways, they are excellent tools for student collaboration of all kinds.
This morning I did my regular WordPress maintenance tasks: upgrading to the latest stable release, updating plugins, clearing out spam comments, etc. And as I did so I looked at the tagline on my portfolio site and realized that it needed updating.
It was:
So now it has a bit more alliteration, and better reflects my current professional identity. Because while I am a historian, I write and think more about teaching than about history.
So it is now:
There are so many other things I could put there: Paddler, Reader, Gardener, Friend, etc. But for right now, these three words seem the best fit.
Image is from Martha Burtis’ keynote talk at the Digital Pedagogy Institute that I attended earlier this summer. Her full talk is available here.
I am a teacher, and am happiest when I am grappling with how to share what I know and what I think with others. Thus, I am fortunate that I hold a position where I am teaching nearly everyday–either through technology training or through teaching courses at ChapmanU.
With this new semester, as with each new semester, I am considering how I can improve my teaching skills. And I’ve determined that incorporating a more regular reflective practice will be the best way that I can improve my teaching. I’ve written about this a bit before on my blog, but I am now committing to make this a more explicit focus of my blogginb.
So, to start off, I will invoke one of my greatest mentors and fellow Friend, Parker J Palmer, who asks:
“How can I develop the authority to teach, the capacity to stand my ground in the midst of the complex forces of both the classroom and my own life?”
He clarifies, that by “authority” he means:
In a culture of objectification and technique we often confuse authority with power, but the two are not the same. Power works from the outside in, but authority works from the inside out. We are mistaken when we seek “authority” outside ourselves, in sources ranging from the subtle skills of group process to that less-than-subtle method of social control called grading. This view of teaching turns the teacher into the cop on the comer, trying to keep things moving amicably and by consent, but always having recourse to the coercive power of the law.
External tools of power have occasional utility in teaching, but they are no substitute for authority, the authority that comes from the teacher’s inner life. The clue is in the word itself, which has “author” at its core. Authority is granted to people who are perceived as “authoring” their own words, their own actions, their own lives, rather than playing a scripted role at great remove from their own hearts. When teachers depend on the coercive powers of law or technique, they have no authority at all.
I am painfully aware of the times in my own teaching when I lose touch with my inner teacher, and therefore with my own authority. In those times I try to gain power by barricading myself behind the podium and my status while wielding the threat of grades. But when my teaching is authorized by the teacher within me, I need neither weapons nor armor to teach.
Authority comes as I reclaim my identity and integrity, remembering my selfhood and my sense of vocation. Then teaching can come from the depths of my own truth—and the truth that is within my students has a chance to respond in kind.
His words remind me of something that I have grappled with so many times as I’ve stood in front of a classroom: that feeling of vulnerability and exposure that comes from the unpredictability of human interaction, as well as the actual physical limitations of my own body to enact and enable a teaching experience.
Perhaps I feel this more keenly because of my awareness that my body can be awkward in the physical space of the classroom. On days when I am using crutches it can be nearly impossible to deftly use the podium computer or to meander around the desks of the classroom. Or on some days when I am physically spent and need to sit instead of stand, I feel the challenge of engaging students with my less-than-powerful physical presence. And of course even on days when I am standing confidently there is the sense that my cyborg body is speaking louder than the words that I am sharing with the students.
But then there is the flipside of that, the fact that I am more physically vulnerable can break down the barriers that might be typical between professor and student. If we all gather our chairs in a circle on a day that I need to sit, the students also move away from the spaces of their desks and the trappings of their classroom role. On those days there is no barricade of podium and desk. On those days learning can happen in ways that are quite different from the learning that occurs when I am delivering content from a screen.
Given that I have little control over the days that I can stand in front of my students versus those that I cannot, I try to do the best I can to prepare for whatever might happen when I enter the classroom. A teaching exercise that I used in the past might have to be altered, or a student might need to run the technology if I cannot. If nothing else, it keeps the teaching experience varied, fresh, and open to all kinds of learning possibilities.
So, to return to reflection about my teaching experiences this week, here is a list of a few moments that stand out:
Giving each of my students in my Introduction to Digital Humanities course, their own WordPress site, as a sandbox domain where they can write/play/experiment and carry out the weekly practicum exercises for our class.
Supporting dozens of faculty in using the Chapman ePortfolios platform for creating their T&P dossiers, and in doing so, helping them to create the best-possible digital representations of their scholarly efforts. The wide gamut of content that faculty can embed and link to from their dossiers is not only remarkable, but represents the best and brightest work done by early-career scholars at our university (and never ceases to inspire me to do better work myself).
Leading a workshop on how to use Classroom-Response Systems at a time where we had a major technical snafu that resulted in my presentation being derailed. Having to accept that the workshop was unrecoverable in that moment (there was no graceful alternative) and not letting my frustration about something that I couldn’t control, completely derail the conversation about how instructors could use technologies for student-response.
Allowing students to choose the platform for their collaborative sharing: one class created a closed Facebook group and the other opted to create a Slack Team.
Having my Intro to DH students read the “Letters to a Future Student” from my previous classes. Seeing that this exercise increased their enthusiasm for what they will learn this semester as well as their sense of courage to try new/hard technologies.
As I think about this list and all that has already happened in this Fall semester thus far, I am feeling pleased about my efforts. As Palmer reminds us,
Good teachers join self, subject, and students in the fabric of life because they teach from an integral and undivided self; they manifest in their own lives, and evoke in their students, a “capacity for connectedness.” They are able to weave a complex web of connections between themselves, their subjects, and their students, so that students can learn to weave a world for themselves…
Back when I was a student, I hated the first day of classes (aka Read the Syllabus Day). One semester I rather snarkily informed each of my professors how much I’d paid for their class that day, and that I didn’t feel as though I was getting my money’s worth when the day consisted of having the prof read the syllabus to me (especially because I had already rather-thoroughly perused the syllabus myself beforehand).
What I intend to do this year, which I am hoping will go over well, is to have students learn from my previous years’ students on the first day of class. At the end of last semester, I had each student write a letter “To a Future Student” in the class, and I will pass these out and have the students read them and discuss them as a class, which I will then use to launch into a discussion about class norms, expectations, and policies. I’ll then use that to lead into a brief overview of the class which will cover many of the items in the syllabus.
For a long time I’ve been thinking how helpful it would be to have some of the expertise of my colleagues in IS&T, in my Digital Humanities course. At a conference I’d heard about the benefits of embedding librarians within research courses, and it seemed to me that embedding technicians within a DH course would accomplish a similar aim, and would also reinforce the nature of DH as a collaborative discipline.
So today was my first foray in that vein, as Ryan (a member of our server team) attended my class and gave a demo of the inner guts of a PC and a server machine.
It was successful enough that I will try it again in future classes, and may also call on other technical expertise from our IT department throughout the semester. Because while I don’t think the students need to know all of the details of how a computer works, it is important for them to consider the limitations of various devices and platforms as they imagine the possibilities for their future research projects.
When I prepped my syllabus for the “Introduction to Digital Humanities” class that I taught last year, I included Ted Nelson’s article “Complex information processing: a file structure for the complex, the changing and the indeterminate” because I wanted my students to gain some historical knowledge about how modern-day computer interfaces developed from the ideas of visionary thinkers like Nelson. At the time, I was unaware that Nelson would be a Visiting Fellow on our campus or that I would have the luxury of becoming personally acquainted with him.
Ted Nelson, who coined the term Hypertext.
My students struggled a bit with the Nelson article. Not only was it long, but his ideas didn’t seem to spark much interest. As we discussed his piece together, I pointed out just how revolutionary his thoughts were in 1965, but that seemed to have little impact on their thinking. Moreover, his ideas about hypertext, or links between words and documents seemed so obvious to their minds that it was difficult to underscore their significance. So I took a different tactic and we created a list of all of the characteristics of Nelson’s imagined platform: it would be connected and iterative and creative and collaborative. It would “grow indefinitely, gradually including more and more of the world’s knowledge.”
“Do you know of any platform like that?” I asked.
The response: Wikipedia.
When I shared their reply with Ted a few weeks later, he seemed frustrated. And I could see why. Wikipedia, although a valuable resource and an excellent knowledge repository, is not a creative space. Indeed, it tends towards being rather scripted and formulaic, as well as hierarchical in ways that don’t gel with Nelson’s vision.
My students’ response to my question about Project Xanadu points to the unrealized nature of Nelson’s early vision–we remain locked into ways of digitally writing that replicate paper and although many of us read e-books or use text-based apps of various kinds, they are simply re-presentations of analog modes of creation. But it also points out a far larger problem: that the development of our computer interfaces and software feels like a “given” to most students. They have difficulty imagining that computers could have developed a different way or with an alternate mode of interaction. Which concerns me about how they may imagine their own future–as a series of inevitabilities rather than as dynamic and evolving threads of occurrences on a canvas that they can manipulate and shape to their liking.
I’ve been going through the dozens of “draft” posts that have never seen the light of day. This is one of those (from November 2012), which I didn’t post because at the time I was hesitant to admit some of my tech-frustrations…
For the first few weeks of the semester I had a running joke with one of my colleagues, where I would come back from class and she would ask me what I’d broken that day. Because, for whatever reason, nearly every digital tool that I was trying with my students ended up having a major snafu when I presented it to them in class.
There was the class wordpress blog that ended up stalling when I asked all of the students to post comments simultaneously, and the SIMILE timeline tool that broke whenever the students tried to add events that extended over a period of time, the day that I introduced Prezi that also coincided with the very hour that they rolled out an unannounced upgrade to the menu structure of the software, and numerous fails with using Blackboard tools (the wikis and discussion boards simply weren’t robust enough to be accessed by 25 users at once). Finally, yesterday, I learned that when I asked my students to all create wikipedia accounts, we learned that they screen by IP address for new registrations and had put a 24-hour hold on any new accounts being added from our classroom.
Fortunately I’m fairly patient with technology. Since I’m fussing with it nearly all-day long, I’ve learned that there are almost-always workarounds. Even when they mean using pen and paper (and typewriters).
In teaching my “Intro to DH” class last semester to Chapman’s MA/MFA graduate students, I spent a lot of time discussing professionalization and a significant part of that discussion focused on how funding agencies (like the NEH-ODH) make DH projects do-able. As the culmination of this conversation, for the final project in the course I had the students compose mock applications for an NEH-ODH startup grant.
I designed the course in this manner for three primary reasons:
1) The first time I had to write a grant proposal for external funding, I found it incredibly daunting to describe what I aimed to do with my project when I wasn’t even yet sure myself what I would find once the project got underway. Doing the legwork and the guesswork involved in that process and then writing coherently about it, was much more difficult than I expected. Thus, I felt that it would be a great learning experience for the students to do this before they had actual money at stake.
2) Crafting a mock NEH-ODH application reinforced many of the concepts that we’d discussed in class, and brought them together in such a way that it showed me that the students understood the filed of DH better than if they’d simply written a traditional end-of-the-semester paper. In their proposal they had to discuss other similar projects, outline their technical requirements, include descriptions of team members’ skills, craft a budget, and create a plan for the sustainability of their project. From their proposals I had a strong sense of what they’d learned throughout the semester since when the class started the students had only the foggiest notion of what a DH project entailed.
3) Writing a grant application is a portable skill that could serve the students in a wide-variety of ways after they graduate, even if they don’t continue in academia. Learning to communicate their research ideas to a general audience could serve them in many ways, including a future in technical writing, project management, journalism, or in a non-profit job.
The success of the students in their proposals far exceeded my expectations. As each student gave a lightning talk description of what they aimed to do, I realized that nearly every one of them was worthy of funding. And not only that, since December several of the students have moved forward with their projects on their own (sans funding), based on the proposals that they outlined in our class.
