Introduction to Computer Science YMT113 · Fall 2026 Assoc. Prof. Ferhat Uçar
15 HCI & Projects Monday, December 28, 2026

Demo Day and Where Computer Science Goes Next

Every student demos their project live. Then a short last lecture: what you now know, what comes next in the curriculum and in the field, and how to keep learning after the course ends.

CS50Week 10 · The End

Before class · do this at home

Watch, read, then come

CS50x 2026 · Week 10: The End by David J. Malan. Watch the lecture on YouTube (you are also enrolled on edX), read the notes, skim the slides. Our lecture builds on it instead of repeating it.

  • Tag your repository v1.0, make sure the README's example run works on a fresh Codespace, and put your two-page report in the repo.
  • Rehearse the demo twice with a timer. Five minutes is shorter than you think.

Learning objectives

By the end of this week you can:

  • 1 Present a working program from your own repository in five minutes and answer questions about its code.
  • 2 Explain the choices you made and what you would do differently.
  • 3 Map the course to what comes next: data structures, algorithms, operating systems, databases, software engineering, AI.

★ the wow moment

In September you did not know what a bit was. Today you are demoing software you wrote, from a public repository, with tests.

That is not a small distance. Everything on this page, from the C in your project to the Git history behind it, is what a first-year developer at a software company does on a Monday. The rest of the degree is depth; the shape is already here.

Demo day

  • Order is posted under announcements the week before. Each demo: 5 minutes plus 2–3 questions.
  • Demo from your own repository in Codespaces or on your laptop. If something crashes, explain what happened and keep going; handling it calmly counts.
  • Grading follows the project rubric; the process part is read from your commit history and tags.

The last lecture

  1. What you now know, as one diagram: bits → C → algorithms and memory → data structures → Python → AI and data → web → people.
  2. What the rest of the degree adds, and which course goes deeper into which week.
  3. How to keep going: CS50’s follow-on courses, open source, your own projects, and the loop (watch, build, push).

Thank you

See the resources page for everything worth your time after the course, and keep your GitHub active. The instructor’s office hours continue during the exam period; email for a slot.

In industry

  • Your repository is your portfolio

    Make the README good, pin the repository on your GitHub profile, and mention it in your first internship application. It is proof, not a claim.

  • Keep the loop

    Watch a lecture, build something, push it. The people who keep learning after a course are the ones who keep that loop running with their own projects.

  • What to learn next

    Data structures and algorithms in depth, then operating systems and networks (C again), databases, a web framework, and one AI course. All of it starts from what you now know.

Go deeper

Tags:demoprojectportfolionext steps