The Silence That Counts
A null response gets filed as "no data." That's a category error. Praise and criticism are both proof that someone read the thing and had a reaction worth typing out. Silence sits somewhere else on the graph entirely: it can be the same registering as praise or criticism, minus the effort of writing it down, or it can mean the thing never reached anyone at all. Those two silences produce identical rows in whatever log you're reading, and they mean opposite things.
The confirmation step is the whole argument. A proposal goes to a channel and gets zero replies. You don't yet know anything. Maybe eleven people read it and had no objection worth typing. Maybe the notification got eaten by a client that batches pings, and nobody opened it. Same zero, two different worlds: one says the plan is sound enough that reasonable people looked it over and let it stand, the other says you've measured whether the message sent, not whether anyone read it.
This is why anyone who actually cares about silence goes to some trouble to confirm reach before trusting it. Read receipts, view counters, the little "seen by" list under a message, the eye icon on a shared doc. None of that machinery exists to catch praise or criticism, those announce themselves without help. It exists to turn an ambiguous zero into a confirmed zero, so the absence of a reaction can finally be read as a reaction rather than a gap in the record.
Once reach is confirmed, the silence starts to carry weight. It says: enough people were exposed to this that if it were wrong, offensive, exciting, or confusing, somebody would plausibly have said so, and nobody did. That's a real result. It rules out both ends of the distribution, the delighted reply and the furious one, in a single data point that took nobody any effort to produce.
The failure is treating unconfirmed silence the same way. A post with no comments and no traffic numbers behind it says nothing about whether the argument landed; it might just mean nobody found it. A pull request sitting open for a week with no review isn't quiet agreement, it might be a queue nobody's gotten to. A support ticket that never gets reopened after a fix ships looks like the fix held, but if traffic moved off that code path entirely, it just means nobody's around to notice it broke again.
Sorted properly, the cases line up:
- comments on a post with a real number behind the traffic claim,
- review activity on a PR that's been open long enough for someone to plausibly have looked,
- reopened tickets against a change that's still seeing live use.
Each needs the exposure confirmed first. Skip that step and the absence of complaint tells you about your distribution list, not your work.
The instinct to treat silence as absence of evidence is understandable, it's the safer default, the one that doesn't let you claim credit you haven't earned. But it throws away a real signal in the process. Once you've done the unglamorous work of proving someone was there to respond, their not responding becomes information you paid for and are entitled to use.