Yeah, that’s also something that gives me headache sometimes. I search through our history. I implemented it in this Pull Request, but the decision was already made before when the feedback feature was added. From this comment:
Should the weight be about the whole pick-up or just the amount that the foodsaver took home?
It becomes relevant when calculating statistics.
Reasons for asking for the weight …
(1) of the whole pick-up:
- maybe some people have better overview/are better at estimating
- if multiple users give feedback for the same pick-up event, we could calculate the average
(2) only of the amount the foodsaver took home
- seems easier to estimate smaller amounts, which might give more accurate statistics
- conflicting feedback about the total amount are avoided
As @bruno summarized in this comment, we seemed to favor (1) at that time. Back then, we wanted to implement estimates for the average weight per pickup and extrapolate.
The feedback weight input says “Amount of food all of you were able to save (in kg)”. But it seems it’s difficult to tell them otherwise, probably because it’s too difficult for them to estimate the weight of the whole pickup.
I would consider it, although not retroactively. There are many people who entered the numbers the way Karrot told them to, and I wouldn’t want to break their feedback.
Fair point, and I think our planning came from a time when we expected only a small number of users to enter feedback. Now that it’s different and we should reconsider.
Advantage of not doing extrapolation:
- users have more reason to give feedback; might give more accurate numbers
- it is essentially the status quo
- less complexity; easier to understand
Potential problems of having a direct connection between feedback weight and weight statistics:
- users might be tempted to set higher weight to make their pickup statistics look nicer (user statistics do not exist yet, but well…)
- variance of estimation bias between different people doesn’t cancel out
Overall, I think it would be a good choice to “say no” to more cleverness in software, it might get in the way of humans. Rather accept human error and try to nudge them in a good direction (e.g. by showing hints how to estimate weight).