Makes me think of FizzBuzz enterprise edition: https://github.com/enterprisequalitycoding/fizzbuzzenterpriseedition
Satire, im loving it

what? -Joe Biden

In the C# version of this kata, one of the hidden test cases (TestException) appears to access Current after MoveNext() has returned false. According to .NET conventions, this should result in an InvalidOperationException, but the kata description does not mention this requirement.

This behavior is easy to overlook, especially since most other test cases pass without issue. It would be helpful if the kata description explicitly stated that:

Accessing Current after MoveNext() returns false must throw an exception.

Adding this note would make the expectations clearer and help prevent confusion for users implementing a valid IEnumerator in C#.

Could be a suggestion, not an issue.

This is not an issue. This is a puzzle.

Maybe this misunderstanding comes from not everyone being aware of what a "puzzle" kata is meant to be on Codewars. It could help to update the kata description to clarify that this type of challenge is intentionally designed to encourage thinking outside the box and sometimes outside conventional best practices. That way, users can approach it with the right expectations and mindset.

Thank you for your honesty. However, we're not going to remove this challenge just to suit individual comfort. The spirit of this platform is to encourage learning, exploration, creativity, and unconventional thinking - and since this is marked as a "puzzle", it's meant to challenge those very qualities while keeping things fun and engaging.

Codewars is not only about education. Many people are also here just for fun, solving unique and interesting problems that they would not likely find in the real world, and to gain really deep understandings of their chosen language. Who are you to say that these people should not be allowed to enjoy problems like this, just because you worry it might teach bad practice?

I partially agree with this sentiment but one thing worth to notice is that this challenge can be solved in an interesting way, which does not involve reflection, but abusing weaknesses of RNGs.

TBH - this is NOT a Kata we should have here. Especially not in Kotlin. We do not want to teach any dirty reflection/magic tricks like this. This is about proper coding techniques. And on top of this: who translated this horrible thing to Kotlin? That makes it even worse! Please delete this Kata.

What a horrible way to write code in Kotlin. Who did this???

Nice kata...

Great kata to have fun with...

Python, probably others:

• No random tests
• Incomplete coverage of spec

Python new test framework required