Objective:
- To learn the basic setup, including independent study of code syntax, uploading files on github, creating a readme file, etc.
- To get familiar with the building and feedback process of weekly mini exercises
- To reflect upon the process of coding
Get some inspiration here:
- Daily sketch in Processing by Saskia Freeke
- dwitter.net-within 140 characters of JS
- zach lieberman
- Creative Coding with Processing and P5.JS
Tasks:
- Make sure you have read/watch the required readings/videos of the class00 and class01.
- Study at least one syntax from the list of p5.js' reference (of course, it is always good to know more different syntax. Be curious!)
- Familiar yourself with the reference structure: example, description, syntax and parameters (This becomes your essential and life-long skills for learning new syntax on your own)
- Use, Read, Modify (or even combine) the sample code (the most basic level is changing the numbers), and produce a new sketch.
- Upload your program/result to your own Github account under a folder called mini_ex1. (Make sure your program can be run on a web browser)
- Create a readme file (README.md) and upload to the same mini_ex1 directory (see this for editing the README). The readme file should contain the followings:
- A screenshot about your program
- A URL link to your program and run on a browser, see: https://rawgit.com/
- Describe your first independent coding process (in relation to thinking, reading, copying, modifying, writing, uploading, sharing, commenting code)
- How your coding process is differ or similar to reading and writing text? (You may also reflect upon Annette Vee's text on coding literacy)
- What might be the potential and possibility of coding practice?
- Provide peer-feedback to 2 of your classmates on their works by creating "issues" on his/her github corresponding repository. Write with the issue title "Feedback on mini_ex(?) by (YOUR FULL NAME)" (Before next Wed tutorial class)
NB!: Feel Free to explore and experiment more syntax
What is peer-feedback?
- First you describe what is the work, what are the elements in the work? like what you have seen, what you have experienced and what syntax he/she has used.
- What is the emphasis? What does the work express? What does this work say or mean to you? How would you interpretethe work?
- Do you like this program, and Why? and which aspect do you like the most?
- Provide suggestion for improvement or expansion of the program