generated from rit-ecet-notes/new-course
Finish lecture 1
This commit is contained in:
parent
96533914fb
commit
10ce234d7f
1 changed files with 31 additions and 1 deletions
|
@ -6,6 +6,36 @@ There's a differentiation from text and stories.
|
|||
|
||||
Text can be separate from the story.
|
||||
|
||||
The definition of a text is fuzzy.
|
||||
Digital presentation of english characters is text in the same way that handwritten characters or printed characters are.
|
||||
|
||||
The definition of a text is fuzzy, and even a brief discussion of the definition can cause discussions.
|
||||
|
||||
if words can be different, from version to version, then is it still a text?
|
||||
|
||||
it sort of becomes a bit of "Ship of Theseus"
|
||||
|
||||
Clearly, we need to start with a well-accepted definition.
|
||||
|
||||
This is... the majority of the course.
|
||||
|
||||
What _is_ a text? What _is_ a code?
|
||||
|
||||
"In this class, we'll be thinking critically about the relationship between text and code", using poetry as the lens of analysis.
|
||||
|
||||
# Syllabus and Course Overview
|
||||
|
||||
The course is primarily discussion-based, and asking questions.
|
||||
The core work is readings and discussion forums. The goal is to encourage discussion.
|
||||
There are also text/code activities; these are "hands-on".
|
||||
We will also have a poetry and code anthology; showing our journey through the questions.
|
||||
Finally, there are process letters, which is mid-course reviews essentially.
|
||||
|
||||
"I am a qualitative rather than quantitative grader."
|
||||
If you submit work, you will get a submitted; if you didn't submit it, you will get a not submitted.
|
||||
There will be feedback!
|
||||
|
||||
late submissions aren't ideal, because work builds on itself.
|
||||
|
||||
Fridays will have a discord check-in discussion forum.
|
||||
|
||||
Wednesday's discussion covers why we're using poetry in the first place.
|
||||
|
|
Loading…
Add table
Reference in a new issue