Concept map: Data contracts
Prerequisites (two levels) and direct dependents of Data contracts. Show everything
- 2prerequisites shown
- 1direct dependents
- 2lessons use it
Insights 41
- Replace sentinel values like -999 before they reach linear or distance models
- Fix the missing-indicator column list, because the default mode ties the schema to the training extract
- Choose Yeo-Johnson over Box-Cox when a feature can be zero or negative
- Ship a changed feature definition under a new version instead of editing it in place
- Test the serialization boundary where offline and online features meet for type and null coercion
- Run a leave-one-feature-out audit on a schedule to remove features that no longer earn their dependency
- Validate business rules after the schema passes, because schemas only check shape
- Chunk along the document's own structure before tuning chunk size
Projects 10
- Booking-flow A/B test: should the one-page passenger form ship?
- Late deliveries and review scores in a marketplace: how much damage, and on which lanes?
- Passenger no-show probabilities for overbooking and reconfirmation decisions
- Card-fraud alerts under a fixed review budget: ranking on day 1, tested on day 2
- Flagship: final bookings per departure from booking-curve snapshots
- Route-day passenger backtest and the capacity/price what-if: forecasts are not causal answers
List view151 concepts
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 11
Day 12
Day 13
Day 14
Day 15
Day 16
Day 17
Day 18
Day 19
Day 21
Day 22
Day 23
Day 24
Day 25
Day 26
Day 27
Day 28
Day 29
Day 31
Day 32
Day 33
Day 34
Day 35
Day 36
Day 37
Day 38
Day 39
Day 40
Day 41
Day 42
Day 43
Day 44
Day 45
Day 46
Day 47
Day 48
Day 49
Day 51
Day 52
Day 53
Day 54
Day 55
Day 58
Day 59
Day 60