Earning a Grade: A lot of you have one burning question on your mind as you start your college career:

How am I going to get an A in this course?

We have some news for you: you are in college now, and in college, it really is about learning something and not (just) getting a grade. As a matter of fact, if you are taking a course and the A comes easy, you are either cheating yourself or you are allowing the instructor to cheat you.

Here is the positive take-away from this section: College is your last chance to learn how to learn by yourself, without pressure from parents, teachers, or peers. You want to learn that, because the quality of your life depends on it. Your life. Nothing more, nothing less.

Naturally, we understand that you want some feedback, both in terms of specific corrections and in terms of a grade. You want feedback so that you can improve your learning process. And we will give you that feedback. It is our end of the bargain. Your end is to demonstrate that you actually use the methods and tools for learning that work best in our experiemce. After all, you don't want to waste your time, and we don't want to waste ours either.

People: For this course you will encounter two (later, possibly three) kinds of people:

Instructors: (only one this semester)

Bryan Chadwick

Teaching Assistants: (only one this semester)

Abhishek Chaubey

TAs teach labs, supervise the grading of homework sets, hold office hours, and occasionally substitute in lectures. In general, they are apprentice teachers and are here to learn how to run a course.

Tutors: (only two this semester)

Matt Horan, Mike Reed

Tutors will help in the grading of homework sets, hold office hours, and help out in the Labs.

Class: Class consists of lectures and lab meetings (CSU 212).

Lecture: Only one section:

Section	Location	Instructor
MWTh 4:35 pm	Ryder 429	Chadwick

You must make an effort to attend this section on a regular basis.

Labs: The course also has a lab section of CSU 212. The labs will start on Thursday, January 10th (11:45 am).

You will attend the lab section on a weekly basis. The purpose of labs is to give you some hands-on experience with the actual tools, and to explain some of the principles from lecture with hands-on examples.

Computing Environment: We will use DrScheme v371, a programming environment for the Scheme programming language, some dialects of Java, Algol 60, OCAML, and a few others. For CSU 211, we will stick to the HtDP teaching languages plus teachpacks. DrScheme is installed on the CCS computers. It is also freely available on the Web (see tabs on the left of this page) in case you wish install it on your own computer.

DrScheme runs on most popular platforms (Windows 2000/XP, Mac OS X, Linux, and other unix systems). Programs written in DrScheme have the same behavior on all platforms. You therefore do not need to worry what kind of machine you use when you run DrScheme programs.

Problem Sets: The purpose of the problem sets is to prepare you for the exam.

There will be weekly problem sets. Some problems are drawn from HtDP, the textbook; others are constructed for this instance of CSU 211. We will grade some but not all problems from each set (picked randomly after the due date).

We will drop the homework grade with the worst impact on your final grade from consideration for the final grade. Thus, if you choose to skip an assignment set or if you just don't get it one week, nothing is lost. The story is different for the second or third or ... time.

You may only collaborate on problem sets with your partner (see below). You must acknowledge your collaborator/partner on your cover page. Any other collaboration is cheating; we will report cases to the University Administration.

Pair Programming: You must work on your problem sets (2 - 11) in pairs. Your partner will be in your lab, and your lab TA will assign you a partner. Every few weeks, you will get a new partner.

Pair programming means that you and your partner work on the problem sets jointly. You read them together and you work on the solutions together. One of the lab's purposes is to teach you how to work in pairs effectively; indeed, pairs are provably more effective than individuals in programming. The rough idea is this: One of you plays pilot, the other co-pilot. The pilot works on the keyboard and explains aloud what is going on; it is the co-pilot's responsibility to question everything. After a problem is solved to the satisfaction of both, you must switch roles.

Exams and Quizzes: We will have two hour exams to assess your progress:

• TBD... February 2008
• TBD... March 2008

We will announce the date, time, and locations here (and in class) once they have been determined.

The exams will test material similar to that assigned in weekly homeworks. You will take the exams by yourself. Collaboration is not tolerated! If you can solve every homework problem on your own, the exams will be easy. If not, you will have a difficult time.

Grades: You will get a gpa for your homework and your exams. You must have both a passing homework gpa and a passing gpa to pass the course. For the final grade, we will assign a weight of 40% to the homework grade, a weight of 55% to the two exams. The remaining 5% are up to the instructors' whim (TBD).