Skip to content

risd-creative-programming/s14-creative-programming-projects

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

197 Commits

coding-best-practices-workshop.md

coding-best-practices-workshop.md

 
 

github-workshop.md

github-workshop.md

 
 

open-source-workshop.md

open-source-workshop.md

 
 

readme.md

readme.md

 
 

Repository files navigation

Projects in Creative Programming

RISD Digital+Media, DM2130, Spring 2014
Mondays 1:10pm - 6:10pm, RM 407, CIT
Class website: http://is.gd/dm2130
Class mailing list: https://groups.google.com/a/risd.edu/forum/#!forum/risd-cp

Evelyn Eastmond, [email protected]
Lauren McCarthy, [email protected]

##Overview

This course is a graduate-level hands-on creative-programming studio, supporting conceptual and technical research and development as students build ambitious projects of their own design. This course is ideal for students working on projects with elements involving code and needing a shared research dialogue and space within which to work, ask questions, seek guidance and exchange ideas. The course will consist of a combination of individual meetings, group critiques, and focused topic-and-tool-specific workshops. Access to a full array of languages will be supported. Workshops will focus on more refined technical strategies regarding organizing, sharing and working with large quantities of code, as well as additional topics specific to students' needs. The course will also encourage students to articulate the conceptual and material contexts of their work and to address the considerations of launching projects in social, online, hybrid and physical spaces of engagement.

##Schedule

####Week 1 - Feb 17: Workshop 1 (Github)

  • Introductions and syllabus
  • Git and Github workshop
  • Homework (DUE February 24):
    • Create your personal class blog
    • Add name and link to class readme.md on git, submit a PR
    • In the first blog post include:
      • What is your project?
      • What are the technical requirements?
      • Where do you need most help?
      • Proposed timeline for the semester

####Week 2 - Feb 24: Check-in

####Week 3 - Mar 3: Individual meetings

####Week 4 - Mar 10: Check-in

####Week 5 - Mar 17: Workshop 2 (Creative Coding Best Practices)

  • Creative Coding Best Practices
    • Time Management
      • Discuss readings
      • Discuss estimation exercise
    • Version Control
    • Code Organization
    • Common Errors
    • Debugging Strategies
    • Homework (DUE March 17):
      • Prepare for the midterm on March 31. You will have 15 minutes for presentation and feedback. You decide the format for your review and lead us through it. Think about what you hope to get out of the review and how you will elicit this feedback. Have in mind a few questions that you hope to find answers to. Give us a sense of what you've done so far, and where you're hoping to get to by the end of the semester. Give us something to react to. Make sure you have explicitly decided on the format before class, don't just wing it! After the reviews we will have a meta-discussion about the different types of crits we tried, how they worked, which feedback was helpful, next steps, etc.
      • Project blog post

####Week 6 - Mar 31: Midterm Critique & Workshop 3 (On Critiquing)

####Week 7 - Apr 7: Check-in

####Week 8 - Apr 14: Individual meetings

####Week 9 - Apr 21: Check-in

####Week 10 - Apr 28: Workshop 4 (Open Source Software)

####Week 11 - May 5: Check-in

####Week 12 - May 12: Final Critique

####Week 13 - May 19: Final documentation submission

##Course Expectations This course is mostly self-directed. As such, it will not contain many direct assignments. When there are expected assignments to be completed, they will be assigned and clearly designated at least 1 week before they are due. Evaluation will primarily come from your ability to:

  • organize and schedule your project
  • identify obstacles and articulate them to the class
  • pursue critical research in your problem space
  • provide critical feedback to your peers' projects

In Person Meetings
On March 3 and April 14 you will have an in-person meeting with either Evelyn or Lauren to discuss your progress and technical hurdles.

Check-ins
On check-in weeks, you will be expected to either sign up for a remote check-in via Skype/GoogleHangout, chat or to send an email with your progress and any questions.

Mandatory Blog
Every student will be required to maintain an online log, blog or website detailing their progress on their project, with weekly detailed updates. This will be required to receive a final grade in the class.

##Check-ins There will be remote check-in weeks on weeks there is no in-person class meeting. You can sign up for an individual Skype/GoogleHangout check-in with either Evelyn or Lauren, you do not need sign up with your main advisor. There will be various time slots during the check-in weeks, sign-up for half hour sessions using the links below:

##Project Updates Add your name and project blog link here!

Students need to document their work online somewhere, on a site of their choice (blog, tumblr, wordpress, wiki, github, etc). A weekly update should be posted by the start of class time each week (regardless of whether there’s an in person meeting or not), including:

  • Updates, milestones achieved
  • Open questions, roadblocks
  • Goals for next week

About

Projects in Creative Programming, Spring 2014

Resources

Readme
Activity
Custom properties

Stars

8 stars

Watchers

3 watching

Forks

12 forks
Report repository

Releases

No releases published

Packages

No packages published

Contributors 5