Milestone map
Milestone map
3 milestones
Pick a real problem and plan it
1–2 weeks (10 hrs/week)
Pick a problem real people have that your CS skills can solve. You can build something new or improve a tool you use. Write a one-page plan: the problem, who has it, what you will build and how you will know it works.
Proof required
Link your one-page plan and notes from talking to at least two people who have the problem.
What gets checked
- The problem is real and the people are named (first names are fine).
- The plan uses skills from at least two sections.
- Success is something you can measure.
Common mistakes
- A problem nobody has.
- A plan too big for one person.
Powstik Guide
A one-page plan for your final project.
Steps
- List three problems you or people near you have.
- Talk to two people who have the best one.
- Write the plan on one page.
- Ask three people to check it.
Template
Problem: Who has it: What I will build: How I will know it works: What I will not build:
What gets sent back
- No real users.
- No way to measure success.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Is the problem real?
- Is the scope doable?
- Is success measurable?
You'll sign in first, then come straight back here.
Ship it to real users
6–10 weeks (15–20 hrs/week)
Build it and put it in front of the people who have the problem. Fix what they hit. Keep the code public with tests.
Proof required
Link the working project (live URL or release), the public repo with tests, and proof that at least three real people used it.
What gets checked
- It works for real users, not just in a demo.
- The repo has tests that pass in CI.
- User feedback led to at least one change.
Common mistakes
- Building for months without a user.
- No tests, so every change breaks something.
Powstik Guide
A working project used by at least three real people.
Steps
- Ship the smallest useful version first.
- Get three people to use it.
- Fix the top problem they hit.
- Write the README and run the tests in CI.
- Ask three people to check it.
Template
README What it does: Live link: How to run it: Who used it and what changed:
What gets sent back
- No real users.
- Tests missing or failing.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Can you use it?
- Do tests pass?
- Is the user proof real?
- Is it the person's own work?
You'll sign in first, then come straight back here.
Defend it in a blind review
1–2 weeks (10 hrs/week)
Write a short report: the problem, what you built, what you measured and what you would do next. Reviewers who do not know you read it and test the project.
Proof required
Link your final report (2–4 pages) and a 5-minute video walking through the project and its code.
What gets checked
- The report matches the project and the numbers are real.
- The video shows the code, not just the screens.
- Limits and next steps are honest.
Common mistakes
- Claims the numbers do not back up.
- A video that hides the code.
Powstik Guide
A final report and a 5-minute code walk-through.
Steps
- Write the report from your plan and results.
- Record the walk-through.
- Have a friend read the report cold.
- Submit for blind review.
Template
Final report Problem: What I built: What I measured: What went wrong: What I would do next:
What gets sent back
- Numbers without sources.
- No code shown.
Resources
Foundationstart here
What a verifier looks for
- Do the numbers in the report hold up?
- Does the code match the video?
- Is the person clearly the builder?
- Would you trust this person to build the next thing?
You'll sign in first, then come straight back here.