Top Banner
Practical advice on being a TA Jessica Su
63

Practical advice on being a TA - Stanford Computer Science

Dec 10, 2021

Download

Documents

dariahiddleston
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Practical advice on being a TA - Stanford Computer Science

Practical advice on being a TA

Jessica Su

Page 2: Practical advice on being a TA - Stanford Computer Science

About me•Have been a TA nine times for six different professors

•CS 161 (Design and Analysis of Algorithms), five times

•CS 246 (Mining Massive Data Sets), twice

•CS 224W (Social and Information Network Analysis)

•MS&E 111 (Intro to Optimization)

•Taught CS 161 in the summer of 2016

•Was head TA for CS 161 and CS 246

•Won the CS department's outstanding TA bonus in Winter 2017, Spring 2017, Fall 2017, and Winter 2018

Page 3: Practical advice on being a TA - Stanford Computer Science

About teachingFront-end work Back-end work

Office hours

Piazza

Lecturing

Homework design

Lecture design

Grading

Page 4: Practical advice on being a TA - Stanford Computer Science

About teachingFront-end work Back-end work

Office hours

Piazza

Lecturing

Homework design

Lecture design

Grading

Page 5: Practical advice on being a TA - Stanford Computer Science

Prepare for office hours

Page 6: Practical advice on being a TA - Stanford Computer Science

Prepare for office hours

Read the solution set

Page 7: Practical advice on being a TA - Stanford Computer Science

Prepare for office hours

Read the solution setWatch the lectures

Page 8: Practical advice on being a TA - Stanford Computer Science

Prepare for office hours

Read the solution setWatch the lectures

Ask if you don't understand something (the solution set might be wrong)

Page 9: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Page 10: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Use QueueStatus

Page 11: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Use QueueStatusStudents should only get in the queue once every two hours

Page 12: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Use QueueStatusStudents should only get in the queue once every two hoursStudents in the queue get priority over students not in the queue

Page 13: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Use QueueStatusStudents should only get in the queue once every two hoursStudents in the queue get priority over students not in the queueLimit students to 10 minutes each (when the queue is too long)

Page 14: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Have several people staff the same office hours

Page 15: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Have several people staff the same office hoursSeveral people = 1 TA per 15 students

Page 16: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Have several people staff the same office hoursSeveral people = 1 TA per 15 students

DO NOT: Hold additional office hours slots

Page 17: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Have several people staff the same office hoursSeveral people = 1 TA per 15 students

DO NOT: Hold additional office hours slots(the same students will come to each one)

Page 18: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Have several people staff the same office hoursSeveral people = 1 TA per 15 students

DO NOT: Hold additional office hours slots(the same students will come to each one)

DO NOT: Hold group office hours

Page 19: Practical advice on being a TA - Stanford Computer Science

Common problemsToo many people in office hours

Have several people staff the same office hoursSeveral people = 1 TA per 15 students

DO NOT: Hold additional office hours slots(the same students will come to each one)

DO NOT: Hold group office hours(you will give away the answer)

Page 20: Practical advice on being a TA - Stanford Computer Science

Common problemsDon't know how to answer a question

Page 21: Practical advice on being a TA - Stanford Computer Science

Common problemsDon't know how to answer a question

Say "I don't know, but I'll check with people and get back to you"

Page 22: Practical advice on being a TA - Stanford Computer Science

Common problemsDon't know how to answer a question

Say "I don't know, but I'll check with people and get back to you"

Email them no later than 1 hour after office hours

Page 23: Practical advice on being a TA - Stanford Computer Science

Common problemsDon't know how to answer a question

Say "I don't know, but I'll check with people and get back to you"

Email them no later than 1 hour after office hours

If the solution sets are wrong or incomplete, update the solution sets

Page 24: Practical advice on being a TA - Stanford Computer Science

Common problemsAccidentally misinformed a student

Page 25: Practical advice on being a TA - Stanford Computer Science

Common problemsAccidentally misinformed a student

Email the student and correct yourself

Page 26: Practical advice on being a TA - Stanford Computer Science

Common problemsAccidentally misinformed a student

Email the student and correct yourself

If it was a large group of students, you can post on Piazza

Page 27: Practical advice on being a TA - Stanford Computer Science

About teachingFront-end work Back-end work

Office hours

Piazza

Lecturing

Homework design

Lecture design

Grading

Page 28: Practical advice on being a TA - Stanford Computer Science

1) Be nice

Piazza

Page 29: Practical advice on being a TA - Stanford Computer Science

1) Be nice2) Answer quickly

All posts should be answered within 24 hoursMost posts should be answered within 15 minutes

Piazza

Page 30: Practical advice on being a TA - Stanford Computer Science

1) Be nice2) Answer quickly

All posts should be answered within 24 hoursMost posts should be answered within 15 minutes

3) Try to be on Piazza duty the day after your office hours

That way, you'll already know how to answer all the questions

Piazza

Page 31: Practical advice on being a TA - Stanford Computer Science

About teachingFront-end work Back-end work

Office hours

Piazza

Lecturing

Homework design

Lecture design

Grading

Page 32: Practical advice on being a TA - Stanford Computer Science

GradingGrading should be fair and consistent

Page 33: Practical advice on being a TA - Stanford Computer Science

GradingGrading should be fair and consistent

Ideally, students understand why they lost points and agree that the deduction was fair

Page 34: Practical advice on being a TA - Stanford Computer Science

GradingGrading should be fair and consistent

Ideally, students understand why they lost points and agree that the deduction was fair

