Milestone map
Milestone map
2 milestones
Do the course work in public
7–14 weeks (12 hrs/week)
Take Multivariable Calculus for free and do a worked-solutions notebook for the problem sets, every step written out. Keep everything in one public repo or notebook as you go.
Proof required
Link your public repo or notebook with a worked-solutions notebook for the problem sets, every step written out, and a screenshot or log showing the self-check passed.
What gets checked
- Steps are shown, not just answers.
- A program checks a sample of your answers numerically.
- Mistakes you found are marked and fixed.
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 a worked-solutions notebook for the problem sets, every step written out.
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Each unit has problems with full solutions. Do them first, then mark your work against the 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: Multivariable Calculus (MIT OpenCourseWare Scholar) 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
Masteryfor the dedicated
What a verifier looks for
- Steps are shown, not just answers.
- A program checks a sample of your answers numerically.
- Mistakes you found are marked and fixed.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Find the best point with gradients
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a program that uses gradients to find the lowest or highest point of a real function (a cost, a fit to data), with a plot of the path it takes. Keep it small enough to finish in about two weeks.
Proof required
Link a program that uses gradients to find the lowest or highest point of a real function (a cost, a fit to data), with a plot of the path it takes, with a README that says how to run or read it.
What gets checked
- The gradient is worked out by hand and matches the code.
- The plot shows each step.
- It says when the method can get stuck.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
A program that uses gradients to find the lowest or highest point of a real function (a cost, a fit to data), with a plot of the path it takes.
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
Masteryfor the dedicated
What a verifier looks for
- The gradient is worked out by hand and matches the code.
- The plot shows each step.
- It says when the method can get stuck.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.