Prove
LiveProof-of-Work · Oct–Nov: every verified proof counts. 35 days leftAll outcomes
Skills

Turn Warehouse Data into a Dashboard

7 weeks · 2 milestones

Business Intelligence Concepts, Tools, and Applications (Data Engineering Zoomcamp (DataTalks.Club), module 4), then one project of your own. Part of the Varsity Curriculum: Data Science.

Milestone map

Milestone map

2 milestones

Do the course work in public

3–5 weeks (4–5 hrs/week)

Take Business Intelligence Concepts, Tools, and Applications for free and do the module 4 homework: data models with tests in dbt, and a dashboard built on them. 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 4 homework: data models with tests in dbt, and a dashboard built on them, and a screenshot or log showing the self-check passed.

What gets checked

  • Model tests run and pass.
  • The dashboard reads from the models, not raw tables.
  • Homework answers match the dashboard.

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 4 homework: data models with tests in dbt, and a dashboard built on them.

Steps

  1. Make a public repo or notebook first.
  2. Do one unit at a time and commit after each.
  3. Run the self-check: Answer the homework from your own models and dashboard, then compare with the posted answers.
  4. Write a short README: what is here and how to run it.
  5. Ask three people who know the topic to check it.

Template

README
Course: Business Intelligence Concepts, Tools, and Applications (Data Engineering Zoomcamp (DataTalks.Club), module 4)
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

  • Model tests run and pass.
  • The dashboard reads from the models, not raw tables.
  • Homework answers match the dashboard.
  • Ask one question about a choice in the code; the answer should be clear.

You'll sign in first, then come straight back here.

Build a dashboard someone uses

1–3 weeks (5–8 hrs/week)

Use what you learned. Make a dashboard for a real person (a club, a shop, a teacher) that answers the questions they asked, built on tested data models. Keep it small enough to finish in about two weeks.

Proof required

Link a dashboard for a real person (a club, a shop, a teacher) that answers the questions they asked, built on tested data models, with a README that says how to run or read it.

What gets checked

  • The person's questions are written down and each has a chart.
  • Data models have tests that pass.
  • The person says they used it (message or note).

Common mistakes

  • A project too big to finish.
  • A demo that only works on your machine.

Powstik Guide

A dashboard for a real person (a club, a shop, a teacher) that answers the questions they asked, built on tested data models.

Steps

  1. Write one line: what it does and for whom.
  2. Build the smallest version that works.
  3. Test it on someone else's machine or with someone else reading it.
  4. Write the README.
  5. 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 person's questions are written down and each has a chart.
  • Data models have tests that pass.
  • The person says they used it (message or note).
  • Check that the work is the person's own.

You'll sign in first, then come straight back here.