@kazk

Will do.

The kata hasn't been abandoned. Yes, much of the initial feedback I received felt like a weird mix of frustration, discouragement and a desire to help -- feedback that is, at best, vaguely aligned with the Codewars 'Community Code of Conduct'. Much of the initial feedback was a strange cocktail indeed. But given all of the useful insights shared above/below, I have a better understanding of the history and current state of things here at Codewars, and I have a better understanding of the various frustrations aired here. I'm listening, even to those whose frustrations (and other struggles) get in the way of being patient and communicating clearly and politely; I'll keep what's genuinely useful and leave the rest (like throwaway/discouraging comments about my level of experience, which are just as toxic for the people making them as they are for the people receiving them). I'll continue listening and contributing. Regardless of the level of my kyu, I can make helpful contributions -- and that includes kata and feedback to help shape a healthier Codewars based on a consistent and clear foundation of fundamental requirements, on relatively unambiguous docs and systems that support everyone involved. I'm looking at the discourse for this kata, as a whole, and there's a lot here that is useful -- I see the potential for better support all around, including for those who have met those future clearer (and more strenuous) requirements for katas and still need constructive and encouraging feedback from others.

No, Taste Sensations has not been abandoned. I haven't let others' projected struggles discourage me, and I haven't given up. I've un-published it, and I'm going to continue working on it as I go back to familiar and unfamilar docs (thanks again, @hobovsky) and keep learning what I can despite the limitations (mine, as well as those in the Codewars docs and systems). I've gained a lot from being here, solving katas and learning from others with more (typically much, much more) knowledge and experience than me. In large part, creating and publishing Taste Sensations was my way of giving back, of offering something in particular to those with less knowledge and experience than me. And I'm going to keep doing that, as I seek to raise the standard of my katas and tests. I'm all for raising standards, clarifying/refining/streamlining the docs, and helping people to lift themselves up in the process of learning together. My goal is to keep using Codewars as a resource for my lifelong growth as a programmer -- all the way to 1kyu, and beyond. I would love to get to the point where I am contributing here as a moderator -- for me, that would be a significant mile-marker of my development not only as a programmer but as someone committed to others' growth as well.

@KenKamau Thanks for your support. I'm not going to give up on this kata -- in developing it further, there will be opportunities for me to keep learning. BTW, I've learned a lot by solving your katas.

@B1ts @hobovsky I'm grateful for your taking the time to consider and respond to my thoughts and questions with your insights. Extremely helpful. These are all juicy ideas, and this feels more like a useful conversation, more like the community for which I signed up. Thanks for the links as well -- very helpful, though I can see now, too, how the docs neeed further development.

The lesser experienced of us need support from those who can help clarify things without exasperation and without making judgements and declarations about our lesser knowledge and experience. Even with a higher barrier of entry and clearer support in the docs, even after doing what one needs to do to get a kata to a particular standard before publishing it, there still needs to be safe space to make mistakes and learn new things after publishing.

@JohanWiltink Thanks again for your feedback.

@B1ts You make a a fair point about the need for someone who is creating a kata to have read the docs. I've read the codewars docs that I can find, and I'll go back to those docs to fill in the holes. If you can provide a link to the documentation to which you're referring, I'd appreciate it. When it comes to process, there is obviously more than one relevant to codewars, and my process of learning (including publishing, making mistakes and learning from them) is one of them. It needs to feel safe to make mistakes here. It's with the help of supportive feedback that I can improve the kata, make it more original.

This doesn't really support moderation process

What is the best way, when creating and publishing a kata, to support the 'moderation process', aside from abiding by the docs?

Thanks for taking some time to answer my question -- many thanks for that. But you can keep the elitist commentary -- that doesn't support my process at all.

Cheers.

Thanks for the feedback.

• Error messages are no longer useless ;)
• Fixed tests added in addition to the random tests
• How is a user's modification of the input an issue? How can that be avoided in the sample test?

It's not useless insofar as its an obstacle within each subarray. What are your thoughts on how the middle element could function differently?

Thanks for the link to the docs. Much appreciated.

Using JavaScript, my code passes 11 out of the 13 tests, passing four out of the six tests listed under 'should return false if walk does not bring you back to start'.
The error message: 'Value is not what was expected'.
Is there any way to find which specific tests resulted in the error?
Cheers.