Skip to content

TA Check-Ins

During the project, you'll meet with a TA twice, on two different days:

  • Check-in 1 reviews your plan, before you put hours into coding.
  • Check-in 2 reviews your code, and is a rehearsal for your presentation.

These check-ins are the main feedback you'll get before you present. Each one is worth 15 of the project's 100 points: 10 for showing up and 5 for a short reflection afterward.

When to go

You choose when, based on how far along you are:

Week Check-ins available Where you should be
13 (11/16–11/20) Mon 11/16 – Thu 11/19 Writing your README and stubs
Thanksgiving (11/23–11/29) None
14 (11/30–12/04) Mon 11/30 – Thu 12/3 Building your minimum version, about 75% done by Thursday
15 (12/07–12/11) Sun 12/6 – Tue 12/8 (last day of TA hours) Finishing up

Most students have Check-in 1 in Week 13 or 14, and Check-in 2 in Week 14 or 15. If you book both close together, you still need new code to show at Check-in 2. Slots fill up near the end, so don't wait.

How to book

  • Book a 15-minute slot through Microsoft Bookings, signing in with your JMU account. Online check-ins use screen sharing.
  • Arrive ready: your repository pushed, VS Code open, and your README.md on screen.
  • Be on time. If you're more than 5 minutes late, the TA may help someone else, and you'll be recorded as a no-show. If you miss a slot, book another one.

Check-in 1: your plan

Your work doesn't need to be finished. The TA's job is to check your direction and scope against what we expect before you spend hours coding. Be ready to:

  1. Pitch your idea (2 minutes). Who would use your program, and what does it do? What's your minimum version, and what are your stretch goals?
  2. Talk about your data. Where does it come from? Have you found or made the file yet? Is it nested?
  3. Walk through your stubs. Does each function have a clear name, type hints, and a docstring? Which functions are logic and which do input and output? Which logic functions will you test?

The TA will then give you one or two suggestions. Common ones:

  • Too big? Pick the part that will be your minimum version, and move the rest to stretch goals.
  • Too small? Add a feature that needs a data file, a dictionary, or a loop, such as saving high scores, tracking history, or summarizing by category.
  • Logic mixed with input and output? Split the function so the logic can be tested.
  • Using a framework you haven't cleared? Ask your instructor right away (see Going further).

If you have nothing written yet, come anyway. The TA will help you write your first few stubs, but the check-in will be recorded as "not ready."

Check-in 2: your code

The goal is for you to explain your own code, as you will in your presentation. Be ready to:

  1. Demo your program (2 minutes). Run it and show what works so far.
  2. Explain one function (3 minutes). Pick an interesting one and explain it the way you would in your presentation. Then answer a follow-up question or two, like "What does this return for [a small example]?", "Why a dictionary here instead of a list?", or "Show me the test for this function."
  3. Talk about your progress. How much of your minimum version works? Do your tests run? What's left, and what will you cut if time runs short?

The TA will then give you one tip on your code, and one on your explanation. If you get stuck explaining part of your code, the TA will help you work through it and make a note for your instructor. It's much better to find that out now than during your presentation.

After each check-in

The TA records that the check-in happened, how it went, and the main advice they gave you. Then it's your turn: submit a short reflection on Canvas, the same day if you can. A few sentences per question is plenty.

After Check-in 1:

  1. Where does your plan stand now? Describe your minimum version in a sentence or two, and say whether it changed because of the check-in (cut down, expanded, or split differently into functions).
  2. What was the most useful thing the TA said, and what will you do about it? Name the specific change you'll make before Check-in 2.

After Check-in 2:

  1. What's done, and what's left? Which features of your minimum version work now, and what will you cut if time runs short before you submit?
  2. How did your explanation go? Which function did you explain, what did the TA ask about it, and what will you change about your explanation before you present?