Learning Data

Topics › Analytics engineering › In the weeds of data crafting

Make the call

Eight situations an analytics engineer really faces: two accounts with one student ID, a shared email, an agent's claim with no query, hashes that moved overnight, a pull request that drops the readable key, a credential nobody earned, a reopened account, and a new status code. 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 3 of 10.

← Previous · Film 2 of 10

Start from a question

A model has no edge until a question gives it one. Model only what the question touches, and name who owns each meaning first.

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

Next · Film 4 of 10 →

One row of what, and when

Twelve on census day, nine today: both right. Say what one row is and which day it describes, before any SQL, and test both.

5 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