Welcome to the Spring 2005 session of Grinnell College's CSC 152, Fundamentals of Computer Science II, which is described relatively well in the official blurb. My own take on this course is that we'll be expanding your knowledge of Computer Science and of computer programming, while emphasizing the development and analysis of common data structures and algorithms. We will be using Java as our development language. As in all Grinnell callses, we'll also be working on general thinking and work skills.
In an attempt to provide up-to-date information, and to spare a few
trees, I am making this as much of a
paperless course as
Warning! Experience shows that CSC152 is a significantly more time-consuming and accelerated course than CSC151.
Meets: MTuWF 11:00-11:50 a.m., Science 2417
Instructor: Samuel A. Rebelsky, Science 2427. Office hours: MTuWTh 1:15-2:05. I also tend to follow an open door policy: Feel free to stop by when my door is open or to make an appointment for another time. Check my schedule for more details.
firstname.lastname@example.org. Hours TBD.
My grading policy is always subject to change.
The final examination for this course is optional. It can be used as a makeup for one examination. Like the other examinations, it will be a take-home examination.
My experience shows that students who turn in work late learn significantly less than students who turn material in on time. (I'm not sure about cause and effect.) Hence, I strongly discourage late assignments. Unless prior arrangements have been made, assignments are due within five minutes of the start of class. After that they are considered late. Late assignments are penalized one letter grade per day late (or fraction thereof).
Labs: While you won't do as many labs as you did in CS151 (if you took CS151), Labs are for your benefit, not mine, so I won't be grading most of them (other than to check that you completed them).
Participation: As I suggest in my statement on teaching and learning, I don't think you learn the material as well if you don't participate actively in the class. Hence, a portion of your grade is based on participation. Students who miss no more than two classes and who regularly answer questions or make comments in class receive 90 for participation. Missing 3-5 classes results in a 10 point penalty. Missing 6-8 classes results in a 25 point penalty. Missing 9 or more classes results in a 50 point penalty. Particularly good answers, comments, and questions result in bonus points for participation.
The Project: Over the past few semesters, I've found that building a large class project gives students a particularly beneficial (if painful) experience. We will need to pick a project in the next few weeks.
Extra Credit: I will occasionally give you quizzes to ensure that you're keeping up with the reading. Correct answers on the quizzes will give you some amount of extra credit.
Throughout the term, I may suggest other forms of extra credit.
My experience suggests that otherwise intelligent people sometimes
have great difficulty with the kind of thought necessary in CSC152.
It strikes me as unfair to penalize students because their brains don't
work right for CS. Hence, if you make a
best faith effort, I will
give you at least a B-. Such an effort includes attending at least 95%
of the classes (you can miss no more than two), doing the readings before
class, participating in class, attempting every homework assignment,
and spending eight hours on each take-home exam.
Rebelsky, Samuel (2005). Espresso: A Concentrated Introduction to Java. Online resource available at
I am attempting to write a lab-based introduction to Java for this class. We'll see how it goes.
Rebelsky, Samuel (2005). The TAO of Java. Online resource available at
I am also attempting to write a series of labs that cover the key elements of this course (types, algorithms, objects). We'll see how it goes.
Rebelsky, Samuel (2005). The CSC152 2005S Web Site. Online resource available at
My online resources for the course.
I usually create these pages
on the fly, which means that I rarely
proofread them and they may contain bad grammar and incorrect details.
It also means that I tend to update them regularly (see the history for
more details). Feel free to contact me with any suggestions for changes.
This document was generated by
Siteweaver on Fri May 13 13:28:27 2005.
The source to the document was last modified on Fri May 13 13:28:22 2005.
This document may be found at