Evaluation

Two moments. No assignments, no uploads, no deadlines outside the room.

Team project presentation — 40%

In weeks 11 and 12, each group presents the team project built in Block 3. Half the groups present each week.

The presentation has two parts:

1. Live demo — the app running at its deployed URL. Not slides, not a video: the real thing, clicked through in front of the room.
2. Code walkthrough — we open the repository and ask questions. Every member is asked about code they did not write. If you shipped it as a team, you are expected to understand it as a team.

The grade is a group grade, adjusted per person from the walkthrough. Rubric: it works · design · scope and ambition · verification · walkthrough.

Exam — 60%

Written exam in the exam period. Two halves:

• 30% — your own solo project. Questions about the app you built alone in Block 2: why it is structured the way it is, what happens when a given input arrives, where a described bug would live. The question template is public and shown in Week 5, so you know the shape of the questions while you build. You may use AI for all of the project — the exam checks that you understood what you shipped.
• 30% — general code-reading. You are shown AI-generated code and asked to judge it: find the bug, predict the output, spot the missing case, pick the better spec.

An A4 cheat sheet (both sides, handwritten or printed) is allowed.

Practical notes

• Nothing is submitted on Moodle. All work lives on GitHub. Moodle carries links and announcements only.
• The solo project is examined, not graded — there is no hand-in and no deadline. It exists so the exam can ask you about it, and so your team has something to build on in Block 3.
• Every practical class ends with a TA seeing your work run. That is the check-in; there is no other.
• One grade-review form is opened at the end of the semester, after grades are published. It is the only form in the course.