General Statement on Collaboration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Programming, like composition, is an individual creative process in which you
  must reach your own understanding of the problem and discover a path to its
  solution.  During this time, discussions with others (including the instruc-
  tional staff) are encouraged.  (But see the Gilligan's Island Rule below.)

  However, when the time comes to write code, such discussions are no longer
  appropriate---the program must be your own personal inspiration (although
  you may ask the instructional staff for help in writing and debugging).

  Since code reuse is an important part of programming, you may incorporate
  published code (e.g., from text books or the net) in your programs, provided
  you give proper attribution and THE BULK OF THE CODE SUBMITTED IS YOUR OWN.

  DO NOT UNDER ANY CIRCUMSTANCES COPY ANOTHER PERSON'S CODE---to do so is a
  clear violation of ethical/academic standards that, when discovered, will be
  referred to the Executive Committee of Yale College for disciplinary action.
  Modifying code to conceal copying only compounds the offense.

The Gilligan's Island Rule
~~~~~~~~~~~~~~~~~~~~~~~~~~
  When discussing an assignment (either programming or nonprogramming) with
  other students, you may write on a board or a piece of paper, but you may not
  take any written or electronic record away from the discussion.  Moreover,
  you must engage in a full hour of mind-numbing activity (such as watching
  back-to-back episodes of Gilligan's Island) before you work on the assignment
  again.  This will ensure that you can reconstruct what you learned from the
  discussion, by yourself, using your own brain.

								CS-223-01/08/09