![]() |
CSE 142 - Summer 2001 Section AH with Robert Carr |
TA Information
email: rjcarr@cs.washington.edu web: http://www.cs.washington.edu/education/courses/cse142/CurrentQtr/sections/AH/ office hours: Fridays from about 10:30 - 12:00
Important Emails and Contact Info
only TA: cse142-ta@cs.washington.edu only teacher: cse142-instructor@cs.washington.edu both and consultants: cse142-staff@cs.washington.edu section AH (only our section): cse142-section-ah@cs.washington.edu Also ... please subscribe and frequently check the class bulletin board, which is located at ...
uwash.class.cse143.bboard
Instructions on how to set this up if you are unsure can be found here.
Grading
The grading this quarter will be different than you have gotten used to in most other classes. For each homework, there will be two grades. One will be how well your homework functionally works, how well does it follow the specifications, call the 'operation grade' or just 'O'. The other will be based on style and how well you completed the homework ... it is not only thoroghly commenting your code, but also coming up with elegant solutions to the problems. We will call this your 'quality grade' or just 'Q'.Both of these parts, operation and quality, will be given a 0, 1, or 2 grade.
Quizzes
A major part of this course will be (pop) quizzes. Not a major part in referring to the final course grade, but they will be quite frequent (you can assume you will get one every week, even before exams), and will help you keep up with all the new material. Grading for the quizzes will be on a credit/no credit basis.My suggestions for doing well on the quizzes would be to go to every lecture and at least review the notes before every section, if not completing the required textbook reading (which you should be doing anyway). Don't stress out about the quizzes too much, they should be pretty easy, won't count for much of your grade.
Section Material
I started off talking a little about the section. This section has been designated as an 'Experienced Programming' section, but realize that is won't really change too much. Where the difference will be really is the depth that I explain things, and how I will answer more technical questions rather than deflecting them to a place outside of the classroom. But ... be warned that although I have a lot of Java experience (at least hopefully more than you), I haven't done any Java 'hacking' nor do I know all the internals about what is really going on. So, I will do my best to answer all of your questions, but sometimes you may have to steer them towards the professor (and hope he knows the answer).It will be hard to do a review of the material I covered in section because I sort of went all over the place, and you really just had to be there. The only important information was how to read and interpret the Java documentation pages.
A couple of the places to start with these are the docs on the course (Java) classes ...
http://www.cs.washington.edu/education/courses/cse142/CurrentQtr/help/javadocs/index.html
or the complete Java SDK documentation pages ...