Concept map: Hypothesis-driven EDA
Prerequisites (two levels) and direct dependents of Hypothesis-driven EDA. Show everything
- 4prerequisites shown
- 5direct dependents
- 3lessons use it
Insights 6
- Check whether missingness depends on other columns before dropping incomplete rows
- Classify an outlier as error, rare truth or regime change before deciding what to do with it
- Sample by a hash of the entity key so a sample stays consistent across tables and reruns
- Do not treat LIMIT or TABLESAMPLE SYSTEM as a random sample, and use reservoir sampling for streams
- Plot the rows before trusting a summary table, because identical statistics can hide different shapes
- Try several histogram bin widths and check density plots for impossible values
Projects 12
- 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?
- Where does a steel plant's electricity cost exposure concentrate? Load and power-factor profile
- Readmissions by admitting specialty: case-mix-adjusted comparison without chasing noise
- From session data to an experiment backlog: which conversion drivers deserve a test?
- District math results: a binomial model that separates context from performance
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