
UNION ALL Keeps Repeated Rows: Decide Whether Those Repetitions Mean Something
Combining two tables is not always the same as collecting their distinct values. Before choosing UNION or UNION ALL, decide whether two identical-looking…
From a download link to a useful question: approachable guides to understanding and working with data.

Combining two tables is not always the same as collecting their distinct values. Before choosing UNION or UNION ALL, decide whether two identical-looking…

A cumulative percentage adds shares as you move through an ordered table. Its final value is a useful check, but only after you know which observations…

A remarkably good model score deserves a question about the data split, not just congratulations. If the same examples appear in training and evaluation,…

Two columns of map coordinates may look ready for subtraction, but their units and reference system matter. A difference measured in degrees is not…

Record a simulation’s seed alongside its settings and code version so a repeatable result is not mistaken for evidence that its assumptions are correct.

Use an explicit, unambiguous ordering rule when extracting a limited database sample so first ten does not mean whichever rows happen to appear.

Inspect CSV quoting before counting visible lines as records, especially when fields contain addresses, notes or other multiline text.

Before counting categories, inspect spelling, capitalisation and invisible spaces, while preserving distinctions that belong to the original data.