Monday Review Format
Each student will have 5 minutes to present 5 slides and demo their piece, 10 minutes for feedback.
Send up to 5 slides as a pdf to Jack by Sunday midnight. These will be compiled and run off the classroom iMac. Practice your presentation before Monday.
The goal is to have as little time wasted on technical issues and setup as possible!! If you have software to demo from your laptop, have this already running so you can switch the projector input to show it easily. If you have something installed, be sure to turn this on before your turn. We will be sending out the review order soon.
Monday Review Schedule
1:10 Welcome
1:20 Yangyang
1:35 José
1:50 Woohun
2:05 Fernando
2:20 Break
2:30 August
2:45 Xinyu
3:00 Carly
3:15 Sang
3:30 Justin
3:45 Break
3:55 David
4:10 Adrianne
4:25 Jason
4:50 Hyo Jin
Content for Monday’s quick presentation
We’d like you to cover at least these 5 points in your presentation/slides.
- Project summary (what did you do, what is the experience)
- Concept & background (why, inspiration, etc.)
- Tech (what technology did you use)
- Limitations (what were you not able to do, what could you improve)
- Future work (what’s next? how do you think this could go further)
Useful material
State diagrams & Flow charts (lecture, Nov 19)
Coding practice and debugging tips (lecture, Nov 12)
Criteria for project evaluation
Your final project will be evaluated by a number of factors, based on three components, described in detail, below.
Remember that all criteria are important, and that you are not expected to have the perfect, final technical installation piece at the end of the class. Instead, we expect that you either have:
-
A working prototype that demonstrates the concept
-
A set of smaller experiments that are examples of your larger vision
It is very important that the project is well-documented with clearly understandable code, and that you show that you understand everything that you have used in your project. We would also like to be able to run your code on our own machines, so you need to document everything it takes to install and run your application.
1) Project documentation / presentation
-
Descriptions, explanations, text, …
-
Images, video, sketches, illustrations, …
2) Technical
You are welcome to use code and libraries that you integrate into your project. But you need to show that you understand all pieces that you use, and show that you adapt it in a creative way for your own purpose. For example, not just copying someone else’s code and change some parameters.
-
Code structure
Logical separation of components into functions or objects to make your program easy to understand.
Variable and function names that make sense and make the program easy to follow.
-
Commenting
All non-obvious parts of your code must be commented with explanations.
If there are parts that you don’t understand, comment them as well, and then make sure you discuss them with Jack, Lauren or Alex before the final.
-
Documentation
An explanation of how your software works. How does a person install and run it? (any extra libraries needed?)
What input (keyboard, mouse, sensor, etc.) it uses, and how it responds to it.
3) Concept / creativity
How creative were you in using the techniques introduced in this class for an artistic purpose?
What other elements did you integrate to achieve your vision?
How well do you describe how your prototype(s)/experiments could fit into a larger vision/project/installation?
How clearly do you describe other options for using different/alternative technology to achieve similar expression or other realizations of your vision/concept?