Earn extra honor and gain new allies!
Honor is earned for each new codewarrior who joins.
Learn more
  • 14909989?v=3

    Still bad design.

    @cliffstamp: For the record, bad design is kata quality issue, and I won't bulge on this one. If you don't agree, go complain on the repo.

  • Profile pic
  • Profile pic

    Description updated again when random strings of nonsense all passes the reference solution which is very basic. This is an ~8 kyu kata because of how restricted the inputs have to be to be parsed by the refernece solution.

  • Profile pic

    Since this is a vital point to you, I'll make up a big imaginary scenario and add it to the description.

  • Profile pic

    The specifications are part of an imaginary story, a guy on a key board, it is imaginary, they are made up, you can make up any you want :

    • the machine malfunctions and sends no signal (undefined)
    • the return message ("bad input") on an empty string is because the guy wants to know when the modem crashes

    and so on for any specification you want.

    It doesn't correspond to reality, it is modeling a fake situation with a set of arbitrary rules to test your ability to handle them.

  • 14909989?v=3

    Re-raising the issue below. Bad design is an issue.

  • 14909989?v=3

    it is just a specification

    Bad specs are still an issue. By tomorrow you'll be saying "this kata requires intentionally bad specs but they're the specs, so it's not an issue". It is.

  • Profile pic

    In typical algebra for beginners it is common to write things like 1x^1 to reduce cognitative load, however kata don't need to mirror ideal utility, they just need to pose problems useful to learning how to code.

    Empty string is considered an error, because it was deemed to be an error, it isn't necessary to make up a back story, it is just a specification, however if you want one :

    "Sometimes Mr. Dicken's modem fails and all his hard work is lost and the message is wiped ... oh noes! In this case (if you receive an empty string, null, undefined etc ...) return "Input Error" so Mr. Dicken's knows he has to try again!

  • Profile pic

    Description updated.

  • 31668662?v=4

    You also need to account for any entry errors that Dickens might make

    Either explain what is considered a mistake, or remove this requirement altogether.

  • 17622328?v=3

    raising issue about lack of random tests before this gets approved

  • 13985748?v=3

    Thanks, smile67! I will definitely check out your katas. I always love a good brain-teaser!!

  • 15776046?v=3

    Good kata, thanks! If you know math quite well (as you wrote), you can try my three math katas (new to JS? ...C# not?);-) One is easy, but the "LS" kata isn't solved since weeks:-)

  • 13985748?v=3

    Thanks for catching that. I had inserted some Example Test Cases, but they vanished for some reason.

    Also, I am not sure how to create random test cases...

  • Profile pic

    You should provide at least one Example Test Case to make it clear what input and output are expected.

    Also, random test cases would prevent easy cheating attempts.

  • Loading more items...