// APS101, Winter 2009: Lecture 16 (Feb. 12)
//
// The official marks for A1 and the Midterm have been posted on Blackboard.
// Take a look at the A1 solution, and the tester class (available on the course website).
// Also, take a look at the Midterm solutions (see Blackboard announcement for the link).
//
// This is the last lecture before Reading Week. 
// (there will be no lectures/tutorials/labs during reading week). 
//
// The Assignment 2 description will be posted soon. Try to get started on it early. 
//
// NOTES ON ASSIGNMENT 1
//
// 1) Make sure to follow the assignment specifications exactly.
//   (i.e. spell all method names correctly, and make sure to have the right 
//    number, type, and order of parameters for all methods). 
//
// 2) For methods like carInfo and driverInfo (i.e. toString() methods), make sure to
//    follow the format given. Even if you're off by just one character (such as " "),
//    the resulting String value is incorrect.
//
// 3) For the sign-off statement, a lot of you handed in files with extensions like .docx
//    or .odt. In the future, please keep the sign-off file as a .txt file (i.e. "signoff.txt").

// NOTES ON THE MIDTERM
//
// - Overall, the avergage was quite high (for a 1st year Computer Programming midterm).
//
// - Suprisingly, Q3 was not the worst question. On average, the worst marks were on Q2. 
//   This means that you guys need more practice writing your own classes ON PAPER.
//
// - The problem with Q3 was that it was confusing, because the class, variable, and method names
//   were not descriptive at all. So, when you're writing your own programs, make sure to
//   have descriptive class/variable/method names (otherwise your code will look like Q3!). 
//
// HAVE A GREAT READING WEEK!