Grace Hopper Center

CSC 222 Weekly Assignments: Weeks 18 to 20

CSC 222


Overview

This is it, time for your final projects. I asked you to choose a project to work on during the last three weeks of our course, and promised you a rubric. here it is.

Wednesday, January 21st

Classwork / Homework

Sean, Waleed, Delaine, Evan and Giselle should all have active vouchers for the CPE certification this morning. After they confirm this with Chris, the rest of us will move to the commons to work on our projects.

Please plan your time wisely so you are ready to present your final project to our class on Thursday, January 29th.

Ongoing Beginning Wednesday, January 21st

CPE Update

I was delighted to see Evan and Giselle on our snow flaky Saturday morning. Along with Sean, Waleed, Delaine and Arya, they have the option of taking the CPE certification today. They also have the option of waiting until the last day, Thursday January 29th (when final projects will also be due).

Monday, January 10th

Classwork / Homework

It was great seeing Sean, Giselle, and Waleed on Saturday to study for the CPE certification. They join Delaine and Arya in earning retake vouchers. We have one more opportunity to do this, next Saturday, January 17th between 9 am and 12 noon.

I added a new exercise 18 to Chapter 4 Exercise Set 1: CPE Practice as a result of conversation with Giselle on Saturday.

By the end of class today you should email me a proposal for your final project.

To help you select an appropriate project, let me share some case studies developed for the AP Computer Science program that my dear friend Chris Jones turned me onto:

The advantage of selecting one of these projects is that it comes with structure and guidance, so if you are feeling unsure of what to do, I highly recommend choosing one of these.

Whatever you choose, it will be our goal to incorporate your work into our course materials so future students can directly benefit from it.

Sean already emailed me Cursed Tools, a passion project he has been working on for awhile (thanks, Sean!). This reminded me that your project should be:

  1. in its own git repo, with a nice name and README.md describing it.
  2. released under a free-software license so others can benefit from your work.

In fact, instead of emailing me a description of your project, why not just send me a link to your repo and document your project in your README.md?