Tutorial 3 (week 4)

Problem Set 2 Presentations

We will have some of you present the contents of your README.md to the tutorial. This includes:

• the dev guide
• a sample flow of your application, e.g. when adding a peg
• the data structure that backs your board implementation
• testing, very briefly (just go through what classes you test and do not test)
• the tradeoffs justification
• the persistence justification

You are free to present more if you wish, such as some parts of your code. No need to get fancy (such as with slides) -- just go through your README and highlight anything that you think is cool/unconventional/needs more feedback.

The intent of this is to share your design decisions so that you can receive feedback and improve it for Problem Set 4, which will use your Problem Set 2 codebase. Additionally, your peers will also gain other perspectives in implementing the same application.

The tutor will personally go through all of your README, and they might ask you to present some parts that are unique/interesting.

You are reminded that to get the full 6% marks from tutorial participation, you need to present at this opportunity, or present your Problem Set 3 at tutorial 5.

Problem Set 3 Discussion

Problem Set 3 might seem daunting -- you need to create a physics engine and a game engine from scratch! A lot of you might not even have an idea on how a physics engine is supposed to work.

Hence, let us have some time to discuss Problem Set 3 in this tutorial. Please prepare questions that you want discussed, and we will try to discuss them after the presentations.