Princeton University
Computer Science Dept.

Computer Science 333:
Advanced Programming Techniques

Spring 2008

Brian Kernighan

Sat May 10 07:43:48 EDT 2008

Thanks to everyone for really fine presentations. By the way, the somewhat older generation that drifted in and out was mostly community auditors from various of my courses. Most of them have technical backgrounds in computing, and they have often had significant managerial roles as well. When they say, as they did repeatedly, that they are really impressed with your work, it means something.

Now all that's left is to turn it in by 5pm Tuesday 5/13. Here's the final submission information.

Lecture notes:    2/5    2/7    2/12    2/14    2/19    2/21    2/26    2/28    3/4    3/6    3/11    3/25    3/27    4/1    4/3    4/8    4/10    4/15    4/17    4/22    4/24    4/29    5/1   

Assignments:    1     2     3     4     5    

Project:    preliminary description (2/5)     potential external projects (2/11)     more project details (2/19)     design document (2/25)     SVN hints   more hints (3/11)     weekly meetings (3/25)     Project groups     central authentication code (4/5)     project demo information (4/8->4/22)    

Readings:    general bibliography     language tutorials     TPOP RE in Haskell     Perlis's Epigrams on Programming     Ousterhout on scripting languages     original Ajax article     O'Reilly Web 2.0 article     Bentley papers     "Why I Hate Frameworks"     SQL injection how-to     Bjarne Stroustrup interview     "Where are the software engineers of tomorrow?"     Mars Rover, DART     Virology 101    

Old stuff:    Newsgroup     playlist     survey     ed to grep assignment     ed source code     awk patches     network code     registrar code     interface comic     Peter Wendell material     Jonathan Betz     interviewing at Google     Henning on APIs     Bloch on APIs    

Dates: All dates are subject to minor changes. 

	 S  M Tu  W Th  F  S
Feb	                1  2
	 3  4  5  6  7  8  9	first class
	10 11 12 13 14 15 16	assignment 1 due; preliminary project info
	17 18 19 20 21 22 23	assignment 2 due
	24 25 26 27 28 29	assignment 3 due
Mar	                   1
	 2  3  4  5  6  7  8	assignment 4 due
	 9 10 11 12 13 14 15	project proposal due this week
	16 17 18 19 20 21 22	spring break
	23 24 25 26 27 28 29	assignment 5 due; first TA meetings this week
	30 31
Apr	       1  2  3  4  5
	 6  7  8  9 10 11 12	project prototype
	13 14 15 16 17 18 19
	20 21 22 23 24 25 26	alpha test
	27 28 29 30
May	             1  2  3	last class; beta test
	 4  5  6  7  8  9 10	project presentations
	11 12 13 14 15 16 17	Dean's date; project due 5pm
	18 19 20 21 22 23 24

Course Summary

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.

COS 333 is about programming, not about a specific language. The course will assume that you are familiar with C and Java, and will include excursions into C++, Visual Basic, and scripting languages like shells, Awk, Perl, Python and Javascript. There will be significant emphasis on tools, both how to use them and how they are designed and built. The course will use Unix more than Windows, but not exclusively. Students must be comfortable with C and Java programming and with Unix, and able to write modest-sized programs that work. COS 217 is a prerequisite; you can take 333 while taking COS 226 but it's probably not a good idea unless you're a decent programmer.

Syllabus

This syllabus is always subject to change. Each topic will take roughly one week; there's no guarantee that we will cover all of them.

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.

Mechanics

There will be two lectures each week. During the first half of the semester, there will be a modest-sized programming assignment each week, which should take perhaps 5 hours to complete. During the second half of the semester, students will work in groups of 3 or 4 on a project that will involve a significant amount of design and implementation.

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 handed out in class or found on the Web. The books listed in this bibliography are also worth looking at; they cover a wide variety of material related to programming.

Lectures:
Tuesday and Thursday 11:00-12:20, somewhere.

Professor:
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, make an appointment, or just drop in if my door is open, which it usually is.

Teaching Assistants:
      Anirudh Badam (abadam, CS 317, Tue 4-5)
      Jia Deng (jiadeng, CS 316, Wed 3-4)
      Bill Zeller (wzeller, CS 418A, Mon 3-4)

Assignments

Five programming assigments will be assigned during the first half of the term; each is intended to take about five 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 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. You must complete all assignments and project requirements to pass the course.

Project

The second half of the semester will be devoted to a group project; more details will be given soon. The project can be done in whatever combination of languages and techniques makes most sense; one of the goals of the project is to encourage careful tradeoffs among alternatives, and planning of interfaces to minimize dependencies among components. The project is a good place to explore personal interests further than can reasonably be covered in class.

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.

Quizzes

There may well be sporadic unannounced, very short, in-class quizzes to test your understanding and verify your existence. These will be worth perhaps 5-10 percent of the course grade.

Regular class attendance is expected and class participation helps. Frequent absences are grounds for a failing grade regardless of other performance. This means you.

Collaboration Policy for Assignments

(This policy on collaboration in assignments is adapted from the COS 217 web page.) 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 (although you may ask teaching assistants for help in debugging). If you have a question about how to use some language or operating system feature, you can certainly ask your friends or the teaching assistants.

Do not, under any circumstances, copy another person's program for an assignment. Writing code for use by another or using another'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 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 work on your own machine or in a private subdirectory, i.e.: 

	% mkdir cos333
	% chmod 700 cos333

Collaboration Policy for Projects

Projects will often use open source code and other publicly available material as building blocks or as the basis for modification and adaptation. This is permitted and indeed encouraged, but such code must be properly attributed, and the project as a whole must be substantially your own work. Please consult with the instructor if you are uncertain about a proposed course of action.

Project groups are encouraged to share insights and information about how things work, how to get things done, and other aspects of programming knowledge.