Get good at
seeing your data

A path is not a name — it's a position in a tree. Transforms compose down it, visibility toggles cascade along it, and blueprint queries select subtrees with globs. Design the tree once, and filtering, styling and coordinate frames all fall out of it for free.

Querying a timestamp returns, for each component, the most recent value logged at or before it. So you only log what changed: a mesh logged at t=0 is still there at t=900. It also means a component you never update stays pinned at its first value — usually what you want, occasionally a surprise worth knowing about.

Log at least two: a monotonic sequence for determinism, and a wall clock for correlating with the outside world. Add a simulation clock when sim time and real time diverge. Timelines are cheap; switching between them in the viewer costs nothing.

Log images as encoded frames rather than raw arrays, mark calibration and geometry as static, downsample high-rate scalars that nobody reads at full rate, and split long sessions into chunks. A well-shaped 10-minute run is usually under a gigabyte.

As soon as two people open the same recording. Manual panel arrangement doesn't survive contact with a teammate; a blueprint checked into the repo does, and it turns "look at the third panel" into a shared reference.