Programming, like composition, is an individual creative process. Individuals must reach their own understanding of the problem and discover a path to its solution. During this time, discussions with friends are encouraged. However, when the time comes to write the code that solves the problem, such discussions are no longer appropriate; the program must be your own work.
Do not, under any circumstances, copy another person's program, comments, README description, or any part of the submitted assignment. This includes character-by-character transliteration of another works (whether inspected visually or copied digitally), but it also includes derivative works (i.e., by renaming variable names or subtlety shifting around statements in order to try to hide that copying has occurrred). You are also not allowed to use other people's code, comments, or results, even when "citing" them -- all work must be your own. Writing code for use by another or using another's code in any form is academic fraud and will be dealt with harshly. You are also responsible for ensuring that the code you write for the assignments is not readable by others.
You should submit your work on an assignment (electronically) before its due time. If you submit your work late, we will give you credit for it on this scale:
We will grant extensions only in the case of illness (with a doctor's note) or extraordinary circumstances. If illness or an extraordinary circumstance will cause you to submit an assignment late, then you should discuss the matter with your instructor as soon as possible. Please plan your work on the assignments so that travel, interviews, athletics, religious holidays, etc. do not cause you to submit it late. A heavy workload is not an extraordinary circumstance.
That said, you are allowed three "free" late days during the semester. You do not need to tell us that you are applying your "late day" -- we'll remove the late penalty at the end of the semester from the assignment that benefits you the most.
We are not permitted to accept work after Dean’s Date, so no submissions of assignments (including Late Days) will be accepted after that date.
All of the code you turn in for this course should have good style. Make sure that your code has proper indentation, descriptive comments, and a comment header at the beginning of each file, which includes your name, userid, and a description of the file.
Because accidents can happen and it is good practice, we require you to use a version control system to maintain your code for this course. We ask that you setup an account with github, gitlab, or bitbucket, web-based hosting service for projects that use the git revision control system.
You must configure these services to use a private code repository. Do NOT under any circumstances make your code public, including after the course is over.
The basic git workflow in the shell (assuming you already have a repo set up):