I am also encoutering this issue. . any advise?

Yes, I also thought the same think. This solution absolutely is using string operation.

Regrettably we cannot have that part of the description different from language to language, so I fear we will have to do with the test cases below.

Oh, to think that me and 6 of my group were at Makers just on Thursday ;)...

Otherwise, you could come to this upcoming event hosted by a very cool guy (shameless self-promotion :p), again, with a good part of my group.

As far as the use of a method instead of a function goes, to me is more a matter of personal preferences, plus of course ahdering to common practice with the same dev team. Btw, you certainly seem to know your Ruby, probably more than me, so there is little else I can comment on :).

Hi Andrea, the problem is that you do not manage the path incrementally: look at the href for the last step and condier that confidential should indeed be inside important.

Hope this helps :)

P.S.: oh, you are London-based too? You should definitely come when we do the next katathon, some training or something similar :D

This is the tests telling you that your solution is too slow when run a lot of times on big numbers.
You'll either have to find a way of speeding up your current algorithm or find a different one which is faster.