Learning Data

Topics › Analytics engineering › In the weeds of data crafting

Make the call

Eight situations an analytics engineer really faces: a revoked badge shown as valid, a column nobody uses, a failure at 2 a.m., a primary key that isn't enforced, tests before the SQL, an expiry no source records, a stale source, and a number one off the census. 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 5 of 10.

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

Next · Film 6 of 10 →

Built in layers

Four layers turn the tests green. Each layer has one job; each CTE, one step; and the rule is written once.

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