Code Portfolio Assignment

Short Version (the TL;DR)

• During the term, you will identify code blocks that we frequently use, collect them in one place (an Jupyter (.ipynb) notebook), and describe how they work. This will be your code portfolio.

• You will submit your code portfolios on the same days that you take the second and fourth quizzes.

• An example code portfolio has been provided on the course website.

Why are we having you do this?

• It can be used as a cheat sheet on quizzes. Having an up-to-date code portfolio will allow you to quickly find essential chunks of code that you can use in your homework assignments and quizzes.

• Emphasizes that code is reusable. Once you write a piece of code to do some task, you don’t need to rewrite that code every time; you can just copy and paste the code you wrote before.

Description

Over the course of the semester, you will fill in your code portfolio notebook (*.ipynb file) with code blocks/chunks that you find you are (re)using multiple times. For this assignment, you will be bringing together these essential blocks of code. Rather than needing to look back at previous assignments repeatedly, you’ll just need to look at your code portfolio to find the code that you need.

Along with the actual code, you will need to include a text description of what the code does, what specific variables do, etc. (i.e., comment the code). You will submit your code portfolios on the same days as the second and fourth quizzes. The course instructors will check your portfolios to ensure that you are keeping them up to date.

An example code portfolio can be found on the course page.

Grading

Part of final grade on the Code Portfolio assignment will be based on the two check-ins. We expect you to be thoughtful about what code you add to your portfolio and provide clear explanations that another student could understand. As long as you put an honest effort into creating your code portfolio, you should have no problem getting the points for this assignment.