Thanks for this great commented solution. :)

I'm very new to Ruby.
How does this each_byte handle the requirement to handle odd/even chars differently? :o

Nicely done, I couldnt figure out how to get args to go in one implicit return.

I really like this solution.
It uses common well known funcitons and still results in short understandable code :)

Very easy to understand and short solution!

When I started out I was at a level where approx 7's in PHP / SQL got me around.
Willingness and ability to learn is more important than actual skill for that first job! :=)

Hi,
Didn't find how to report a cheat solution so I thought I would write here.
The solution in Ruby by Poilon is clearly not trying to solve the actual problem but "cheat the way through".

I don't know enough Ruby to understand how it works but maybe it can be prevented with tests.

I'm also having troubles with the Ruby random tests.
Just learning Ruby here so not so sure if it's that or the description.

Testing for [36, 52, 76, 53]

• Expected: [53, -1, -1, -1], instead got: [52, 53, -1, -1]

52 would be the closest number to 36 and not 53.
It feels like it's suddenly not the closest number but the second closest.

That should probably be a section in Kata Best Practices.