-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove "Average Power User Assessed Rank" from kata editor #2207
Comments
thing is, the usual average has its troubles too. Afaik:
@kazk: if a change needs to be done here, imo the best (quick) option would be to remove the integer values and just drop the float result instead. related: #1939
errrr.... actually there is... x) |
Yeah, that number is pretty much pointless. See:
CW has many WTFs like this from over the years.
The number is updated whenever a rank assessment is done. So in your example, their choice will not be accounted for until the recalculation is triggered.
Good point. I just checked and the power users' average is rounded to the nearest. The average of all is not rounded and is truncated implicitly when stored in the database.
The field is an integer field so it's not quick. How does this relate to #1999? I don't think showing an average is helpful to begin with. If we're going to keep the current beta process largely unchanged, I'd show a sparkline: The root cause of all the conflicts between users when assessing ranks is that everyone have their own scale. Like I've been saying, this is Codewars' fault for not providing any guidance over the years. |
I wanted to open a feature request to show a breakdown of all the votes (a bar graph would be great) exactly for this reason, but kinda forgot about it :( |
that's #1939 actually. But the thread got crowded about other topics... (my fault... x) ) |
It looks like this info was added at some point to show how PUs' opinions are different from the general public's ones, but as of now it serves no good purpose:
┆Issue is synchronized with this Clickup by Unito
The text was updated successfully, but these errors were encountered: