And the award for the shortest solution goes to you! :)

come on, that's better than many top voted ones

this is my favorite

lmfao, I think i've seen this in production

Unfortunately this kata was retired because too many people downvoted it. :/ I'm glad you enjoyed it though!

Thanks for your reply! This is my first kata so I'm definitely still learning and appreciate your feedback.

I'm not trying to say the kata is "good" what I am saying is that I think it's pretty normal to fix tests during beta, is it not?

Now, you say:

What makes the things worse is that you're patching the holes along the way

but when I was reading about the beta process I came across this.

During this period it is important to leave feedback to the kata author about ways it can be improved. It is likely that during the beta process, many of the solutions will become invalid as feedback is given and test cases are added/modified.

I've solved much worse katas than mine and that's not to say I don't appreciate raising the bar for quality katas so to speak but your point about users having a bad experience at finding the solution is silly to me. I set the Discipline as Puzzle for this very reason, it's not a fundamental aspect of javascript that you'd reach for to solve something like this initially. I also set the estimated rank fairly high because I don't expect users to be able to bang this out like an 8 or a 7 kyu.

this kind of problem is more a lost cause than anything

I disagree with this point, this is something that was fun for me to throw together and I'm just unfamiliar with the process. I feel like at this point I have a pretty good test suite after going back and patching solutions that got past my original tests which I thought the beta process was for, partially. To get feedback and make any changes that need to be made.

I also feel like the auto-retire feature is too aggressive. I didn't get any feedback before just immediately having my kata retired by people who didn't even solve it correctly...

The one person who actually solved the kata the correct way enjoyed it, it was all the people who did it the wrong way that downvoted it which seems like it's in bad faith to me.

Again, thanks for your time and your feedback! I'm not sure anything will come of this but thanks for letting me vent.

Thanks for building interesting kata, keep it up mate :)

Hi,

The main problem is that the idea of the kata itself is just bad, actually ("bad" as "bad for a kata"). What makes the things worse is that you're patching the holes along the way, meaning you actually didn't create the kata with a clear mind about what it implies to create something like this, and it and just "proves" (in a way) that the idea is bad. I agree that the original idea is kinda funny, but you'll waste sweat and blood, trying to enforce ~~any-~~everything to get there, especially in JS, while at the same time, if you actually succeed at enforcing this special solution, most users will have a pretty bad expeirence at finding how to solve it.

As you can see (I hope), this kind of problem is more a lost cause than anything, when it comes to make a kata out of it.

cheers

I have a kata that I've put together https://www.codewars.com/kata/bananas-1/javascript but it keeps getting auto retired without any feedback for why people are downvoting it. I also can't delete the kata so now https://www.codewars.com/kata/bananas-1/javascript and https://www.codewars.com/kata/banana/javascript exist (because the original banana one was retired and I can't delete it). I've been updating the test cases as I see incorrect solution get around my tests which is why I think it's getting downvoted but it's just annoying that I'm trying to work through any issues that my kata has but before it even gets a real chance it's automatically retired.

Any help would be appreciated! What am I doing wrong?

This is the way I intended people to solve this kata. Nice job!

lmao, you're incredible

haha, you're too clever! I love that you're pushing me to write more/better tests.