Yea I'm honestly a huge brat when it comes to descriptions/directions, I always learned easiest by examples vs. interpreting the written directions (terrible weakness I have, this is probably a learning disability of some kind). So this is my issue. But thanks for the fun Kata!

I liked this Kata a lot - thank you! Its easy to break down into stages and solve piece by piece.

I like this Kata a lot but the instructions are not great, I HATE when the description of the problem does not include enough information about the parameters/rules of the Kata. I don't think I should have to find what this Kata is actually asking for by failing lots of test cases/hitting submit over and over/console.logging a million times. I read the description and thought all that mattered is that all the letters are included in Part1/Part2, and that they must be in order - I started designing my entire solution around that. Its hard to tell if there are not allowed to be other letters/extra letters, because this is not even mentioned in the description, and there is only ONE example in the description of the Kata(which is super simple). I assumed that I had to check the order first and foremost and that all the letters are there. The instructions are vague, no where in the description does it say there can't be extra/other letters that are not in the 's' argument. I want the rules in the instructions, I don't want to have to hit submit a million times to figure out how to actually solve this because the instructions/my design is not addressing the actual Kata requirements due to lack the rules/necessary parameters.

Edit: reading through questions section and I saw this was your intention... I find this annoying when working with katas, but I guess you have your own tastes in the nature of problems you like to solve that don't align with mine, and I respect that.

There needs to be more of a description here than just briefly mentioning the two methods added as properties on the 'node' object argument. I have to console log just to clarify everything for myself. You have a node.setNext method that you didn't even mention in the description of this Kata. This is obviously crucial in solving this. Please update the description to include a clear picture of what your passing into the function as an argument.

Codewars voters prioritize the shortest line count over readability and efficiency... Always.

Almost twins. This is what I came up with pretty much. Except I summed the zeros count.

This was so cute and sweet I did my own version. I just don't like reducing length of arrays I'm running a for loop over so I switched to a while loop format. Good answer!

i just refactored to use ternery statements to replace the if elses.

im not really on board with the codewars obsession with super compacted code. Its not necessarily easier to read and understand.

Omg our solutions are like twins.

OK I dont have that solution I have an O(n) solution that is fast enough - but has errors only on strings with a length of 23 & 25. I'm only smart enough for the solution I currently have...

I have an O(n) solution that works for every single string except it sometimes fails for those with a length of 23 or 25. Every other string length works! So frustrating!!! It will work for all other string lengths including 26 and all odd #s.