Interesting Kata, thanks.

Easy and fun!

This seems super complicated for 7 kyu.

JS description for cases that the net won't break should be Infinity

JS approved

JavaScript translation

TypeScript translation

I met this issue as well. More interestingly, if you calculate the difference between your answer and the correct (presumably?) answer, they always differ by a number that has a high power in 2 when prime factorized, like 1736704 (2^15 * 53) or 16384 in the case of IMMUNOELECTROPHORETICALLY, which is 2^14.

Since the clan has already been grouped, if you partitioned it, each of them will be unique

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.

This is the correct "best practices" solution.

Sorry, got to do this. With my background as a merchant marine this just hurts too much.
With a breakneck speed of 90 miles/ hour (which we call knots, btw, o you heathen Kata author) at open sea, any fishing vessel - forget that: any vessel - would be reduced to chopsticks. Your function could be a lambda without arguments and only one return, like this:

find_time_to_break = lambda who_cares, pointless: 'Around the time you will interact with the first wave with an amplitude over an inch and a half, crossing your path.'

Guess what? This doesn´t work and it's the only right answer.

Amazing😳