Updated. Let me know if I've missed something - used your ref to make such changes.

Updated with random tests, although not sure if it makes sense, given the all possible inputs are tested in "All Months" test case.

I think I messed up where the test/example belonged. I think it's updated now (not sure, as it's my first kata translation).

It belongs to dart:core (at least since the supported version, which is 2.8.0)

For the Dart translation, I think auto-importing dart:math library is misleading.

Added a Dart translation!

Oh, I'm a beginner programmer (working about 1 year) and I couldn't agree more on the requirements when dealing with people, you're absolutely right about it and sadly, it will never change. People in general will always change their minds whenever they can, that's why I love doing open source projects and just dealing with this annoying chattering when I have to. Don't let your hopes go down tho, there are awesome places to work and they'll minimize this kind of situations.

I think you're half right. You've said things that I agree, but sometimes you just have an answer that fits your demands. You know your parameters and they won't change, but most importantly: you don't have to think about scalability on a common solution like this one.

"WAIT, are you SAYING that scalability or abstraction SOMETIMES isn't a good thing?"
Hell no, but if we would stop to think about an ideal solution for everything, we would end up stuck extra minutes/hours finding, creating or adapting a design pattern on top of a solution that is much smaller and simple.

There are a lot of higher level KATAs that need a generic or abstract code, that are full of random tests and it will break your code if the mindset is slightly distorted. My purpose here was to find the smallest and quickest solution to this KATA, I see by your answer that you aimed for a more generic solution, that's indeed better than the most solutions on this KATA, but again, that doens't make our solution - by any means - horrifying.

Really good kata! Just a little typo on the second paragraph (java): "Each robot will have a name, hit points, speed, and then a list of battle tacitcs they are to perform in order."
tacitcs -> tactics, no big deal.

I guess you're right, my bad.

The feedback on the tests aren't showing!! I don't know if it's supposed to be like this, I've never done a kata on beta before, anyway, very good and overall challenging one!