Learning Data

Topics › Analytics engineering › In the weeds of data crafting

Make the call

Eight situations an analytics engineer really faces: a request to model everything, a learner defined as a row, fees mid-build, three words for one learner, two definitions of award, credit for attending, reasons to split, and a question with no decision. Decide what you'd do; each answer explains why. Your answers stay in this browser.

Scenarios

In the series: In the weeds of data crafting

Film 2 of 10.

← Previous · Film 1 of 10

Declare it, then build it

dbt calls every query a model. The data model is the blueprint: declared beside the code, and checked by the tests.

5½ min · 4 labs · 8 scenarios · In the weeds of data crafting

Next · Film 3 of 10 →

What makes it the same one

One learner, three keys, and a look-alike. Rules match most of them; a person decides the rest, and the decision becomes data and a test.

4½ min · 4 labs · 8 scenarios · In the weeds of data crafting

  1. 1Declare it, then build it
  2. 2Start from a question
  3. 3What makes it the same one
  4. 4One row of what, and when
  5. 5Promises and proofs
  6. 6Built in layers
  7. 7Who owns what
  8. 8An agent on the team
  9. 9Written once
  10. 10End to end