- Students work individually
- Reports due one week after the final session of a given lab
- Some stellar entries will be posted as examples on the course website
Technologies of Text is an experiential course organized around a series of “humanities laboratories,” each with associated readings. A central goal of the class will be to bring its two facets into conversation: to use our readings and discussions to contextualize our applied work in laboratories, and to use our applied work in laboratories to enrich our understanding of concepts from our readings.
To help accomplish this goal, you will submit regular lab reports, which will constitute your central scholarly activity throughout this semester. Your entries will follow a template (which we will learn to access in the first lab in class) and include a mix of description, analysis, code, figures, or images. This ongoing assignment will give you the chance to organize the diverse tasks of the class’ experiential work, practice the skills introduced in the labs, bring your experiential work into conversation with class readings and personal research, and experiment with ideas that will be further developed in your Unessay projects.
Your lab reports will be composed using a regular template, which we will discuss on day two of class,
You can look at the template to see how these reports will be organized, but as an overview there are a few elements I will expect to find in each lab report:
A description of the lab activities completed. Most of our experiential activities will include specific outcomes. You might produce a specific material product, such as a letterpress printed sheet, or be asked to adapt the lab’s code to answer a new question. The first task of any lab report will be to demonstrate completion of these tasks. In the case of a coding session, you will likely integrate code snippets directly into your Markdown file (more on this as those labs approach). For other labs you may instead reference external proof of your work, such as photos.
Prose that reflects analytically on the work of the lab, putting it into conversation with one or two readings from the same unit of class as the lab. This prose need not be as formal as a research paper, but it should demonstrate careful thought and preparation. You should integrate the readings explicitly, if possible through direct quotation. Use this writing to experiment with intellectual pairings you think might be generative to your larger thinking and help you prepare for the class’ Unessay projects.
Organizing Your Lab Reports
Your lab reports will comprise a collection of Markdown or
.md files collected in the
lab-reports folder of your Github Classroom Repository. We will learn how to write in Markdown and contribute to Github during the first lab (which you will reflect on in your first lab report). Your repository will sync with my Github classroom so I can check in on your progress. I may also download particularly strong entries for reposting as model student lab reports on the class website.
You should name your files following the following convention:
YYYY-MM-DD-labreport-LABNAME.md (Year dash two-number-month dash two-number-day dash labreport dash name-of-lab-from-class-schedule period md)
ToT is a challenging and full class. The semester will include sixteen labs (a record for this class). To give you some flexibility, you will complete lab reports as outlined in your course contract, which will mean there will be some labs for which you will not submit reports.
Pacing Your Work
Your lab reports should constitute a developing record of your thinking about our class and its activities. Thus you should be working on them steadily, responding to the labs in a timely manner, in part to keep your thinking fresh and in part to avoid falling too far behind as new labs approach.
Lab reports are due within one week of the lab session. If a particular lab session extends through multiple classes, its report is due within one week of the final classroom session devoted to it. You may not wait until late in the semester to complete lab reports for activities earlier in the semester, and I will check your repositories periodically to ensure you are working steadily. The coding labs, in particular, will build on each other and you will find it difficult to complete reports for later coding labs if you do not complete earlier ones.
I regularly assign ongoing assignments in my classes and every semester I strongly urge students to start working early in order to complete the work. Each semester at least a few students ignore this urging, usually to their later dismay. Complications will almost certainly arise during the semester, and if you put off starting your lab reports you will struggle to earn full credit on this assignment.