Field note · December 30, 2024
Course note — One metric, one definition
The reason three dashboards show three different revenue numbers is never a bug. It is three people who each wrote their own definition, and all of them were reasonable.
Revised One metric, one definition this week. The change was small and the reason was not.
The reason three dashboards show three different revenue numbers is never a bug. It is three people who each wrote their own definition, and all of them were reasonable.
The first draft explained the mechanism and stopped. What was missing was the failure: the thing that happens when you get it wrong, described concretely enough that someone recognises it later. A lesson that only teaches the correct version leaves you unable to spot the incorrect one, which is the situation you will actually be in.
It sits in the Modelling the warehouse module. The exercise is a thinking one rather than a query one — some of this material is about deciding what to compute, and that does not need a keyboard.
Ordering matters here more than in most courses. It follows Why your query costs what it costs and leads into Joins that do not fan out, and reading it out of sequence mostly works but costs you the setup.
Free means free, and it also means we can rewrite it whenever it is wrong. No edition, no errata PDF, nothing to repurchase. The whole course is 36 lessons and the fixes land the day we find them.