List of tutees here. A worse list ('Faculty & Student Information' --> List of all tutored students and links to information). SIS used to have a list.
Different schools have different routines for tutorials. Computing always meets the whole group, relitively often. The frequency of meetings changes with the year of the students:
- First years: once a week in first semester; once a fortnight in semester two.
- Second years: twice a term
- Third years & MSc: ?once a term?
Scheduling - the first years (and sometime the second years) will have a slot in their timetable for tutorials for each term. I haven't figured out how to find out what this is without asking the students. You organise the other years as you want.
The groups are too big for the offices, so try to book a bigger room - every other member of staff will also try to book a bigger room at the same time.
These were meant to mirror Oxbridge's every-week tutorials-with-academic-content; however at Leeds there is no academic content. Our basic goal is to make friends with the students, so they have a friendly face to turn to if things go wrong (and hopefully you build enough of relationship that they come to you before things go wrong...).
You will meet your new tutees the week before semester one starts. The tstaff mailing list will send out a temporary page containing your tutees. I tend to play games in these sessions. There might be a couple of meetings in the week, and a "party" in the refectory at the end.
Resources for tutorial sessions are improving. Sam's ideas. Uni page here, tutor toolkit, random email from FEPS (which doesn't match with the meeting frequencies suggested in computing), general strategies (computing doesn't do 1-1 meetings) and referral points.
- every session: quickly go around everyone and answer: "one thing that's gone well, one that's gone badly, and what are you looking forward to". Good way to quickly gauge mood and have everybody say something.
- introduce some of your research (communication challenge for you!)
- public speaking (who can talk for 5 minutes with repeating, present a news article, module content, etc...)
- debate. Break the group in two and have them prepare arguments for and against a particular point:
- PG's essays
- debate: are software patents evil? (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
- egoless programming
- Long Now / Feynmann
- A Declaration of the Independence of Cyberspace
- \/\The Conscience of a Hacker/\/
- team work (solve a jigsaw (but only one blindfolded person can touch the pieces), ball-flow, play Pictionary...)
- exam technique (go through the past-papers archive before exam season). Ask everyone how they revise and what works best/worst.
- review a topic that most have issues with (pointers in C, professional use of email...)
- living in the UK
- typical computing careers (pay-scales, tax-rates, countries, typical software-engineer vs other roles, video games developer, google's promotion hierarchy, pay vs. interesting work vs. where you live vs. salary, interviews). link1. link2. leeds destinations. academic flow.
- the Professional Computing module throws some assessment at the tutorial sessions in the first semester of the first year.
- Ask everyone to present one of these mental-health-support cards.
- Games. Mafia, code names, or others. Poor-man's articulate.
- SWOT analysis of a topical issue (exam results, year-so-far, module progress...)
- Read chapters of interesting books:
There is little incentive for the students to attend (marks or curriculum):
- best keep it fun.
- remind them that it'll be you writing references etc...
- email students who fail to attend is week asking "is everything okay?".
- Luckily there are also very few checks that tutorials take place or are well taught.