Working System (Demo Video)
Salary
This task pays a fixed salary of 24 MVP points, plus up to 42 quality points for exceeding the minimum requirements — for a total of 66 points, with a maximum of 11 points per person.
Minimum Viable Product (MVP)¶
By the end of this task your team proves that at least one feature runs once, end-to-end, with the expected result and no errors. The deliverable is a single demo video (max 5 minutes) uploaded to YouTube as Unlisted or Public that shows the program actually running (terminal or app window) with a voice-over explanation. Subtitles alone are not accepted. Pick one clear scenario, show inputs and outputs, and keep the focus on the user-visible behavior—do not do a source-code walkthrough. Aim for a simple, stable demonstration that an end user could follow.
Example: Team 'ByteBusters' demo “Search by keyword”
Their 3:30 video opens with one sentence on purpose, then shows the CLI: they add two books, run a search for “Dune,” and the expected result prints. The narrator explains what the user sees and why it’s useful. No editor windows or code—only the running program.
Technical Details¶
Prepare a tiny script: (1) What & who (10–15s: “This is a simple library catalog for readers”), (2) One clean scenario (2–3 minutes: start app → input → output → finish), (3) Close (10–20s: “Next we plan Save/Load”). Record your screen (any screen recorder is fine), ensure clear audio (test mic), and large enough font for the terminal. Keep runtime under 5 minutes—too short or too long weakens the grade; 3–4 minutes is a good target. Upload to YouTube as Unlisted/Public, then place the link in README.md under a ## Demo section, optionally noting the commit/tag used. The video must show the system working, not IDEs or code; if you mention technical details, keep them brief and tied to what the user sees.
Quality¶
Quality focuses on user experience, demonstration clarity, and timeboxing. Speak slowly, avoid jargon, and explain why the feature helps the user. Show a stable, repeatable run (no crashes, no warnings), tidy screen, readable output, and steady pacing. Respect the max 5 minutes; aim for a smooth story rather than rushing. Common pitfalls to avoid: racing through source files, narrating internal algorithms without showing behavior, or trimming the scenario so much that the user can’t understand the value.
Example: Team 'NullPointers' keep it user-first
Their 4:00 video for “Load CSV → List Entries” uses a small sample file, shows the exact command, and briefly notes an error message the app would show if the file were missing—then demonstrates the successful case. Clear audio, readable terminal, and a one-sentence wrap-up.
Example: Team 'PixelPenguins' show the feature, not the code
For a simple cellular automaton, they display the grid, toggle a few cells, run one generation, and explain what changed. They avoid editor windows entirely, keep the cursor visible, and end with “Next: Save/Load patterns.” Total time: 3:45, within the limit.