Also, OP, focus the Beta stage on one language. Now you have to fix them in two languages.

It would be much better if the OP published one kata, got it through the beta stage applying all remarks raised by reviewers, and then moved to creating the rest of challenges. Because now, the OP has four published kata, all affected by the same issues, collecting downvotes due to technical problems.

Specify that "starting from 0" does not mean the returned list starts with that 0 ( it would make a lot of sense if it did actually ).

Kata should have fixed tests as well as random tests. Submit tests should always include example tests. These things combine nicely. :]

( What you absolutely do not want is a solution that fails example tests but passes submit tests. )

Needs description example or example test with add_-5 ( or similar negative value ). It's perfectly valid, it's within the spec, but it comes as a surprise in Submit Tests now, and surprises in Submit Tests are ++UnGood.

• if you're going to have a functional programming tag, you may want to showcase actual functional programming in your example solution.
• it is perfectly possible to sort an empty list. the result is an empty list.

I think it's generally a good idea not to take any feedback that points out problems in your kata personally. Try to focus as much as possible on improving the kata and not worry about how the criticism was delivered (that's what's important to you, and your goal is to have a good kata; focus on that). Of course, the goal of the platform is to create a pleasant environment for everyone, but that won't be a problem for you if you simply keep your mind focused on improving.

I'm a beginner and my first kata was a disaster, but i learned a lot from the criticism and got a approved kata, but i definitely have a lot of room for improvement.

propose improvements to the process

We are trying :')

I thought anyone could submit ideas and the community would shape their fate, but I didn’t know that a core group of experienced users is responsible for maintaining the quality bar.

Basically, this. However, this does not mean that there is no place to discuss your idea for a kata, there is the #kata-ideas channel specifically for this purpose on Codewars Discord. It is also hinted in documentation.

Unfortunately, there is one hugely incorrect assumption behind your reasoning: you seem to think that improvements to the process are not being proposed, and that there is no internal push for better solution. This is, unfortunately, very, very wrong assumption, and the problem lies on the receiving end of the proposals, suggestions, and requests :(

@Kacarott Thanks for your objective answer. I now realize I misunderstood how kata creation works on this platform. I thought anyone could submit ideas and the community would shape their fate, but I didn’t know that a core group of experienced users is responsible for maintaining the quality bar. And I didn’t mean to cause unnecessary work by submitting a kata without reading the docs thoroughly. My bad on that.

Maybe you could consider limiting new users to one or two beta katas until one gets approved. That might naturally reduce the overload and push people to prepare better.

That said, I want to add something important: I find it disappointing when someone like Johan vents frustration directly on newcomers rather than addressing the systemic issue with the team. If low-quality kata submissions are such a recurring burden, the mature and efficient approach would be to propose improvements to the process rather than taking it out on individuals trying to learn and contribute. It comes off as unkind and, honestly, a bit cowardly to lash out at those with less experience instead of pushing for a better solution internally.

Anyway, I’ve really learned a lot on Codewars and I appreciate the platform and everyone who helps make it what it is — especially those who offer guidance instead of gatekeeping.

I do think there should be a link to kata authoring guidelines in the kata creation editor. If people then still come up with low quality stuff, we can justify being remorseless.

It's been re-requested again a couple of days ago. Fingers crossed, nth time's a charm.

@Skrimir You are right that disrespect is not welcome, however the way I see it, the comment which started this was not actually disrespectful. It was actual constructive criticism about a very specific problem, albeit communicated quite bluntly. I think you misunderstood it as disrespect where that wasn't intended. This is ok, misunderstandings happen, however you responded by sarcastically disregarding Johan's attempt to point out a problem, which itself could be seen as disrespect. This might explain why his last comment was condescending.

So please:
@Skrimir try not to take constructive criticisms of your kata personally, the beta phase for kata can be quite brutal (and it used to be much worse), but it is only criticisms of the kata, not the author. I've seen plenty of new author's have their first kata absolutely ripped to shreds, but they took the criticism at face value and made new and better kata which did very well.

@Johan try to make your critiques more clearly about the kata than the author, I think phrases like "You're reinventing the wheel, and yours is square." are unnecessarily abrasive, I think your point is made fairly well without it.

I do think there should be a link to kata authoring guidelines in the kata creation editor. If people then still come up with low quality stuff, we can justify being remorseless.

You are absolutely right! Already changed :)