Professional Practice Learning Goal #2 requires that all students present a professional body of work in an online context, demonstrating a critical awareness of audience and selection of work. Because we're exploring the professional practice of creative technologists, our "online context" will be the development of a GitHub portfolio. If you're not already familiar with GitHub, you can think of it as LinkedIn meets Behance for coders and developers. In addition to being a space to share your work and connect with others in your field (potential collaborators as well as recruiters), GitHub is also a space for "maintaining" and "versioning" your code as well as for the structured development of "open source" projects (all of which are concepts we will cover in class).from the syllabus
If you don't have one already, you will need to create a GitHub account for your online portfolio. If this is your first time setting up a GitHub account, you might consider signing up for the GitHub Student Developer Pack which comes with all sorts of valuable freebies.
Below is the narrative for the first half of the semester. There are various different assignments to choose from (so long as you complete a minimum of two assignments, designated by the red underline). Because everyone is going to be entering this course with different coding experience, everyone will likely start the semester at a different point in the narrative below. Read through the narrative and choose the point that feels right for you.
You're ready to make creative coding a central part of your professional practice...
You take a moment to admire the hand coded sketch you created while following along with the videos, and you feel empowered. You decide to spend a bit more time experimenting with it. Inspired, you remix the code around, deleting a few bits and editing some others. You've got some ideas you're not sure how to code, so using the new web dev lingo you learned from the videos you search on duckduckgo for a solution (you don't trust Google of course, on account of all the data they mine from you). There you come across an answer to your question on a website called stackoverflow, so you copy the code into your code editor and with a few minor tweaks you've got things working (mostly). So you update your GitHub project, copy the URL and proudly submit it to the canvas page as your first assignment.
You've got a GitHub account and you've created a repo, but you don't really get GitHub. You know GitHub has something to do with "open source", which is a term you've heard before and generally understand, but don't know that much about. So you read over Nick's notes on FLOSS (Free/Libre Open Source Software) and check out some of the videos on the playlist he curated, before watching the video he made on the new media concept of "versioning" (~18mins). Having a new appreciation for the history, theory and politics of a movement you've now become a part of, you decide to brush up a bit more on your GitHub skills. You already know how to get stuff up on GitHub using their website's interface (~24mins), but you also want to learn how to do it directly in your code editor (~17mins) and maybe even the terminal (~21mins) (like the l33t h4x0rz do).
Before you realize it you've got a couple pretty cool creative code sketches in your GitHub account, just in time too! We've reached the middle of the semester and it's time to start collaborating with others on our class Internet Artware project!