06-reference

3blue1brown why colliding blocks compute pi

Sun Apr 19 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·reference ·source: 3Blue1Brown (YouTube) ·by Grant Sanderson

“Why colliding blocks compute pi” — 3Blue1Brown

Episode summary

Grant returns to his 2019 viral result — two frictionless blocks colliding elastically produce a total count of collisions whose digits match pi, when the mass ratio is a power of 100 — and delivers the full physical/mathematical explanation he left out of the original. The spine of the argument: translate the dynamics into a 2D state space where v1 and v2 become coordinates, rescale axes by sqrt(mass) so conservation of energy becomes a circle (not an ellipse), then exploit the inscribed angle theorem plus the small-angle approximation arctan(x) ≈ x to show that the number of collisions before the “end zone” is the largest integer n with n·arctan(sqrt(m2/m1)) < π. For mass ratios that are powers of 100, that arctan is a power of 10, and the answer literally reads off the digits of pi. The back third is a meta-essay: purity exposes hidden connections, and this puzzle is secretly mirrored in Grover’s algorithm — the subject of his next video.

Key arguments / segments

Notable claims

Why this is in the vault

Two reasons. First, the meta-principle Grant closes on — “purity exposes hidden connections” — is the cleanest articulation of why Ray Data Co spends any time at all on theoretical exposition rather than only on applied case studies. The colliding-blocks → Grover’s isomorphism is the kind of unexpected bridge that would not exist if mathematicians had refused to idealize, and it’s the closest available rhetorical template for explaining why Sanity Check treats things like information theory and measure concentration as practically relevant to shipping data products. Second, the video is a reusable pedagogy reference for any future newsletter on state-space thinking — translating a tangled physical or business question into a geometric question via the right coordinate change is a move the newsletter returns to often, and this is the cleanest worked example in the vault so far.

Mapping against Ray Data Co