Milestone map
Milestone map
2 milestones
Do the course work in public
6–11 weeks (6–10 hrs/week)
Take Operating Systems: Three Easy Pieces for free and do the homework for virtualisation, concurrency and persistence. Keep everything in one public repo or notebook as you go.
Proof required
Link your public repo or notebook with the homework for virtualisation, concurrency and persistence, and a screenshot or log showing the self-check passed.
What gets checked
- All three parts are covered.
- Answers are checked with the simulators.
- Concurrency code is free of races (shown with a test).
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 homework for virtualisation, concurrency and persistence.
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Run each simulator, answer, then check with its -c flag.
- 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: Operating Systems: Three Easy Pieces (OSTEP (free book)) 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
- All three parts are covered.
- Answers are checked with the simulators.
- Concurrency code is free of races (shown with a test).
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Finish an OSTEP project
1–3 weeks (5–8 hrs/week)
Use what you learned. Make one OSTEP project (a shell, a memory allocator or an xv6 change) with tests. Keep it small enough to finish in about two weeks.
Proof required
Link one OSTEP project (a shell, a memory allocator or an xv6 change) with tests, with a README that says how to run or read it.
What gets checked
- It builds and runs from the README.
- The supplied tests pass.
- The write-up explains one hard bug you fixed.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
One OSTEP project (a shell, a memory allocator or an xv6 change) with tests.
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
- It builds and runs from the README.
- The supplied tests pass.
- The write-up explains one hard bug you fixed.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.