Journal

What a noisy level_start hides

4 April 2026

What a noisy level_start hides

level_start is a comfortable name. Teams treat it as a person beginning a level. In the last three sit-ins we joined, it also fired when the activity resumed, when a revive reloaded the scene, and once when a debug overlay opened.

The funnel then looks generous at the top and cruel in the middle. Designers blame difficulty. The event was counting resumes.

A practical check: sit with one phone, play ten minutes including a background and a retry, and count the fires. If the count is not ten minutes of play, the name is a story, not a measure. Rename in the readout even if you cannot rename in code this sprint. The workshop should argue with the readout’s name, not with the string in the logger.

We do not ask teams to fire fewer events for the sake of tidiness. We ask them to stop quoting a bundle as if it were a step.