• This chapter’s key idea is: EDA is not a checkpoint; it’s an ongoing loop.
  • A good data team rarely moves cleanly from “EDA→modeling ↔ done.” You inspect something, discover an issue, rethink the question, transform the data, revisit an earlier assumption, and repeat.
  • Your two notes are especially useful:
    • Correlation has two practical jobs: finding potentially predictive relationships and identifying redundant variables.
    • Never trust correlation as a number alone. Visualize it. Pearson correlation mainly captures linear association, so very different relationships can produce misleadingly similar—or surprisingly weak—correlation values.
  • One nuance I’d attach to the first note: two highly correlated variables do not always contain the same information. Square feet vs. square meters basically do because one is an exact transformation of the other. But two variables can be strongly correlated while each still contributes useful independent information.
  • The broader note I’d keep: EDA is where you argue with your assumptions visually—not just calculate statistics.
  • Correlation gives you a relationship to investigate, not a causal story to believe.
  • The examples show the three main possibilities really well:
    • Confounding: ice cream sales and shark attacks both rise because of summer.
    • Reverse causality: maybe higher home values improve schools, not just the other way around.
    • Feedback loops: both variables may influence each other over time.
  • And often there are other variables outside the dataset, which is the uncomfortable part people forget.
  • One nuance from the screenshot is worth preserving too: “Correlation does not imply causation” should not become “correlation is meaningless.”
  • Sometimes a relationship really is causal. The correct mindset is not to dismiss it automatically, but to ask what evidence would support the causal claim.
  • EDA can generate problems, not just investigate predefined ones. A data scientist can notice an anomaly, pattern, or strange relationship first, then formulate the business or research question around it.
  • Use correlation to discover. Use causal reasoning to explain. Don’t confuse the two.