Beta
Where do they meet?
Loading description...
Date Time
Algorithms
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
Fixed tests and random tests have different input date string formats:
More crucially, why pass in date strings when passing in a
Date
object is infinitely more appropriate for the task? This is just bad kata design.It's funny. When I saw the results of these testcases:
and
I have to create a special 'sad LOL' icon for this one... o.O
As for the first case I don't know what happened, but when I copy pasted your times and used it on my solution I got 'between Montpellier and Nice' as well. Any idea what could have happened there? You know the system better than I do...
As for the second case - You are totally correct. It should be exactly as you've described. I'll have to figure out my error... In the meanwhile I'll unpublish the kata.
The problem was with my code. I have built a way-too-complicated solution that did not account for the minutes, instead used Date.getHours() to set new times. Not a good idea. I've changed my solution altogether, and now it should consider every single minute (but not seconds). I've also changed the difficulty to be a 6 kyu. I'm not entirely sure about it, so if I'm wrong feel free to change it.
Thanks again for your feedback! :)
It seems that it's still incorrect in the random tests:
and
I'm afraid this time my fault is different.
The drive time to montpellier was 9.5 and 10.5 in the starter code but not in my solution. I forgot to update it earlier (which was another issue) but as I went over the kata again to fix the issue you've raised before I've found it and updated it as well to 9 and 11.
That half an hour accounts for both errors.
I am terribly sorry for this and again thank you for your feedback. I can only hope that someone who has created so many katas himself can forgive my noob problems. I'm trying to create some standard process for myslef to create a kata that'll be worth people's while with as few hiccups as possible, but I'm still learning a lot so obviously I'm missing some things here...
There's a syntax error (missing = ) in the JS starting code: "let meet(bus1, bus2)"
Right, thanks! :)
Fixed.