2023‐24 Delivery

xx-1xx Week x

Discussion points

Action points

02-23 Week 6

Discussion points

• Attendance has dropped to ~25%
• Recognition that this is a bit of a weird week re: content

Action points

• explore introducing some content earlier at relevant points e.g. leaks/valgrind when discussing pointers

02-09 Week 5

Discussion points

• numbers dropping off - clashes with assignment
• Value added by coming to sessions - support and additional explanations
• good forum activity around the assignment
• pick up in office hr bookings

Action points

• Opportunity for more interaction after reading week break, for ideas see: IDEAS

01-26 Week 3

Discussion points

• Re-cap of pointers went well

Action points

• Avoid explaining a new task just before a break
• Consider an exercise where matrix size is modified

01-19 Week 2

Discussion points

• Some students not engaging with the activities in the session. 1 person playong solitaire throughout, another with a blank screen.
• Some interaction between students, but quietly. Ideas for encouraging pair programming discussed.
• Not as much progress as hoped - notes read?

Action points

• Move some easier exercises into pre-work
• Some not familiar with the Git workflow, add links to notes from Python course
• When responding to questions or an answer, repeat so picked up by microphone
• Keep responses on Menti hidden until at least 30% have answered, then reveal and discuss
• Allow more time for students to answer: use think, pair, share?

01-12 Week1

Discussion points

• Attendance - a number of students left early
• Good balance of staff to students needing assistance
• Not always easy to get to students
• Accessible design of slides and Menti quiz

Action points

• Have some challenge/stretch activities available
• Bring post-its to identify clear rows, to be rows 3 and 6
• Sam to share Menti theme with Michael to improve accessibility