Clever - Maybe because your solution was the obvious one and this has fewer lines of code and leverages already available methods?
Best practice? Eh, maybe not, if I were using large data sets this obviously isnt ideal, but for small values of n like this challenge, it doesn't make a lick of difference.
If I wanted something more efficient I would have used a different approach, but it's a kata, not a time sensitive app.
If the kata wanted a CPU efficient solution it would have run very large data sets as part of the final tests.
Clever - Maybe because your solution was the obvious one and this has fewer lines of code and leverages already available methods?
Best practice? Eh, maybe not, if I were using large data sets this obviously isnt ideal, but for small values of n like this challenge, it doesn't make a lick of difference.
If I wanted something more efficient I would have used a different approach, but it's a kata, not a time sensitive app.
@g964 do you have anything else to say. all you say is how many have passed. Many are stuck in this kata.
Wow youre a douchebag
Thanks for finding this issue! I used #reduce incorrectly
For 1610 guys result is 80.
As you can see at the top of the page 7365 guys passed the kata and 504 in Ruby.