CSC 195 2014S, Class 14: Wrapup
===============================

_Overview_

* Preliminaries.
    * Admin.
    * Questions.
* Silly demo.
* Debrief on the course.
* Evaluation forms.

Preliminaries
-------------

### Admin

* Have a great summer.
* If you should choose to partake of block party, please partake responsibly.
* Everyone passes, even MSZ

### Questions

Silly demo
----------

GameManager.prototype.addRandomTile

Debrief on the course
---------------------

Three goals for the course

* Prepare Sam's summer research students (or subset thereof)
* Learn some languages related to image making
* Web site development

Questions

Knowing then what you know now, would you still take this course?

* Probably
* But not everyone

Things that were really successful?

* Building on to the original "build a Web site" assignment.
    * Should probably be formalized.
* Range of different languages and things we learned.  Cover a large things
  that are useful.
    * A bit of familiarity with languages
    * We know we can probably teach ourselves these things, but it gave
      us incentive to do so
* Review of student work.
    * Comments in class
    * Outside of class
* Open-ended assignments was helpful because you could explore different
  options.  Didn't need to accomplish a particular goal.
    * But some people need structured questions
    * Sam should give choices - Here's something for those of you who
      need structure; Here's the general thing for those who don't
* GitHub is likely to be useful.
    * education.github.com probably lets you sign up for a private account

Things that were less successful?

* 8 a.m.
* No food.  Sam classes always have food.
* Need more organization.  
    * GitHub repo earlier.
    * Assignments posted in easy-to-find locations.
    * Actual readings.
    * Etc.

Knowing what you know now, how would you structure the class
differently in terms of topics?

* Maybe do D3, a Javascript data visualization stuff language
  (Data-Driven Documents)
* More database.  Maybe earlier.
* Separate Processing and Web development courses
* Drop Postscript or at least show us cool things we can do.
* Disect a Web site and then rebuild and then discuss the IP (intellectual
  property, not Internet protocol) issues of having done so

Other changes you would make?

* Some large group assignment that involves branching and such.
* Emphasize portfolio building.
* Competition with a pitch.
* Capstone project.
* More lectures (or less lectures, more reading)

Evaluation forms
----------------