Sorry if this sounds stupid, but: What's the exploit in your solution? I used a similar solution and thought it was the intended one.

I was mildly confused by the usage of "nd" as well. May I suggest using "stop", "final", "terminal", "limit", "endpoint" or something similar?

At the risk of sounding stupid: What exactly is your reasoning behind that, @Absurdated?

Sounds as if your solution might be getting stuck in an infinite loop.

Wait a minute. As far as I can tell, this returns "4" for center([[1,2],[3,4],[5,6]]). I was under the impression that in order to have a single center, all matrix dimensions must be odd in size, so there shouldn't be a center for [[1,2],[3,4],[5,6]]. I assume the test cases are lacking here?

I'm surprised I had to scroll through several pages of actual solutions to find this (expected) gem.

As a Ruby noob, I have to ask: Are one liners like these really common development practice? Am I just too inexperienced to read them at one glance? In my limited programming lessons I was taught that readability should be more important than conciseness.

As far as I know, using existing functionality is part of the expected and intended solution. Source: Comments on other "Enumerable Magic" katas that all follow this pattern. I vaguely recall the author stating on one that these katas are meant for students aged 10-14.

As far as I know, using that is the expected and intended answer. Source: Comments on other "Enumerable Magic" katas that all follow this pattern. I vaguely recall the author stating on one that these katas are meant for students aged 10-14.

As far as I know, this is the expected and intended answer. Source: Comments on other "Enumerable Magic" katas that all follow this pattern. I vaguely recall the author stating on one that these katas are meant for students aged 10-14.

Apparently, as far as I can tell from reading comments on similar katas, this is valid and intended. The author's reasoning seems to be that these are supposed to be beginner's katas, intended to emphasize the importance of looking at the standard library.

This needs more open test cases and / or examples. For a non native speaker it's hard to guess the correct behaviour from the current test description.