Aggregating away the signal in your data
stackoverflow.blog
stackoverflow.blog
One thing this article is reinforcing to me is the value of domain knowledge to an analyst. I am deeply skeptical of "one size fits all" analysis tools, services, and consultancies for exactly this reason. Making insight actionable requires knowing what actions can be taken, and how.
Domain knowledge is still essential, both to pick meaningful projections of the data and to drill into patterns once observed. But since domain knowledge is always limited, it's nice to have techniques that allow you to notice patterns you didn't know well enough to summarize.
https://www.youtube.com/watch?v=jYH8CQS6Ab0
One of the best tips, straight from a practitioner - from a former Google search ranking engineer who touched multiple other domains later in the career. Stop tuning knobs and watching metrics, look at the data!
Something the author hints at but isn't quite explicit: manual inspection of individual examples from your dataset can help you understand what questions to ask, what category to facet on, or the bug in your aggregation.
I think the graphs look great and I want to make similar stuff - does anyone have experience with observable? Does it beat ggplot, tableu and others?
The depth and knowledge the author displays is fantastic.