Final Project
For your final project, you are welcome to create anything you'd like using any of the course topics as a starting point.
Phase One: Ideation
Before you start working on your final project, you'll need an idea!
A: Selecting a Base
First, choose one of the CS Sampler lessons to serve as a basis for your project. You could make:
- A Python turtle program, or anything else with Python
- A p5.js interactive artwork or game or anything else with Processing
- A Twine story or other interactive fiction
- A vibe-coded thing
- A MakeCode Arcade retro game
- A JavaScript 3D or 2D game, or anything else with JavaScript
- An A-Frame world, or any other 3D creation
NOTE: If you would like to use a different language/framework as a starting point, you must clear it with your instructors first
At the end of this point, you should have a base technology selected!
B: Blue Sky Brainstorming
Once you have an idea of the tech you want to use, it's time to start thinking of ideas. Remember, in this phase, there are no bad ideas.
At the end of this part, you should at least ten (10) different ideas of what you could build!
C: Making a Decision
Once you have a lot of ideas, it's time to whittle them down to what's feasible and reasonable. Think through some pros and cons of each idea, and consider which idea would be the most fun, rewarding, and valuable.
At the end of this part, you should have exactly one (1) idea with which to move forward!
Phase Two: Implementation
Once you have settled on an idea, it's time to bring it to life!
A: Planning on Paper
Before you dive into the code, think through everything on paper. This will help you catch pitfalls and think through more details before you get lost in the code.
At the end of this part, you should have an outline of your project, including each part of it and how they all fit together.
B: Building with Code
Now, it's time to start coding! Follow the outline to fill out your project as you see fit. This is the part where you actually build the thing. It does not have to perfect - you can think of this part as a rough draft.
At this end of this part, you should have something working - an MVP.
C: Meeting the Requirements
Once you have something, you can start making it better! Do some testing, look out for user experience issues or bugs, and think about what might make your project better. As part of this phase, it is highly recommended to share your project with other students, so they can provide constructive feedback as well. This step of iteration and refinement will help ensure your project is as good as it can be.
At the end of this part, you should have something good - something that clearly represents at least two hours of effort/work!
Phase Three: Conclusion
You might have finished building your project, but there's more you have to do to fully complete it!
A: Hosting the Project
You will need to make sure your project is available online. If you're using HyTOP, you're all set! If you're using MakeCode Arcade, Twine, vibe coding outside of HyTOP, or some other tech, you may need to do some extra stuff to make sure your project can be reached.
At the end of this part, you should have a link you can share where anyone can access your project!
B: Submitting the Project
Once you have your project available, you actually have to share it! Click here for the Final Project Submission form.
C: Presenting the Project
The final step to complete your project is to present it! Presentations are scheduled for the final day of club. As part of your presentation, you should talk about your motivations for choosing the project, challenges you faced developing the project, and your code architecture. You should also demonstrate your project!