Class 55: Course Evaluation

Held Wednesday, May 10, 2000

Overview

Today we'll use the class period to give you a chance to evaluate the class.

Question 55 for today's class: What were the best aspects of this class? The worst?

Question 56 for Friday's class: What is the most important thing you've learned so far in CS105?

Notes

• Please attend class on Friday.
• Note that I've brought food to class today not to bribe you, but to provide incentive for you to attend. (In CS152 we had a ``carrot or stick'' discussion, so I'm using the ``carrot'' approach.)
• I will email you grades next Wednesday. That should give you a few days to argue for changes (up or down).

Contents

• Evaluations
• Subject Matter

Summary

Evaluations

• We'll spend today and Friday working on evaluation. I expect that you will attend both classes.
• Today, you will complete written evaluations of the course.
• Friday, we'll review what we've learned in the course and consider ways to improve the course.
• There are two evaluation forms:
  • An experimental institutional numeric evaluation form. The institution eventually hopes to make this a formal tool that is used in faculty reviews (for tenure, promotion, and raises).
  • A course-specific narrative evaluation form. I use this to improve the course.
• Fill out the institutional review form first. Please make sure to comment on each of the section.
• When you have filled out the institutional form, pick up a copy of the course-specific form. When you are done filling that out, you may leave.
• I do not read the forms until after I've turned in grades.

Subject Matter

• The institutional evaluation forms ask a number of questions about the ``subject matter of the course''.
• Hence, it is important for me that you understand my perspective on this issue.
• At one level, this is a course about the social impact of computing. From that perspective, my primary goal was to help you understand some of the core social computing issues.
• This is also a course about the technology of computing. From that perspective, my primary goal was to give you some experience in ``thinking algorithmically''. I also wanted you to have some understanding of what is involved in writing programs.
• However, I also expect the course to contribute to your overall thinking skills. From that perspective, my primary goal was to give you experience (and, eventually some comfort) in reading and understanding technical writings. (From your success in understanding Redcode, I feel that I was at least partially successful.) As in all Grinnell courses, I also wanted to challenge you to apply (and, hopefully, enhance) your skills in discussion and critical reading.