Things like this are making me really start to enjoy learning R.
So elegent!

Description should be updated to advise that an R programme should return NA if the code is not H, Q or 9.

Changed find_intercept to find_time_to_break.
Function name didn't make sense. Solution isn't to find the intercept, this was a throwback to an earlier idea I had.

Agree. Clarified in the description. (People are going to struggle if they dont already know the range of degrees possible in a circle though)

1. Changed. Good catch.
2. Implemented float('inf'). I am concerned that this would be harder to translate into other languages. Thoughts?
3. Done. Will have a 5% chance of appearing in each of the 50 tests. If this edge case doesn't get captured, it will force a test.
4. Just for everyone to appreciate : this is not a misspelling, it's an atttempt at breezy humor. Cod is a fish, this Kata is about cod fishing (didn't say it was a good humor). Would be a shame to remove it IMO, it adds character and eases people up to a problem outside of most people's comfort zone. If this really does aggrevate people, it can be changed.
5. Good catch. Changed.
6. Slept on it and I agree. Changed.

Also, changed the random tests to between 0 and 359 degrees. ( Was 0 and 180)
Really appreciate your involvement on this Blind4Basics

Done. Can anyone advise if this would cause an issue for translations?

1. Changed (Thanks for the clarification Steffan)
2. I don't see this as an kata breaking issue? The 'hell' I did this for was that further Katas are planned. It allows for problems with >2 ships or other posibilities to be consistent in style.
   3/4. Done. Bearing has an well documented explicit mathematical/navigational definition, but added to show it is in degrees (not radians) and to define its measurement.
3. Done.
4. Now testing on the (not example) test cases. Didnt want to give the game away of when this situation happens, but totally agree.

Thanks for the feedback! Much appreciated.

You are in for a shock.
There are far far worse out there.

'Marking as resolved since this isn't an issue'
Is this some sort of social experiment?
It makes zero sense.

Shame to say, but this is hands down the most confusing kata I have come across - and there are some bizzare Katas around.
Not sure if this adds any educational value to Codewars in its present form , but nothing that can't be fixed simply by changing the description.

The big issue for me is that the description is plain wrong;
'If the amount of load is more than 2 times the standard amount of clothes, return 'Too much clothes''
What the tests expect is;
'If the amount of clothes is more than 2 times the standard amount of load, return 'Too much clothes''

Seems a really abstract idea too, what is load even meant to mean? I would guess max capacity of the washer, but it changes in each test.
Why would having less clothes than the load break the washer? What is the standard amount of clothes? It's really not intuative - especially for a beginner Kata.

Isn't the beta process meant to catch things like this?

Thanks so much, this makes perfect sense now.