Milestone map
Milestone map
2 milestones
Do the course work in public
7–14 weeks (6–10 hrs/week)
Take Introduction to Computer Science and Programming using Python for free and do the course problem sets in Python. Keep everything in one public repo or notebook as you go.
Proof required
Link your public repo or notebook with the course problem sets in Python, and a screenshot or log showing the self-check passed.
What gets checked
- Each problem set runs and gives the right answers.
- The code is yours: names, comments and commit history match a real person working.
- Edge cases (empty input, big numbers) are handled.
Common mistakes
- Copying posted answers: verifiers read the history.
- Skipping the self-check, then asking for review too early.
Powstik Guide
A public repo or notebook with the course problem sets in Python.
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Do the practice problems for each unit until the checker passes them.
- Write a short README: what is here and how to run it.
- Ask three people who know the topic to check it.
Template
README Course: Introduction to Computer Science and Programming using Python (MIT OpenCourseWare) What is here: How to run it: Self-check result: What was hardest:
What gets sent back
- No history, just one big upload.
- Self-check not shown.
- Code that does not run from the README.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Each problem set runs and gives the right answers.
- The code is yours: names, comments and commit history match a real person working.
- Edge cases (empty input, big numbers) are handled.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Build a small Python tool you use
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a Python program that solves one real problem for you or a friend (a budget helper, a quiz maker, a file sorter). Keep it small enough to finish in about two weeks.
Proof required
Link a Python program that solves one real problem for you or a friend (a budget helper, a quiz maker, a file sorter), with a README that says how to run or read it.
What gets checked
- It runs from the README steps on a fresh machine.
- It solves the problem it claims to solve.
- It uses functions and data structures from the course, not one long script.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
A Python program that solves one real problem for you or a friend (a budget helper, a quiz maker, a file sorter).
Steps
- Write one line: what it does and for whom.
- Build the smallest version that works.
- Test it on someone else's machine or with someone else reading it.
- Write the README.
- Ask three people to check it.
Template
README What it does: Who it is for: How to run it: What I would do next:
What gets sent back
- Does not run from the README.
- Not clearly the person's own work.
- Claims more than it does.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- It runs from the README steps on a fresh machine.
- It solves the problem it claims to solve.
- It uses functions and data structures from the course, not one long script.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.
Part of