This page is a course resource for Beth Katz's sections of CS 162 in Spring 2008.
The answers to the Abstract Data Type (ADT) implementation practice and quiz are here.
Warmup problems are questions I write on the board at the beginning of some lectures. They are not graded but cover a topic students should know at that point. They often lead into the day's lecture topic. I did them almost every lecture in Spring 2007. You need to be able to write code on paper without a crutch.
Notes to the class are email notes I've sent to the entire class to reinforce some idea or answer a question. That page archives and organizes all the notes.
Example programs from class are also in /home/grader/katz162/examples. I will update this as we create more examples.
Check out my learning page for more discussion on textbooks and asking questions.
Even if you breezed through CS 161, CS 162 will be more challenging. Plan to spend more time on it.
You need to plan to spend time outside of class for this course. We will go into the lab for structured activities, demos, and lecture. We will not go into the lab to give you time to do your homework.
Note that I expect you to use functions extensively and have good coding style. I don't expect piles of comments, but I want each and every function to have a useful description of its purpose. We'll use the Javadoc format for documentation on some assignments, but simple // comments are fine unless you are told otherwise. Programs at this level are read as much as they are executed. You need to be able to read and understand the code you write. Create it that way rather than making it readable as an afterthought. Eclipse uses the Javadoc comments you write to give you hints about that code; take advantage of that by writing good comments as you create the code.