#1 Repetition

Due in class on Thursday 10/26

“If something is boring after two minutes, try it for four.
If still boring, then eight.
Then sixteen.
Then thirty-two.
Eventually one discovers that it is not boring at all.”

― John Cage

Experimentation is required to gain familiarity with creating and planning computational works.

For our first project, you should experiment with the conceptual and formal powers of REPETITION. What does REPETITION do to a mind? To a body? How can REPETITION represent or complicate our understanding of a concept? How do the formal properties of REPETITION, such as in Tony Conrad’s Flicker, op-art, or techno, drone, or experimental hardcore create affects and meanings in the viewer/listener/participant.

The project requires you to embrace and express REPETITION. Begin by making a series of physical sketches (pen, paper, crayon, paint, etc). Consider the stresses on your body and feelings of pain, frustration, and joy that may emerge during this process. You should have at least 30 sketches, of various sizes and detail by the end of the process. Bring these to class on Thursday the 26th.

At the same time, explore how REPETITION works in code. What kinds of formal effects can you generate with for loops? How does REPETITION in space differ from REPETITION in time? How do you approach each in code? Is it possible to represent in code a process of REPETITION you executed by hand? Is it desirable? Is it efficient?

Make series of code sketches, in p5, processing, etc, that embrace REPETITION as a formal or conceptual scheme. After making 10 such sketches, choose one to deepen and extend. The final output could be a video (using screen recording), a print out, or a piece of software running on a computer or in a webpage. Bring both your code and the final output to class on Thursday the 26th. Try not be too concerned with your level of familiarity with coding. Use what you know, look things up, cobble ideas together, and ask questions. We will class time on Thursday the 19th and Tuesday the 24th working on our projects; writing code and asking/answering questions.

On the 26th, we will spend time with everyone’s project, looking at both the code and the drawings and discussing challenges, epiphanies, frustrations, and breakthroughs.