Learning Data

Topics › Analytics engineering › In the weeds of data crafting

Make the call

Eight situations an analytics engineer really faces: credit that doubled, a census number for the app, a report that changed after a rename, a withdrawal recorded after publishing, monthly snapshots, a version current before it's true, four fixes for a fan-out, and two versions that overlap. 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 4 of 10.

← Previous · 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

Next · Film 5 of 10 →

Promises and proofs

Every gap gets a decision. Promise it in a contract; prove it with a test, written before the code it checks.

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