Learning Data

Topics › Analytics engineering › In the weeds of data crafting

Make the call

Eight situations an analytics engineer really faces: a fix made in the catalog, last year's diagram, a rename that “only affects one mart”, a number copied onto a page, two descriptions one word apart, a deprecation date ignored, a decision log deleted, and a new question. 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 9 of 10.

← Previous · Film 8 of 10

An agent on the team

An AI agent drafts in minutes. It follows rules written in the project, shows the query behind every claim, never weakens a test, and people approve.

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

Next · Film 10 of 10 →

End to end

One question, ten steps, ten commits. Every file in its place, for as long as it's needed.

8½ 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