← CSC 313 Teaching Computing

CSC 313 Culminating experience presentation

Each culminating experience “group” (including those doing their projects individually) will give a 7–10 minute presentation outlining their project (see below for details). The goal for this presentation is primarily to get some intermediate feedback on your project, from both myself and your classmates. Since we are somewhat time bound by external factors—i.e., the scheduled workshops or teaching activities—we’ll do these on Thursdays of weeks 5, 6, and 7.

Each “teaching” project will present what they have prepared the week before their activity. Non-teaching projects are interspersed throughout. I randomly ordered these projects and placed them accordingly.

Presentations will take place during the first part of the day’s lab session. Attendance for these lab sessions is mandatory unless arranged with me beforehand.

Schedule

April 28 (wk 5)

  • Intro to Python (1)
  • Intro to Python with a quiz game
  • Intro to data science with Python

May 5 (wk 6)

  • Intro to APIs with Python
  • Intro to web development
  • Intro to Python (2)
  • Individual proposal—Meta-cognitive scaffolding during debugging
  • Intro to AWS services

May 12 (wk 7)

  • Making music with code
  • Intro to MATLAB for Chemistry students
  • Individual proposal — Property-based testing in introductory programming classes
  • Individual proposal

Contents of the presentation

Here are items that your presentations should include (not necessarily in the order given).

For those teaching workshops (at the library or otherwise)

Your presentation should cover the following content:

  • Intended audience. In terms of experience with computing and/or any other dimensions that are relevant)
  • Learning objectives. These should be phrased in terms of measurable items. For example, “Understand Python syntax” is not a good learning objective, because it’s not clear how to measure whether someone understands Python syntax. Instead, you can say “given a snippet of Python code and an input, a student should be able to predict what its output will be”.
  • Contents of your workshop. This is the bulk of your presentation. Presumably, by the week preceding your workshop, you should have a really good idea of what your workshop will look like. Communicate this to us. You don’t need to give us a minute-by-minute breakdown, but walk us through the exercises/activities and how they relate to your stated learning objectives.

For these projects in particular, this will be your primary opportunity to get some feedback about your planned workshop before you run it.

For those working on research proposals

  • Research question
  • Background. What do we need to know to understand the importance of your proposed research? How does your research fit into related prior work?
  • Motivation. Why is it important to perform the proposed research? What does it add to prior work?
  • Research plan. From a high-level, describe your proposed research plan.

I am expecting most of your time to be spent on items 1–3 above.

Deliverable

There is no online submission for this. You’ll be graded primarily based on the following criteria:

  • Completeness (i.e., addresses all the requested items to a satisfactory degree)
  • Preparedness