Resolved?

Check it out now if you have the chance, I think it flows better with some rewritten sections descriptions moved around. Thank you for your input.

I believe that part is handled

Hi,

I just "stumbled" again on your kata.
And reading this:

I added a good amount of clarity to the description

...while I just wrote this to another user, I'm thinking that the middle part of the message might be useful to you too ;) (in the case of your kata, I'd tend to say that most of the final section of the description should be somewhere else (as in: "before the examples"))

cheers

Fixed. Let me know if you like how it looks now! I appreciate the suggestion.

Description should not use h1 to denote section headers. h2 is better, but I personally think h3 looks the best.

Changed return type to always be (float, float)

I added a good amount of clarity to the description, let me know what you think.

Added a lot more random tests, shuffled balanced/unbalanced.
Changed return type to always be (float, float)

At first I thought the criteria for a 'bad rung' was that it was not symmetric.

... :/

• nothing is explained in the description (edit: mmmh, it's actually said in the description, but a bit convoluted...)
• that's exactly what I thought after looking at the sample tests

CCL: the description of the task is really insufficient...

To add to this, ideally something that looks less like a real ladder shape. At first I thought the criteria for a 'bad rung' was that it was not symmetric.

Hi,

it would be (very) good to add an example to the description of a problemtaic ladder. After I read 3 times the description, I still don't get what my goal really is and how to proceed.

cheers

• Too few random tests
• Balanced/unbalanced random tests should be shuffled
• Returning multiple types (sometimes float,int, sometimes float,str) is bad practice

Having multiple output types is bad.