7 kyu

Simple Fun #107: Company Bot Strategy

141 of 251myjinxin2015
Description
Loading description...
Puzzles
View
AllIssues2QuestionsSuggestions1Show Resolved
  • Please sign in or sign up to leave a comment.
  • Just4FunCoder Avatar

    Your output will be considered correct if its absolute error does not exceed 10-5 compared to our tests.

    However, approximate equality check is not enforced in :-

    • C#

    • JavaScript's sample & fixed tests

    • Ruby

  • ejini战神 Avatar

    C# generate warnings -> tests/Fixture.cs(120,15): warning CS0219: The variable 'passed' is assigned but its value is never used

  • user9644768 Avatar

    Ruby translation should be updated 3.0, see relevent information here: https://github.com/codewars/content-issues/wiki/List-of-Ruby-Kata-to-Update

  • JohanWiltink Avatar

    It's a fun little kata, but the description only had me confused, I figured it out from the examples, and in the end it felt like too simple a task for two whole pages of description.

    I'm afraid the story, which is nice, doesn't add a whole lot to the kata, except possibly confusion. I had visions of Robot Wars, but you don't really train those, so that wasn't it. What it was seemed academical really, when going from the examples worked first try.

    I know it's simple fun, but shouldn't the description also be simple then? (Or more fun. In that case, I vote Robot Wars is more fun than CodeFight Company Bot CodeFights.)

    • myjinxin2015 Avatar

      If my description is too short, I will get an issue report: the description is not clear. If my description is too long, I will get an issue report: the description is too long to read. So what should I do? ;-) And how short is really short, how long is too long? Describing a short text does not mean that the problem is simple, and vice versa :] Compared to these, I am more concerned about whether my kata(I mean some difficult kata, it seems that few people try) can be approved within 10 years :(

    • JohanWiltink Avatar

      I see your problem. But surely there must be some middle ground?

      And I do think there's some relation between the difficulty of the kata and the length of the description. If a horribly complicated problem reduces to "add a to b", that just won't feel right. Conversely, if two lines of description make perfectly clear a complicated problem which is going to be a major programming project, that will not feel like a problem. But if you need a lot of specification for that complicated problem, that's also not a problem.

      I guess this comes down to the description having to be no longer than the complexity of the solution, though it can be shorter. (This compares apples to oranges, but I think you'll get the point.)

      Puzzles may be the exception to this; there the challenge is reducing the problem from the description. But this one doesn't seem like a puzzle.

      Do you see my problem?

    • myjinxin2015 Avatar

      Your comment let me remembered my Thinking & Testing series. To be honest, the kata description is not too long. It's even shorter than your comments ;-) In order to meet your wishes, I will make a special kata for you.