|
|
|
|
|
by drdaeman
2842 days ago
|
|
This means the numbers are meaningless and don't provide a good representation. Needs better data. Call me inhumane, but a single story doesn't mean anything. It's just some random point in the set. Drawing any conclusions from such a single point is dangerous (the larger the set, the more), as we humans just love to extrapolate single points and even tend have quite strong emotional defenses about their importance. To remove the emotional part, just think of something from IT, like response times or test coverages. See, a story of an obscenely long API response (out of thousands) doesn't make much sense anymore. Debugging individual cases may even lead you on a completely wrong track. Unless you want to merely resolve that particular single request. I'm sorry about the tone. Stories about others make humans relate (which is good), but they also have such undesirable effects (hype over facts, extrapolating, etc). |
|
Averages and generalizations only tell a portion of the story. Anecdotes can shed light on "noise".