The way the results are displayed makes it challenging to troubleshoot your query. I agree with Voila that it would be better to have the traditional SQL test assertion data display. Thanks and all the best!

Thank you for the prompt response - the error was in my query not in tests!

Hi!
I believe that there might be an error in the 'Edge Test Case'. The only employee present in that data set is above 40 (born Aug. 2/1983) but the solution seems to require the employee to be between 26 and 40. Could you please look into this?

I can see that there is a negative opinions about this approach but I am still quite new and still learning so I could someone please explain how this approach even works? I'm not really able to see the connection between how i's reversed order matching the reversed order of n produces the right result...

Thank you in advance for your time and help!

I can see that there is a lot of negative opinions about this approach but I am still quite new and still learning so I could someone please explain how this approach even works? I'm not really able to see the connection between how i's sorted ascending order matching the reversed order of n produces the right result...

Thank you in advance for your time and help!

Same issue in Ruby...

Interesting but for me it was quite difficult and I think it's closer to a 5kyu or 6kyu.

Nice one but in my opinion it should be 8ky...

Name will never be null in this situation so it's unnecessary...

Thanks!

In C# the description says that "Array/list will always has even size":

• Firstly, there is a typo, should be "will always have..."
• Secondly, all the arrays in the sample test have an odd number of elements

In C# there is a typo. The instructions have a variable called youSpeed and the actual code has yourSpeed.