Archive of 2017 Course Materials.
Home. // Assignments/Grading. // Schedule. // Policies.
Shorter writing assignments
These writing assignments will be brief but engaged. This will sometimes mean a very brief (e.g. 25-50 word) reflection on some reading. Other times, it’ll mean submitting process journals that are a little longer (150-250 words).
Brief Reflections
These are intentionally short because the expectation is that they’ll be dense. Students are asked to critically engage some reading, tool, or process and, in the brief space of a specified number of words (usually 25-50), articulate the central arguments or assertions (implicit or explicit) and work to situate those within the context of our course.
Process Journals
Process journals, in addition to being slightly longer, will trend more toward the experiential narrative. As we learn new technologies or methods, you’ll occasionally be asked to compose a process journal entry that encapsulates your experience with those technologies or methods. That is to say that it might simply describe how you perceived the topic before our work with it and then after, reflecting on that change. It might also, however, explicate a particular intellectual or methodological challenge that you had to overcome: what was the nature of that challenge and how did you overcome it? What was gained by the experience? If you step back and reflect, can you see how this troubleshooting experience might apply more broadly to your work with technologies and methods in general?
Submission Procedures
Navigate to the “class-journals” directory and remember our process:
(1) Navigate to the directory that’s your last name, which you’ve previously made.
(2) Create a Branch (name it something descriptive).
(3) Upload or create your markdown file called “[lastname]-[assignment_designation].md” within your directory.
(4) Be sure to make commits along the way that very briefly describe what you’ve done.
(5) When you’re happy with it and want to submit it, create a pull request and merge your branch into the “master.” be sure that you’re able to merge without conflicts!
An Introduction to Digital Humanities by Jacob Heil is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.