1. Be very familiar with these instructions and follow them at all times. In a course this size it is important for it to be administered with great attention to detail. Read these instructions several times in the first few weeks. If anything is unclear, ask. This page may be found in Oncourse > C212 Haynes team > Resources > Responsibilities and Procedures.
2. If there is anything that might be important and which is either urgent or better to discuss in person than by email, try calling my office, 855-3376, or stopping by, and if I'm not there, please do not hesitate to call me at home, 336-3221. I work at home a good deal.
3. Be familiar with all the course's Oncourse material. It is recommended that you not disable email notification of announcements sent by Oncourse, and if you do, check Oncourse several times a week.
4. Understand the course material and how it is being taught. In some cases this may necessitate attending lectures. Come whenever you feel the need. And master the assigned material. Even if you think you know the programming language well, you probably need to learn more to avoid confusing students. (I find every semester that I do!) If something is unclear to you, ask.
5. You must be prepared to help students with the homework assignments, so you should solve all assignment problems, or at least carefully study a provided solution, before the lab devoted to an assignment.
6. When assisting students with problems, your job is to guide them to their own solutions. Avoid giving them explicit code to patch their bugs.
7. Attend the weekly teaching team organizational meeting.
8. Hold scheduled office hours (at least two hours per week for an AI, one for a UI).
9. Arrive several minutes early and do not leave early for assigned labs and office hours. If you can't be there for some reason, try to find a substitute and inform the instructor. If you can't do that, inform the office and the instructor so further attempts can be, and in the worst case a notice can be posted so students aren't left waiting for you.
10. Assist with grading of tests and the final as assigned. Assist with conducting special help sessions prior to the final exam.
11. Read and respond to email from the instructor in a timely fashion (generally every week day). You can email all the course instructors via the team email distribution list below. Email chaynes if it doesn't concern the rest of the team.
12. Keep your email well within quota. If you go over quota, I get an email message every time anything is mailed to the team.
13. Read the course's Oncourse discussion and post responses to student questions. If you are assigned this as a special responsibility for a week, read it at least once a day, including weekends, and post replies to any questions that have not been satisfactorily answered. If you do not know the answer to a question, then find it out!
14. Treat all students professionally, equitably, and with respect.
15. Never confront a student with an accusation of academic dishonesty. Instead, bring any such suspicions to my attention immediately.
16. Do not make policy, such as excusing students from an assignment, test, or anything on the course policy web page. If you think a student deserves an exception to the policy, refer them to me.
17. Only give constructive feedback in grading and office hours: avoid comments that might be interpreted as insulting or judgmental.
18. Do not perform tutoring for this course for money or other tangible compensation.
19. Obtain a desk copy of the text from the undergraduate secretary in LH225.
20. If you have office hours scheduled in LH112, you need to go to the LH215 office and fill out a Lindley Hall Access Request Form to get on the card access list to the room. Sue Menzel schedules the room: see  http://www.cs.indiana.edu/~menzel/lh112.html, and email menzel@cs.indiana.edu to make reservations. It is good to have some after-5pm office hours on LH112 offered by the team, but during normal hours they can be in the LH230 suite (which has a PC in the SW corner: let me know if you want access to it), or in any suitable office you have access to.
21. If you are using the LH230 suite, when informed that you have an account on its PC, install course software per the instructions for students on personal machines (see the Oncourse Resources page).

1. At least two days before your first lab, be sure you have the projector code for your lab (obtained by emailing stcsite@indiana.edu ) and go there to be sure you know how to find it, run the projector, login to the computer, and anything else you need to know about the physical setup.
2. Get whiteboard markers for use in labs from the office.
3. Be sure you are clear about what to do in any lab your are responsible for leading.
4. When addressing the whole lab, speak very slowly and loudly enough for all to hear. Force students to use pair programming when called for by an assignment, except for one person if the number is odd, or groups of three if allowed by the assignment.
5. When helping a pair, there is a strong tendency to address yourself to the driver (student at the keyboard). This is very bad, as it reinforces the strong tendency for the driver to take the more active role. Talk equally to both, erring if anything on the navigator's side.

1. Assignments and quizzes should be graded, recorded, and returned in lab the following week.
2. Mark up papers using a pen that is not black and dark enough so your marks show up well and copy well.
3. Graded materials that are not picked up in lab should be returned to me at the next team meeting.
4. If you have graded an assignment for the whole class, place graded materials in the course box in the mailroom in appropriate manila folders for each lab, and email the team to let everyone know they're there. Others pick them up before lab and leave the folders in the box for future use. When you have finished grading a group assignment, copy them using the CS dept copier so each team member gets the original or a copy. You can borrow the department copy card from the CS office receptionist.
5. When you've finished grading a quiz, sort them by lab and put them in my mailroom box in an envelope and send me email so I know when they're there. Ideally this will be by the morning of the first class of the week, latest early morning of the second class, for return in labs that week. I like to see what kind of mistakes the students are making and how you're interpreting the grading standard. I'll put them in the class box, with separate folders for each lab, when I'm done and email everyone so you can pick them up.
6. Keep all grading and roster materials confidential. Never leave them lying around where others may see them. If they are no longer needed, shred them. (There is a big shrewder in the department's workroom.)
7. Solutions of assignments are posted shortly after they are due. For some more complex assignments we may use one of the best student solutions. For others, unless the instructor provides a solution, whoever is assigned to grade an assignment should prepare a sample solution as soon as the assignment is known (generally at the weekly meeting), and send it to the instructor asap, before the labs. It is important that you know a correct solution so you can advise and grade properly.
8. You can download all submissions for a given assignment in one zip file using Oncourse. If the course does not show up as an Oncourse worksite for you, email me right away.

9. When grading the first assignment, if a student is not in the OnCourse gradebook, add the student and send him/her email, copying me, saying that students should not submit material unless registered. (They may not have had a chance to register yet, in which case we don't want them to loose the grade, but more likely they are unregistered auditors violating the auditing policy.)

10. Handins are not returned to students. Return physical handins to the instructor in an envelope with the handin date.

11. We never curve harder than the standard 90% correct A, and so on, but we usually curve higher. Sometimes considerably higher. On the first quiz if they're generally very disappointing, I'd still give at least 10% As, 20% Bs, 40% Cs, 20% Ds, and 10% Fs. Probably somewhat higher than that. We want to get their attention without having half the class drop (typically about 1/4 drop anyway). The final course curve, after most of those who don't belong in the course have dropped, is much higher than that, with more Bs than anything else and very few Ds or Fs.

12. Storing files with student data: University policy requires that any files containing student data be stored only temporarily (say at most a few days) on machines whose security is not maintained to their professional standards, which includes all personal machines. Reasonable security procedures must be used to protect such temporary data. For longer term storage of data, use a single directory with all privileges restricted to you ( chmod 700 .)  in your account on a departmental unix machine. Delete this directory shortly after the end of the semester.

Course specific: C212:

1. Team email distribution list 212-team@cs.indiana.edu

2. For detailed grading instructions, including information on our automated grading tools, see Oncourse > C212 Haynes team > Resources > Grading