Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Oh, I see now! I didn't know that one can parse the submitted solution this way ))) Thanks!
Hello, thanks for the link, but unfortunately I can't figure out how to use it :) Is this a hyperlink? Or is it some file in your profile? How can I read it? Thanks!
Thanks! I am glad you liked the katas! As far as the imports are concerned, when I include them, some people say that it gives away the solution and the kata becomes too easy. When I don't include the imports, other people say that they should be there :) As for me, I don't like the online IDE, I usually copy the task into my desktop IDE and let it handle the imports.
Check out java 8 stream API ;)
Ok! I have changed the kata accordingly. Using reflection is also a great suggestion, I will make the change when I figure out exactly how to do it ;)
Hello, thanks for the suggestion! I will put the student class in the kata description for clarity.
But I am not sure that specifying the imports section alone will impose a strict requirement to use streams in solution. I think the best way would be to change the methods signature (replace Student array by Stream)
to smile67 - yes, you are right! ;) kata 2 is not harder than kata 1. My goal is to make a series of katas of the same level of difficulty (level 7) just to practice different ways to summarize information. Is there a better way to group katas than by giving sequential numbers?
Great suggestion! I guess, it will be the easiest way to test for using streams in this kata! Thanks
Thanks! Great suggestion!
Thanks for the suggestion! Ok, no problem ;)
I agree it's a good idea, but I couldn't think of any way to enforce using Stream API and unit test for it. Maybe you have some clue? Thanks!
Thanks! I have learned a better way to unit test IllegalArgumentException (with a @Test(expected = IllegalArgumentException.class) annotation). This is a bit prettier code ;)
Thank you, it is a great suggestion!
Thanks, great suggestion!
Loading more items...