Maybe instead of calculating the factor by dividing 1 / s I should have done it as in other solutions that first multiply the velocity by the number of seconds in an hour (3600) and then divide that by s. We'll never know, I'm never looking back on this answer this is now part of my dark past.

I don't deserve the points. I had to attempt it like 12 times for the random tests to pass.

Given that the task is very specific I'd say it is, as it is performant and the code is readable.

If you had to, for example, generate neighbors up to a variable distance n received as a parameter of the function, that would be a different story.

Comparing the bytes directly! Clever

The go version is missing the package name at the start and thats causing a weird 422 server error, please add it:

package kata

Nice, this one actually works with UTF-8

@Javatlacati Dart

Oh, thanks a lot! Makes sense

Thank you!

Well there are multiple reasons. Whenever I can I use const. If I need to reassign then I use let. But I don't use bar anymore, as it can be problematic due to broader scope (functions instead of blocks), hoisting behavior and in the case of constant values, reassignability. I found the explanation on this link to be similar to my reasoning.

https://medium.com/javascript-scene/javascript-es6-var-let-or-const-ba58b8dcde75

Cheers!

You need to manually create them

Wait WHAT?