Learning Outcomes:

• Demonstrate the ability to apply appropriate design patterns in a given problem context.
• Demonstrate the ability to implement and manipulate basic data structures.

More details will be released closer to the time… But here’s the gist of it:

Where and when?

• Week 12
• Wednesday 4pm-6pm (i.e, during regular lecture time).
• In-person, in one of the City campus labs.
• Invigilated.
• Capped within the 2-hour lecture slot, but will likely be shorter than that.

What are the main restrictions?

• You will be using the lab computers (not your own laptop).
• You will be given programming exercises to complete in CodeRunner.
• You will not be allowed to use the internet or any other resources.
• You will not be allowed to use an IDE, Copilot, ChatGPT, etc.
• You will not be allowed to refer to any notes.
• You will not be allowed to have any other application open (other than CodeRunner in a single web browser tab).

How to best prepare?

This is a practical programming test, so the best way to prepare is to practice, practice, and practice your programming.

Here are some suggestions:

• Do all the practice exercises provided, such as:
  • The CodeRunner exercises,
  • The Get Your Hands Dirty exercises,
  • The REWIND exercises,
• Play around with and tweak all the ACP exercises to explore what happens when you change things, and make them your own.
• Be confident you can do the exercises:
  • Without referring to any notes or other resources,
  • Without relying on the compiler to tell you what’s wrong,
  • Without relying on an IDE to help you write the code,
  • Without relying on Copilot or ChatGPT to help you write the code,
  • Without relying on the internet to help you write the code,
  • Without relying on Bob, Jenny, or your classmates to help you write the code.
• Get started on the assignments early, as this provides excellent practical programming experience and confidence.
• Repeat the above magical recipe 17 million times (or until you feel confident).