Computer Science 333:
Thanks to everyone for really fine presentations. By the way, our non-student visitors included present and former community auditors and others from a variety of places both on and off campus. Most of them have technical backgrounds in computing, and often have had significant managerial roles as well. When they tell me, as they did repeatedly, that they are really impressed with your work, it means something.
Now the final bit: here are instructions for final submission by 5 PM on Tuesday, May 14. These echo what was said earlier, but with some minor revisions, so please read carefully.
If you still have a borrowed book or equipment, please return it by Dean's Date as well. Thanks.
Lecture notes: 2/5 2/7 2/7 2/12 2/14 2/19 2/21 2/26 2/28 3/5 3/7 Carter Cleveland 3/12 3/14 3/26 3/28 Peter Wendell 4/2 4/4 4/4-9 4/9-11 4/11-16 4/18 Brad Smith 4/23 4/25 4/30 Jonathan Betz 5/2
Assignments:   0     1     2     3     4
Project: preliminary description (2/5) previous projects (2/5) comments from previous projects (2/5) [2/27] project ideas from around the university project slides from 2/7 design document information (2/21) Git and SVN Project groups and TA assignments The week after break Project demo and submission info (4/15) Advice on demos Project demo schedule
Readings: general bibliography language tutorials
Old stuff: Piazza playlist survey TA office hours refgrep for Linux regular expresssion crossword Netflix culture slides Stanford startup course Flask demo code CAS authentication SQL injection attacks How SQLite3 is tested The Mother of All Demos Draft C++ chapters McIlroy Virology 101 Hamming You and your research Towers of Babel
Dates: All dates are subject to minor changes.
Su Mo Tu We Th Fr Sa Feb 1 2 3 4 5 6 7 8 9 first class 10 11 12 13 14 15 16 assignment 0 due; assignment 1 due 17 18 19 20 21 22 23 assignment 2 due 24 25 26 27 28 Mar 1 2 assignment 3 due 3 4 5 6 7 8 9 assignment 4 due 10 11 12 13 14 15 16 design doc due 3/17 17 18 19 20 21 22 23 spring break 24 25 26 27 28 29 30 weekly TA meetings start this week 31 Apr 1 2 3 4 5 6 7 8 9 10 11 12 13 project prototype 14 15 16 17 18 19 20 21 22 23 24 25 26 27 alpha test 28 29 30 May 1 2 3 4 last class; beta test 5 6 7 8 9 10 11 demo days 12 13 14 15 16 17 18 Dean's date: projects due by 5pm 19 20 21 22 23 24 25 26 27 28 29 30 31
This is a course about the practice of programming, an attempt to expose students to the development of real programs. Programming is more than just writing code. Programmers must also assess tradeoffs, choose among design alternatives, debug and test, improve performance, and maintain software written by themselves and others. At the same time, they must be concerned with compatibility, robustness, and reliability, while meeting specifications. Students will have the opportunity to develop these skills by working on their own code and in group projects.
During the first half of the semester, there will be a programming assignment each week, which should take perhaps 5-6 hours to complete. During the second half of the semester, students will work in groups of 3 to 5 on a project that will involve a substantial amount of design and implementation.
This is meant to be more than a laundry list, however. Each section will also discuss issues of design, implementation, testing, performance, portability, and other software engineering concerns, and these will also be part of the programming assignments. With luck there will be a couple of guest lecturers as well.
There is one required text: The Practice of Programming, by Kernighan and Pike; you should also know basic Unix tools and usage as described in, for example, The Unix Programming Environment. Other readings will be posted. The books listed in this bibliography are also worth looking at; they cover a wide variety of material related to programming.
Tuesday and Thursday 11:00-12:20, Peyton 145
Brian Kernighan, 311 CS Building, 609-258-2089, bwk at cs.princeton.edu. Depending on class size, I may set up regular office hours once things get rolling; alternatively, send mail to make an appointment, or just drop in if my door is open, which it usually is.
Teaching Assistants and office hours:
Chris Moretti (cmoretti@), CS 206, Friday 3-4 and right after lecture
Hao Wu (haow@), CS 223, Tuesday 3-4
Xin Jin (xinjin@), CS 316, Thursday 3-4
Half a dozen programming exercises will be assigned during the first half of the term; each is intended to take about 5-6 hours, but is sure to take longer unless you are careful.
Assignments are together worth about 30-35 percent of the course
grade. Assignments are generally due by
midnight on Fridays
unless there are extraordinary circumstances. For the record,
extracurricular activities and heavy workloads in other classes don't
count as "extraordinary", no matter how unexpected or important or
time-consuming. Assignments will generally be posted on Tuesday and due
at midnight on Friday 10 days later. This leaves enough time that we
will not be able to grant extensions except in case of documented medical
or other serious issues.
If you submit your work late,
If you submit your work late,we will give you credit for it on this scale:
The project will have frequent checkpoints along the way for which you will have to prepare status reports, preliminary designs, and the like. There will be a public presentation and demo at the end, a written writeup, and submission of a system for testing and evaluation. All of these are graded.
The project will be worth about 60-65 percent of the course grade; it will be shared equally among group members, with the possibility of negative adjustments for members who fail to contribute their fair share.
You must complete all assignments and project requirements to pass the course. Furthermore, the class is so large that we don't have the resources to nag and make special arrangements; you are responsible for meeting all the requirements without reminders.
Regular class attendance is required and class participation helps. Unexcused absences are grounds for a failing grade regardless of other performance. This means you.
Do not, under any circumstances, copy another person's program for an assignment. Writing code for use by another person or using another person's code in any form violates the University's academic regulations.
Examples of unacceptable behavior for assignments include:
The program you turn in must be your work. You may get help from the instructor or a TA after you have started writing code, but not from other students. Computer science assignments are not like physics or math problem sets: there is no single right answer. Each student is expected to come up with his or her own individual solution.
If you plan to do something that you are not absolutely sure is legal, ask first. Ignorance of this policy will not be accepted as an excuse for your actions.
You are responsible for ensuring that your files are not readable by your classmates. We recommend doing your COS 333 assignments on your own machine or in a private subdirectory, i.e.:
% mkdir cos333 % chmod 700 cos333
Project groups are encouraged to share insights and information about how things work, how to get things done, and other aspects of programming knowledge.