Milestone map
Milestone map
2 milestones
Do the course work in public
3–5 weeks (4–5 hrs/week)
Take Relational Database Support for Data Warehouses for free and do the module 3 homework: load data into a warehouse, then partition and cluster tables and compare query costs. Keep everything in one public repo or notebook as you go. OSSU lists a Coursera course, where graded work is paid. We use the free Data Engineering Zoomcamp.
Proof required
Link your public repo or notebook with the module 3 homework: load data into a warehouse, then partition and cluster tables and compare query costs, and a screenshot or log showing the self-check passed.
What gets checked
- Tables load from your pipeline, not by hand.
- Before-and-after query costs are shown.
- Each choice (partition, cluster) says why.
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 module 3 homework: load data into a warehouse, then partition and cluster tables and compare query costs.
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Answer the homework from your own warehouse tables, then compare with the posted answers.
- 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: Relational Database Support for Data Warehouses (Data Engineering Zoomcamp (DataTalks.Club), module 3) 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
- Tables load from your pipeline, not by hand.
- Before-and-after query costs are shown.
- Each choice (partition, cluster) says why.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Make slow questions fast
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a warehouse table design for your own dataset that answers three real questions, with query times or costs before and after. Keep it small enough to finish in about two weeks.
Proof required
Link a warehouse table design for your own dataset that answers three real questions, with query times or costs before and after, with a README that says how to run or read it.
What gets checked
- All three questions get the same answers before and after.
- Times or costs are measured, not guessed.
- The design is explained in plain words.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
A warehouse table design for your own dataset that answers three real questions, with query times or costs before and after.
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
- All three questions get the same answers before and after.
- Times or costs are measured, not guessed.
- The design is explained in plain words.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.
Part of