yes, this solution make is great

yeah, it's crazy educational to read how other coders solved the kata so you can figure out ----> WTF

Just read the f..riendly manual

well, you did better at code formatting the first time... x)

I know why, but I won't tell you. Most important thing for a developper: learn how to properly debug your own code. But I can give you some advises:

• if you code on an IDE, use the debugger to go through the execution of your code step by step, to see how every variable evolves
• if you don't and work directly on cw, use the "old tools": System.out.println(...) and print what you need at appropriate places

And I'd finally suggest that you apply your code to that input: "aaaaaaaaaaaaaaaaaaaaaaaaaa"... ;)

errr.... before assumming things like that, be sure about what you're saying. Or you'll be the "whoever" who didn't read his log correctly: this input expect false, not true. The tests in java are perfectly correct (just look at the number of completions...) => debug your code properly, that's all.

note: (generic message)

Seems you're "rather new" to cw, so here are some general guidelines about the comments:

• Issue: problem in the kata itself (description, wrong tests, wrong internal solution...)
• Suggestions: well, I guess that part is clear
• Question anything else that is related to you having a problem solving a kata -> that's you, currently.

When you post issues:

• provide ALL the useful information:
  • language
  • input
  • outputs (actual expected) when relevant
  • error message when relevant
• check, DOUBLE check that this IS an issue, meaning that the problem is in the kata itself and not in your code. If it's in your code, post rather a question
• if you pass this step, you still have to prove/explain what the issue is (and if you can provide fixes, it's even better)

When you post a question: well, most of the above apply too x)

Not an issue => closing.