Best practices:Say what the student had to do to receive full credit

Page 35: Practical advice on being a TA - Stanford Computer Science

GradingGrading should be fair and consistent

Ideally, students understand why they lost points and agree that the deduction was fair

Best practices:Say what the student had to do to receive full credit

Always leave a comment when taking off points

Page 36: Practical advice on being a TA - Stanford Computer Science

Regrade requestsBest practices:

Page 37: Practical advice on being a TA - Stanford Computer Science

Regrade requestsBest practices:

Only give back points if there was an error in your grading

Page 38: Practical advice on being a TA - Stanford Computer Science

Regrade requestsBest practices:

Only give back points if there was an error in your grading

If you give points to one person, you have to give back points to everyone else who had the same answer

Page 39: Practical advice on being a TA - Stanford Computer Science

About teachingFront-end work Back-end work

Office hours

Piazza

Lecturing

Homework design

Lecture design

Grading

Page 40: Practical advice on being a TA - Stanford Computer Science

Homework design

1) Design the problem

2) Peer review

3) Preflighting

Page 41: Practical advice on being a TA - Stanford Computer Science

Homework design

1) Design the problem

2) Peer review

3) Preflighting

Problem should have exactly one interpretation

Page 42: Practical advice on being a TA - Stanford Computer Science

Homework design

1) Design the problem

2) Peer review

3) Preflighting

Problem should have exactly one interpretationIdeally, there is only one right answer

Page 43: Practical advice on being a TA - Stanford Computer Science

Homework design

1) Design the problem

2) Peer review

3) Preflighting

Problem should have exactly one interpretationIdeally, there is only one right answer

Is this a good/educational problem?

Page 44: Practical advice on being a TA - Stanford Computer Science

Homework design

1) Design the problem

2) Peer review

3) Preflighting

Problem should have exactly one interpretationIdeally, there is only one right answer

Is this a good/educational problem?Are there any errors?

Page 45: Practical advice on being a TA - Stanford Computer Science

Homework design

1) Design the problem

2) Peer review

3) Preflighting

Problem should have exactly one interpretationIdeally, there is only one right answer

Is this a good/educational problem?Are there any errors?

Have three TAs solve the problem to make sure there are no errors or ambiguities

Page 46: Practical advice on being a TA - Stanford Computer Science

What if there is an error in a problem set?

Have a bug bounty policy

Page 47: Practical advice on being a TA - Stanford Computer Science

What if there is an error in a problem set?

Have a bug bounty policyStudents get extra credit for reporting errors

Page 48: Practical advice on being a TA - Stanford Computer Science

What if there is an error in a problem set?

Have a bug bounty policyStudents get extra credit for reporting errors

Rewards good students

Page 49: Practical advice on being a TA - Stanford Computer Science

What if there is an error in a problem set?

Have a bug bounty policyStudents get extra credit for reporting errors

Rewards good students

Makes people less mad when they find errors

Page 50: Practical advice on being a TA - Stanford Computer Science

What if there is an error in a problem set?

Have a bug bounty policyStudents get extra credit for reporting errors

Rewards good students

Makes people less mad when they find errors

Errors get corrected fast

Page 51: Practical advice on being a TA - Stanford Computer Science

About teachingFront-end work Back-end work

Office hours

Piazza

Lecturing

Homework design

Lecture design

Grading

Improving the student experience

Page 52: Practical advice on being a TA - Stanford Computer Science

Improving the student experience

Have weekly feedback forms

Page 53: Practical advice on being a TA - Stanford Computer Science

Have weekly feedback formsStudents get extra credit for filling them out

Improving the student experience

Page 54: Practical advice on being a TA - Stanford Computer Science

Have weekly feedback formsStudents get extra credit for filling them outImprove your course based on the feedback forms

Improving the student experience

Page 55: Practical advice on being a TA - Stanford Computer Science

Help students find study partners

Improving the student experience

Page 56: Practical advice on being a TA - Stanford Computer Science

Help students find study partnersAt the beginning of the quarter, students fill out a Google Form with their name, email, and location

Improving the student experience

Page 57: Practical advice on being a TA - Stanford Computer Science

Help students find study partnersAt the beginning of the quarter, students fill out a Google Form with their name, email, and location

Match them randomly with other students

Improving the student experience

Page 58: Practical advice on being a TA - Stanford Computer Science

Help students find study partnersAt the beginning of the quarter, students fill out a Google Form with their name, email, and location

Match them randomly with other students

This helps students who have no friends in the class

Improving the student experience

Page 59: Practical advice on being a TA - Stanford Computer Science

Help students find study partnersAt the beginning of the quarter, students fill out a Google Form with their name, email, and location

Match them randomly with other students

This helps students who have no friends in the class

Form is optional: this quarter, 15 out of 316 students took advantage of it

Improving the student experience

Page 60: Practical advice on being a TA - Stanford Computer Science

Be fair to SCPD (remote) students

Improving the student experience

Page 61: Practical advice on being a TA - Stanford Computer Science

Be fair to SCPD (remote) studentsAll office hours should be accessible through Zoom

Improving the student experience

Page 62: Practical advice on being a TA - Stanford Computer Science

Be fair to SCPD (remote) studentsAll office hours should be accessible through Zoom

Hold some office hours on evenings and weekends

Improving the student experience

Page 63: Practical advice on being a TA - Stanford Computer Science

Be fair to SCPD (remote) studentsAll office hours should be accessible through Zoom

Hold some office hours on evenings and weekends

All recitation sections should be recorded

Improving the student experience