almost three months ago now i wrote an e-mail to support because i’d been confused about one of my autodata goals (which i’ve since archived)—i’d vagualy remembered a derailment on it, but looking at the graph, i couldn’t find it anymore, and was confused. turns out some autodata goals overwrite datapoints when there’s been new progress synced since, for the day of the derailment! (which does absolutely make sense, when you think about it.)
(this story has not necessarily very much to do with the following post/question, but it might be helpful for context, maybe. or maybe not. in any case, i wouldn’t have known how to start this post without this bit of context XD)
do you think that there should be statistics about derailments in the goal settings?
(either optionally toggle-bly if one wants to see/hide them, or always, permanently there, maybe hidden in a more obscure place)
personally, i think that it would be super valuable to have statistics about derailments; like:
- number of past derailments
- dates of past derailments
- maybe also “how much data would have been missing for a derailment to not have been a derailment, on average” (+ total minimum/maximum)
- other ideas?
“number of past derailments” can of course sometimes be inferred from the current pledge amount, but that works Not At All when the pledge cap is low!
“dates of past derailments” (and thus also the total number) could of course be found out by scrolling through the graph, but, let’s be honest, even with my not-even-half-a-year-long-ones that’s absolutely too much effort for me already, for most of them. (besides, i would have to make a note of it somewhere else, which is, of course, tedious
semi-relatedly, i would also love it if the starting pledge for a goal could be shown somewhere! (i’m the kind of person that forgets these things within minutes!)
of course, circling back to the beginning, all beautiful statistics would be completely lost/useless on autodata goals where a derailment data point will be overwritten the next day … *sad mara
@olimay, who answered my e-mail at the time, brought up, among other things, some valid arguments against having derailment statistics:
It’s not something we currently tabulate. One concern is that tabulating it and making it available (even it’s in a relatively obscure place) might end up being really demoralizing for some users, so there’s some caution against implementing it.
which absolutely make sense as well, unfortunately.^^