Compsci 100, Spring 2012, About

Staff

mike image Professor Michael Hewner
  • office: D226 LSRC
  • email: hewner AT cs.duke.edu
  • office hours: Mondays 11-12, Thursdays 1-2, or whenever my door is open
  • phone/IM/etc.: see my homepage
mike image Graduate TA Ruofan Xia
  • office: N006 North Bldg.
  • email: rx51 AT cs.duke.edu
  • office hours: TBA
  • phone: 919-452-5036

UTAs

mike image

Jack Zhang

mike image

Kaitlyn Fang

mike image

Matthew Tse

mike image

Lance Co Ting Keh

mike image

Tori Reynolds

mike image

Scott Cara

mike image

Julian Tigler

mike image

Chris Graybeal

mike image

Andy Ni

mike image

Tyler Nisonoff

mike image

Erick Gonzalez

mike image

Scott Brothers

mike image

Dustin Alin

mike image

Hao Sun

mike image

James Hong

Helper hours for CompSci 100 UTAs are in the The Link. The Link is of the on Lower Level 1 of Perkins Library. The UTA should be near the cluster of chairs between Group Study 7 and Classroom 4.

Map to Perkins
Map of the Link

You can bring code on your laptop or have it accessible (e.g., via Ambient check-in & check-out) so the UTA can use another computer.

Regular Hours

Hours in the Link start Sunday 1/15

Texts

Head First Java (second edition) , Optional, by Kathy Sierra and Bert Bates, O'Reilly, ISBN 978-0596009205

A funny guide to the Java language, which you will mostly use as a reference to get you used to Java in the beginning of the course. It's not very expensive, but if you know Java well, you can get away without it.

Grading

Grading is done on an absolute, but adjustable scale. This means that there is no curve. Anyone earning 90% or more of the total number of points available will receive a grade in the A range (A- to A+); 80% = B, 70% = C, 60% = D. This scale may go down, but it will not go up.

To receive a grade of A or A+ you must exceed expectations. This means you must do everything required extraordinarily well or you must do more than is required and do this well. In other words, to earn an A you must do more than merely meet the requirements, you must go beyond them.

In order to earn an A+ you must do most of the optional assignments and exceed expectations in general.

programming assignments  40%
non-required APTs 10%
required APTs 5%
classwork/prep work 5%
tests (2)  20%
final exam  20%

Attendence/Prep Work/Classwork

We will frequently have activities in class that require participation. For recitation (and occasionally for other classes), we may ask you to do a small amount of work beforehand. The point of this work is to help you learn, so even if you are unable to solve the problem, you should submit the work you have.

If you miss classwork or prep work for one of the allowed reasons, or you feel that your classwork or prep work grade is incorrect, you should email the course TA (not Professor Hewner). If you miss because of illness you must also submit a Short Term Illness Notification Form. You are responsible for discovering that your missed classwork and notifying the TA in a timely fashion.

APTs

APTs are Algorithmic Problem-solving/Programming Testing problems and programs. You'll be given a description of a problem and asked to write code to solve it -- testing the code online and when you're happy with the code submitting it for grading. We don't look at the source code when grading, we run it and test it. However, you should strive to make your code small and beautiful. We will not accept late APT programs this semester. Keeping up with APTs ensures you understand the topics we're discussing in class. You'll have many chances to do extra APTs thus being able to make up for missed submissions. Some APTs are required. You won't be able to make up required APTs, you will have several opportunities to get full credit for the non-required APTs.

Late Programming Assignments

Assignments turned in on time receive no penalty. Assignments turned in up to 72 hours (i.e. 3 days) after their due date incur a 10% penalty. Assignments will not be accepted more than 72 hours late.

Programming assignments will typically due at 8am. That means that if an assignment is listed as being due at "8am on Wednesday" - you really should be finishing it sometime Tuesday night.

If you're having trouble, be sure to see a UTA/TA and preferably the professor in charge of the course as far before the due date as possible. Don't give up, ask for help. Don't give up, ask for help. Don't give up, ask for help.

Individual extensions will be granted for medical reasons (see the Short-term Illness Notification policy) or other circumstances beyond your control that must be presented with an official Dean's excuse. We do not grant extensions after an assignment is due.

If you have personal reasons to ask for an extension, and you do so at least a week in advance, it's possible to get one, so please ask.

Points on assignments will vary. Harder assignments will be worth more than previous assignments, and most assignments will get harder as the semester progresses (harder means takes more time, requires more thought).

Course Policies

Quizzes and Exams taken online or in-class must be your own work, you should not collaborate on them unless you're given explicit permission to do so. This means you don't talk to anyone or look up anything on the web unless you're given instructions otherwise. You will able to bring a small number of notes to the exam.

On programming assignments, you may consult with professors, and TAs/UTAs about any aspect of the assignment. You may consult with other students only in a general way, e.g., about debugging or Java issues, or questions about wording on the assignment. You cannot actively work with someone unless the assignment specifically grants permission to work together with another student. You can ask for hints or help, but if you do you must acknowledge this in your README that you submit with each assignment. Similarly, if anyone looks at your code to offer your help, guidance, or words of encouragement you must acknowledge this in your README.

Consult means you can discuss the programs before writing code, and get help with debugging your program, but you should write your own code. Writing one program and making multiple copies of it is NOT acceptable! For each assignment you are expected to include a list of the people with whom you have consulted (including students, TA's, tutors, professors) as part of your submission. This is required, it's called the README file, and failure to provide it will result in rejection of the assignment as complete (you can resubmit.).

Exams

Tests will be held during the lecture time and in the same room. The final will also be in the same room. See the syllabus page for dates and times.

You will be allowed to take a small number of notes to your exams and the finals. They will not be open book/open notes.