Milestone map
Milestone map
2 milestones
Do the course work in public
5–10 weeks (5–10 hrs/week)
Take Introduction to Probability for free and do worked solutions for the probability problem sets (counting, conditional probability, random variables, limit theorems). Keep everything in one public repo or notebook as you go.
Proof required
Link your public repo or notebook with worked solutions for the probability problem sets (counting, conditional probability, random variables, limit theorems), and a screenshot or log showing the self-check passed.
What gets checked
- Every step is shown.
- A simulation in code checks at least five of your answers.
- Mistakes found against the solutions are fixed, not hidden.
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 worked solutions for the probability problem sets (counting, conditional probability, random variables, limit theorems).
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Do the matching problem sets for each topic, then mark your work against the posted solutions.
- 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 Probability (Harvard Stat 110 (free lectures on YouTube)) 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
- Every step is shown.
- A simulation in code checks at least five of your answers.
- Mistakes found against the solutions are fixed, not hidden.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Check a probability puzzle by simulation
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a write-up of a real probability question (a game, a queue, a test result) solved on paper and checked by a simulation. Keep it small enough to finish in about two weeks.
Proof required
Link a write-up of a real probability question (a game, a queue, a test result) solved on paper and checked by a simulation, with a README that says how to run or read it.
What gets checked
- The paper answer and the simulation agree.
- The simulation runs enough trials to be steady.
- The write-up says what was assumed.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
A write-up of a real probability question (a game, a queue, a test result) solved on paper and checked by a simulation.
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
- The paper answer and the simulation agree.
- The simulation runs enough trials to be steady.
- The write-up says what was assumed.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.