Field note · January 20, 2024
Cutting a lesson down — 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.
A note from writing One metric, one definition, which took three passes to get to something short.
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 hard part of writing this was cutting it. The first version covered every case; the useful version covers the case you hit on a Tuesday and names the rest in a sentence. Completeness is a property of reference material, not of teaching material, and confusing the two produces something nobody finishes.
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.