MadLily/syllabus

Spring 2016 Syllabus (and lecture slides)

W4111 Spring 2016 Syllabus (Section 002)

See the schedule on the course web site: http://www.cs.columbia.edu/~coms4111/ejones.html

Instructor

• Evan Jones
• ej@evanjones.ca
• Office Hours: After class on Thursday

Office hours

• TA office hours will be in the TA room

Textbook

• Database Management Systems 3rd Edition by Ramakrishnan and Gehrke.

(Not required but may be useful for additional detail)

Prerequisites

• COMS W3134 or W3137 (equivalent courses taken elsewhere are acceptable as well) and
• Fluency in Python or can pick it up during the class
  • basic data structures (e.g., linked lists, trees, hashtables)
  • big O notation
• HTML/javascript will help
• Will expect students to use tools such as ssh to work with machines in the cloud
• You need to get permission from the instructor if you do not have these prerequisites. This course is intended for both Computer Science majors as well as non-majors.

Programming Resources

• See our Java to Python Quick Guide
• Additional resources
  • Java to Python Quick Guide
  • Python tutorial
  • Learn Python in Y Minutes
  • Learn Python The Hard Way
  • Flask documentation
  • Flask Tutorial
  • Jinja Template documentation
  • Jinja Tutorial

Assignment Collaboration Policies

• Homework assignments must be done alone.
  • No collaboration is allowed. Don't do it
• Projects are in teams of 2.
  • Both members will recieve the same grade and should collaborate with each other.
  • Collaboration outside of the team is not allowed. Don't do it
• See Columbia's description of academic honesty

Homework Submission Policy

• Homework is generally due before class (8:40 AM) on the due date, unless indicated otherwise.
• Unless we specify otherwise, students should submit their homework in hard copy rather than electronically. This is a large class and the TAs cannot afford the overhead of printing out electronic homework submissions for grading.
• Auditors: Only students registered for course units may turn in work to be graded.

Grading

Grading Policy

• Homework: 15% equally weighted
• Project 1: 15%
• Project 2: 5%
• Midterm 1: 25% (closed book, 1 two-sided cheat sheet)
• Midterm 2: 40% (closed book, 1 two-sided cheat sheet)

Notes on grading (please read):

• The percentages are subject to change as circumstances dictate.
• Active participation in piazza and/or OH can positively affect your final grade.
• Since exams are the main indicators we have of individual grasp of the material, we reserve the right to adjust final letter grades based on exam performance.
• Work that you submit must be your own (or for two-person projects, the team's). We will run the standard software duplication checkers on submitted assignments.
• Don't cheat. It's not worth it.

Late Days

Homeworks

• You allowed 3 penalty free late days to use throughout the semester for homework only.
• One late day equals one 24 hour period after the due date of the assignment.
• Even 1 minute late equals the use of a late day.
• Once you have used your late days, there will be a 25% penalty for each day an assignment is late.
• You do not need to explictly declare the use of late days; we will assign them to you in a way that is optimal for your grade when different assignments are worth different numbers of points.

Projects

• Same deal as homeworks
• For projects, you are allowed 3 penalty free late days to be used only for projects.
• One late day equals one 24 hour period after the due date of the assignment.
• Even 1 minute late equals the use of a late day.
• Once you have used your late days, there will be a 25% penalty for each day an assignment is late.
• You do not need to explictly declare the use of late days; we will assign them to you in a way that is optimal for your grade when different assignments are worth different numbers of points.
• TEAMS: both members of the team are deducted late days for each day the assignment is late.
  If either member is out of late days, your grade will be deducted as per above.

Additional late day rules

• Late days are nontransferrable between homeworks and projects
• To use a late day for a project, both team partners must have a project grace day available each, and they will both be deducted one project grace day each. If you change team partners and your new partner does not have any project grace days left, then unfortunately you will not be able to use any grace days for the project.

Alternative procedures to submit late homework:

• (Preferred) Bring to any TA's office hours.
• Bring to class.
• (Least preferred) Submit to Eugene Wu's office: 421 Mudd in the DSI space: map

When using late days, note that homeworks tend to get harder later in the course.

Communication

• (Perferred): Piazza
• (Least Preferred): Email course staff. There are too many people in the course for this to be a primary option!
• Announcements will be on website and via emails using courseworks

How to ask for help:

0. Search google and see if it answers your question. Then tell us:
1. What are you trying to do?
2. What steps did you think would work and which have you tried?
3. How did it fail and why do you think it failed (OK to say I don't know why it failed)?
4. What error did it produce?