◀ 11.1c11.1d11.1e ▶

11.1d — Create PT: Build Day 3

The list works (11.1b), the algorithm works (11.1c). Today: the parts the VIDEO shows — input the user gives, output the user sees, and the 60-second path through your program that will become the recording. Build day for the audience.

Build Day ~50 min

Input (the rubric row: a program that responds):

Output (what the video shows as behavior):

The demo path (design it like a level — 7.5 skills!):

  1. Seconds 0–10: state the purpose in text on screen (not voiceover-only)
  2. 10–35: give one input, show the algorithm's result (list visibly changes)
  3. 35–55: give a different input, show the different output
  4. 55–60: the list's final state, readable on screen

Rehearse it three times TODAY — the recording happens on 11.2a and takes under 5 minutes if the path is tight, or an hour of retakes if it is not.

Close of Day ~5 min

Socratic: The 60-Second Path

  1. You rehearsed the 60-second path through your program. Where does the viewer see something change because of something they typed?
  2. The video must show input, behavior and output. Which of the three is hardest to see right now, and what will you do about it before recording?
  3. You found an edge case you can talk about. Which bug taught you something about your own program — the one you will tell as your story for WR2b?

Checkpoint — before moving on, you must be able to:

  • Demonstrate input changing program behavior on screen
  • Show output that differs per input
  • Walk the 60-second demo path without console output
  • Rehearse it in front of a witness and survive

Reference Docs

Need a deeper explanation? These pages cover the same concepts:

Next: 11.1e — Create PT: Build Day 4 + List Check

0/3 answered

Answers save on this device as you type. At the end of class, click Download and upload the file to the Canvas assignment.

Saved on this device only — the Dashboard tracks your progress.