Recording the Walk-Through Video
Plan a walk-through that supports each spoken claim with clearly visible on-screen evidence. Demonstrate an actual application run, show a relevant failure and how the application handles it, and explain a significant implementation decision within five minutes. Avoid exposing credentials, personal data, or other sensitive information so reviewers can verify the functionality and limitations demonstrated in the recording.
A 45-second recording shows three source files while the narrator claims the tool handles ticket priorities and errors. The recording ends without executing the tool. The viewer can inspect the source code but cannot verify priority classification or error handling.
Support each significant claim with readable on-screen evidence and explain what the demonstrated behavior means for the user. When a demo video is required, prioritize an end-to-end workflow demonstration over a detailed walk-through of every source file.
A coordinator needs a list of urgent ticket IDs and a separate list of tickets with unresolved priority classifications. The local queue reviewer identifies urgent tickets and flags those requiring priority clarification. It does not assign tickets or mark them as resolved.
Showing verifiable evidence
Ensure the recording provides verifiable evidence of the required behavior. Show readable input data, execute the tool, inspect the resulting classifications, demonstrate input rejection, and explain why tickets with unresolved priorities remain visible.
Review the following hypothetical 3-minute, 30-second recording:
0:00–1:20: Scroll through the repository without executing the application.
1:20–2:30: Show function descriptions at a zoom level that makes the text unreadable.
2:30–3:00: Display a previously captured output screenshot while claiming that the live system works.
3:00–3:30: Show a missing-column error but incorrectly describe it as a successful result with no urgent tickets.
(Select all that apply.) Which claims does the above recording scenario verify, which remain unsupported, and what additional footage is needed to demonstrate the required behavior? Multi-select
Keep the screenshot and explain that its successful output proves the live system is reliable.
Replace the old screenshot with results clearly produced by the command shown, and only claim what that run shows.
Show the missing priority column, the failed run and its exit status. Explain that the input was rejected, not classified as having no urgent tickets.
Replace the repository scrolling with readable sample input and footage of the command actually running.
Keep the current footage but add smooth transitions so the viewer can follow along without seeing a command run.
Make the text bigger, and replace the unreadable function tour with workflow evidence and narration that matches what’s on screen.
A missing required column prevents the application from processing the input. Reporting this failure as an empty urgent queue could cause the coordinator to miss tickets requiring attention.
Review the assignment requirements before planning the recording. Check whether a recording is required, along with its duration, format, submission instructions, access restrictions, and AI-assistance permissions. Publicly available examples do not establish ...