Personal Project
The Big Idea
A personal project is a great way to practise real programming — you choose the problem, plan the solution, and build it from scratch. The goal is not a polished product. The goal is to experience the full cycle: idea → plan → MVP (Minimum Viable Product) → reflection.
An MVP is the smallest version of your idea that actually works — just the core feature, nothing extra. You build that first, then expand from there.
◎ This whole page is optional. Only continue here if you have worked through the competency checklist and want to go further.
Your Roadmap
| Section | Time |
|---|---|
| Choose your project | 30 min |
| Plan and research | 3 hrs |
| Build your MVP | 8 hrs |
| Expand and style | 7 hrs |
| Wrap up | 1.5 hrs |
| Reflect | 30 min |
Choose Your Project
Pick something that genuinely interests you. A project you care about will keep you motivated when the heavy lifting starts.
Some questions to help you decide:
- What problem do you wish someone had already solved?
- Is there a tool, game, or app you use regularly that you could try to build a simpler version of?
- Is there a topic — sport, music, food, language — you know well enough to build something around?
There are no wrong answers. The most important thing is that you want to finish it.
Show project ideas to get you started
- A quiz with 5 questions about a topic you know well
- A tip calculator or simple unit converter
- A to-do list (add items, mark them done)
- A flashcard flipper with a handful of cards
- A number guessing game
- A page that generates a random joke, quote, or colour
- A simple version of the JavaScript Cafe from Sprint 3, with your own twist
These are starting points — change them, combine them, or ignore them entirely.
Plan and Research
Before you write any code, spend time planning. This is how professional developers work — and it will save you hours of frustration later.
Step 1: Write down what your project will do
In plain sentences — no code. Describe what a user will see and what they can do.
Step 2: Define your MVP
An MVP (Minimum Viable Product) is the smallest version of your idea that actually works. It strips out everything "nice to have" and leaves only what is essential.
Example: If you are building a quiz app, your MVP might be:
- Five hardcoded questions displayed one at a time
- A button to submit an answer
- A score shown at the end
That's it. No timer, no categories, no leaderboard — those come later.
Write your MVP down as a list of 3–5 features. A non-coder should be able to read it and understand what the app does.
Step 3: Break your MVP into steps
Order the steps so that each one produces something that runs. Starting with the part that is hardest to test last is a common mistake — test early and often.
Build Your MVP
Work through your plan one step at a time. When your MVP is running, stop adding features. A working MVP is a success.
Commit often. After each small piece of working code, commit it with a meaningful message. If something breaks, you will always have a safe point to return to. Aim for small, focused commits — not one giant commit at the end.
If you get stuck:
- Re-read the error message carefully — it usually tells you exactly what went wrong
- Try a smaller version of the problem in isolation
- Check in with the team on Discord
Expand and Style
◎ Only start this section once your MVP is working.
With your MVP running, you can now add the features you left out of scope. Work in order of priority — what would make the biggest difference to someone using your project?
This is also a good time to work on the visual styling. CSS can transform how a project feels to use.
One rule: Do not add a major new feature on the final day. Bug-fix and polish only.
Wrap Up
Step 1: Fix small bugs and rough edges
Do a final pass through your project. Fix anything that is broken or confusing. Do not start a new feature.
Step 2: Post your project
Share your finished project in your homegroup channel or the general Foundations channel on Discord. You do not need it to be perfect — sharing work in progress is normal and encouraged.
Step 3: Write your reflection
Once you’re done, write a mini reflection on what went well, what didn't go well, and what you would do differently next time.
The Big Idea (revisited)
The skills you practise here — scoping a problem, building an MVP, reflecting on what you would do differently — are the same skills you will use during Bootcamp. The project itself matters less than the process you go through to build it.