Learning Data

Topics › Analytics engineering › In the weeds of data crafting

Make the call

Eight situations an analytics engineer really faces: a join in staging, one mart built on another, CTEs called cte2, an incremental table after a rule change, a mart that recomputes a rule, ephemeral steps, a step the award may not need, and a contract that stops the build. 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 6 of 10.

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

Next · Film 7 of 10 →

Who owns what

Each fact's meaning has an owner. Owners publish a public, versioned core; consumers build on it, never on each other's marts.

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