Pretty funny. I liked it.

Very interesting and enjoyable. I already had the knowledge I needed, but some "outside the box" thinking about boilerplate code did it for me.

Virtually identical to Sudoku Solution Validator for a lower kyu cost, however enjoyable

Tests seem garbled in Java. According to the test criteria, expected string is:
"Ths wbst s fr lsrs LL!";
Testing with a simple .replace produces the following output in console:
"expected:<Th[is website is for losers LO]L!> but was:<Th[s wbst s fr lsrs L]L!>"

Thank you, that helped. Pretty pointless though if you ask me.

Traceback (most recent call last):
File "main.py", line 3, in
test.assert_equals(RomanNumerals.to_roman(1000), 'M', '1000 should == "M"')
NameError: name 'RomanNumerals' is not defined

Why is that variable being used? I am not using any classes for this, why does it suddenly appear during attempts?

Very poor description of the kata. Creator should use less space for the setting and more for actual conditions. Took a lot of guesswork to figure out what needed to be done.

Very enjoyable. For complete newbies (like myself), if you do not know how to tackle this without bruteforcing, find out/google dynamic programming.

That comment is almost a spoiler :P

A challenging kata, but also quite fun. Since I have very limited mathematical background (and it's been quite a long time since I've been to a math class) I had quite some trouble understanding the premise of the exercise. I think it would have a very beneficial effect if a broader explanation were to be included. What I mean by that is, for instance, to illustrate how factorials can be broken down, i.e. that for 6!, that is [1, 2, 3, 4, 5, 6] we can break down 4 and 6 into [1, 2, 3, 2, 2, 5, 3, 2]. I've had somebody more familiar with factorials illustrate this to me and this made the whole thing click and I went from there.

A very thoughtful kata. Can definitely be completed in Python without any hardcoding. As a beginner, this was quite challenging and a welcome refreshment from the usual problems regarding exceptions in coding, this time focusing on optimalisation of less complicated code.
My initial code passed the test cases but timed out on the real examples. It was pretty clear to me which part of my code needed optimalisation. It may help if you think what's bogging your execution down, then start on making it faster and less redundant.