Milestone map
Milestone map
2 milestones
Do the course work in public
5–9 weeks (14–16 hrs/week)
Take Introduction to Computational Thinking and Data Science for free and do the 6.0002 problem sets (optimisation, graphs, simulation, curve fitting). Keep everything in one public repo or notebook as you go.
Proof required
Link your public repo or notebook with the 6.0002 problem sets (optimisation, graphs, simulation, curve fitting), and a screenshot or log showing the self-check passed.
What gets checked
- Each problem set gives the results its handout expects.
- Plots have labelled axes and titles.
- Random results use a fixed seed, so others get the same numbers.
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 6.0002 problem sets (optimisation, graphs, simulation, curve fitting).
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Each problem set says what results to expect. Check your program gets them, and test small cases by hand.
- 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 Computational Thinking and Data Science (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 gives the results its handout expects.
- Plots have labelled axes and titles.
- Random results use a fixed seed, so others get the same numbers.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Simulate a real situation
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a Python simulation of something real (a queue at a shop, a rumour spreading, a savings plan) that runs many trials and plots the results. Keep it small enough to finish in about two weeks.
Proof required
Link a Python simulation of something real (a queue at a shop, a rumour spreading, a savings plan) that runs many trials and plots the results, with a README that says how to run or read it.
What gets checked
- It runs from the README.
- The model's rules are written in plain words.
- Results come from many trials, with the spread shown, not one lucky run.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
A Python simulation of something real (a queue at a shop, a rumour spreading, a savings plan) that runs many trials and plots the results.
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.
- The model's rules are written in plain words.
- Results come from many trials, with the spread shown, not one lucky run.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.