That can make some sense: feel free to suggest if you have something you would have added either in the description or in the comment in the template code.

Hi Giacomo, can you please take a look at an issue report by JNaftali above? I'm not sure I have enough experience to put it right.

Ruby methods are not first class values, so explaining that the 'k' argument will be given as a proc that takes the 'experience' array as a parameter would have made this problem much more clear to me.

Thanks for the input.

Should be fixed now.

The table issue seems to have been fixed. The tests still don't seem to be testing for what they should be - screenshot at http://imgur.com/a/ANnas of the original issue I posted about (tests for encode + decode are actually expecting the encoded version)

Some corrections made, can you try again?

ruby, sorry for not specifying. fyi there's also a typo in the alpha table - there's an entry with a key of => that should have a key of :

What language are you using?

Not sure if this is what hksong is referring to below, but:

Randomized Encode-->Decode
Should return the original input value: "KDETTQDOLK $@9V96G !"ML3B3"
Expected: "10101110111000000000000000000000", instead got: "KDETTQDOLK $@9V96G !"ML3B3"

Seems like my program is performing as expected - decode(encode(string)) returns string - and the test is testing for the wrong thing..