Check-in Presentation

When: Week 15, Thursday 4/28 during lecture
Length: ~5 minutes per student
Weight: 3% of course grade
Submit: Upload your slides to Gradescope (linked to Moodle) after your presentation

Overview

This is a low-stakes progress check, not a final presentation. You don’t need working code yet. The goal is to share where you are, get feedback from your classmates and instructor, and make sure you’re on track before the final push.

What to Cover

Keep it simple and aim for no more than 5 slides. Here’s a suggested structure:

1. What are you making? (1–2 slides) Show us your concept. This could be sketches, reference images, color palette ideas, or a mockup of what the finished piece might look like. Give us enough to picture it.

2. How are you generating it with code? (1–2 slides) Walk us through your approach. You might show a rough outline of your functions, pseudocode, or early working code if you have it. If you don’t have code yet, describe your plan clearly enough that we can give useful feedback.

3. What’s your plan from here? (1 slide) What do you still need to do between now and 5/15? Mention anything you’re unsure about or anticipate being tricky.

Grading

Clarity of concept (1%): We understand what you’re making and why.

Thoughtfulness of plan (1%): You’ve thought about how to approach the problem, even if the code isn’t written yet.

Time (1%): Aim for 5 minutes. Going significantly over isn’t fair to classmates presenting after you.

In addition, you will give each other feedback and receive feedback from your classmates. The details of the peer review activity are to be announced.

Tips

• Slides are a tool to help you present, not a document to read from. Keep text minimal.
• If you have early code running, a quick demo is great but not required.
• This is a good chance to get unstuck. If you’re confused about your approach, this is the right time to try to get feedback.