You will have a limited number of practical assignments spread throughout the semester. Each assignment has three parts. Part 1 is a code tracing assignment tied to the provided code in the assignment. Part two is coding related to the assignment. This coding is often much harder than the labs. The last part is a written reflection component. It is important to start early, as each practical assignments are designed to take 2-4 weeks to complete! Remember, to ask for help early and often, by going to the help desk.
Below are each of your practicals.
Practical One - Knight Fight
A text based game that simply puts a knight against a randomly generated monster.
Practical Two - Encrypted Message System 101
A simple program that allows you to leave an encrypted message for another client.
Practical Three - Data Wrangling University Data
A program that helps you look at college statistics, particularly gender differences.
Practical Four - CSV to HTML Converter
A program that reads a CSV file and converts it to an HTML file.
Final Practical Project
Final Project for CS 163/4 - Rebuilding Practicals 1-4.
Rubber Duck for Debugging?
Often the best thing you can do is explain what you are attempting to do to a friend. In the process of explaining it, you usually figure out your errors, and it helps give you a direction to go from there.
Sometimes in companies, this can be a time-cost for other developers so thus the introduction of a Rubber Duck for testing. This gives you an object for you to talk to just like you would a friend. The object doesn’t have to give feedback (just like a friend doesn’t), but instead, the process of talking through the code out loud will often provide insights into both development and errors.