search

codewars / codewars.com

Issue tracker for Codewars
https://www.codewars.com
BSD 2-Clause "Simplified" License
2.08k stars 219 forks source link

Writing a simple kata is much more "honour-profitable" than writing a hard one. #133

Open MMMAAANNN opened 9 years ago

MMMAAANNN commented 9 years ago

...especially if it stays in beta forever due to unresolved issues.

A good example of a "profitable" kata like that: http://www.codewars.com/kata/testing-1-2-3/

I am not saying this was intentionally left with unresolved issues to gain honour, but should it really work that way?

Here is also another wording for this issue which I left on the forum some time ago:

MMMAAANNN(2 kyu)1 month ago There is now a paradox with voting. Most of the katas are currently actively upvoted during beta and rarely upvoted after that. Now there are some ancient beta katas that don't get approved due to unresolved issues (e. g. because it is a duplicate of another kata), and such katas have significantly more votes than their similar counterparts who finished beta early. That leads to a trend where high-quality katas usually get less votes than katas with issues. This is not good. To resolve this, I suggest resetting kata votes to zero on approval. This will make it fair for all katas. Of course, this will also require subtracting beta-stage votes from total votes on existing approved katas.

┆Issue is synchronized with this Clickup by Unito

bkaestner commented 9 years ago

...especially if it stays in beta forever due to unresolved issues.

The button is also rather small in an approved kata. When a beta kata seems ready, everyone clicks "Ready" and therefore upvotes the kata. But if one solves a kata after each other, (s)he usually only looks at some of the other solutions, and then clicks on "train next".