Field note · June 29, 2024
Five minutes with release_year in movie-ratings
9,000 rows, 53 distinct values, and the one fact about release_year that changes how you query it.
Someone asked what is in release_year on movie-ratings, and the honest answer took one query.
9,000 rows, no nulls, 53 distinct values. Year of release.
The five-number version: min 1,972, p10 1,977, median 2,001, p90 2,019, max 2,024. The mean is 1,999.
The p10 to p90 band — 1,977 to 2,019 — is where ordinary rows live, and it is the pair worth quoting when somebody asks what to expect. Min and max describe the two strangest rows in the table and nothing else; they are useful for spotting impossible values and misleading for everything else.
select
count(*) as rows,
count(release_year) as present,
count(*) - count(release_year) as nulls,
count(distinct release_year) as distinct_values
from movie_ratings;Nothing dramatic: the mean and median are within 0.1% of each other, so an average is a fair summary. That is worth confirming rather than assuming — it is not true of most money columns.
Where this matters: a symmetric column is one you can average, threshold and chart without hedging, which makes it unusually cheap to work with. Knowing which of your columns are like this and which are not is most of knowing when to be careful.
The grain is one row per user-film rating, which is the context every one of those numbers depends on. None of them survive a change of grain, which is why "profile the column" and "profile the table" are the same job. Full schema, and the CSV, on the dataset page.