6 kyu
Seagull Snapshot Festival Obsession
114 of 187Rusca8
Loading description...
Strings
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.
It was absolutely fantastic! I really enjoyed it—thank you for your hard work! 🎉👏
Quite a difficult kata although it looks very easy at first.
I can't see your solution, Ahmet. Have you submitted it yet?
Hi there, yes of course I already have, you can check it out if you'd like to.
When I hit your 'View Solution' button, I get this message: 'There is no solution to show.'
Maybe he solved it in a different language than you? He used Python and you Javascript.
The "View solution" button does not work well, unfortunately :(
Hey my friend Hobovsky! I see this might be an issue. 🤔 Chrono79 suggested that maybe the difference is in the language—he used Python while you used JavaScript. Could that be the reason? Hopefully, ahmet_popaj can help us figure it out!
Yes, ahmet solved it in python, so you will not be able to see his solution unless you also solve it in python (and make sure python is the selected language at the top of the page).
Oh, so that's how it works! Cool—thanks for clearing that up!
Yes, exactly.
PHP translation
Kotlin translation
Merged! :)
TypeScript translation
JavaScript translation
Nice! Thanks a lot :)
Just merged them.
А можно нормально условие задачи объяснить? при каких условиях и как должна быть показана камера? Вот реально влом каждый случай по отдельности разбирать и искать закономерности по ошибкам. В примере одно, в тестах другое, автор имел в виду третье. Там с точками, здесь без точек, тут скобки вплотную, здесь на расстоянии. Ну что за Х?
This kata is not 7kyu, attempting to approve it at such rank for the sake of the competition is outright bogus
I call BS on that statement, 7 6kyu votes, 5 7kyu votes.
If it's translated to other language where the "
·
" string length is not 1, it will not be a 7 kyu.A bit too difficult for a 7 kyu, I agree.
I think, ejini, you're being hostile for no reason. I chose my guessed rank way before knowing anything about that competition, based solely on my experience solving 7kyu and 6kyu recently. I have no idea about how the final rank was assigned, neither about weateher this kata has ended up on the suggested competition or not. And also it seems almost half of the people that made it thought it was indeed 7kyu.
If anyone with power to change the final rank thinks it should be changed, feel free to do it. I for one can't even see the complete list of perceived difficulty votes.
The ranking votes are in the link below, if you're curious:
https://www.codewars.com/api/v1/code-challenges/663fe90a04bdcc6db4c091b9/assessed-ranks
Yeah, it's a six at least. My best guess is that people ranking kata's are mostly high ranks that tend to underestimate difficulty. I've solved 4kyu's that were easier than this one.
Is there a way I can bump it up to 6 though? Or is it some admin thing?
@Rusca8, I don't think ejini was hostile against you, because you definitely have no fault, but against the person (no one knows who) who approved the kata as 7 kyu, even though there were more votes for a 6 kyu rank. Nothing to do now, as kata re-ranking does not usually happen.
Sure you can see who approves a kata. The user is listed as contributor. I approved at 7 kyu. But worry not, I'll leave approvals to other users from now on. I'm sure you guys can do a better job than me.
@dfhwze, I was not intended to be hostile, nor towards the author. I was just pin-pointing out the likelihood of this kata being under-ranked due to the discussions arised in Discord.
Again, based on the kata average assessed rank, the number of up-votes, comments and on-going discussion in discord, majority of the community agree it being an outlier to be approved as 7kyu.
OTOH, I would not raise another issue since I would not want to create any more fuss amongst the author and other contributors. I've already asked an admin to chime in and make the final wording, kudos ^^ !!!
Maybe the admin can push it up to 6kyu then. I would indeed prefer that the rank properly matched the perceived difficulty.
Thanks for stepping in and managing the discrepancy! We'll see what the admin decides.
Hi all, I'm going to go with the democratic approach for this and say 6 as it has more votes (per api call above). If someone needs me to change it to 6 let me know.
@dfhwze I personally think that you are doing a great job contributing and overall, so I didn't mean to be rude, sorry if that's what it sounded like. And I am sure that not too many people can do better than you. :) I just consider that this particular kata is probably a little better suited for 6 kyu, but also not too far away from a 7 kyu rank.
"..........se"
,"l.........."
and similar edge cases don't make much sense, as they result in an "empty" view.Missing tests of the thin scenes (less then 11 chars) with a seagull in it (in the middle or partially outside on the both sides)
Woah, you're right. My own example solution wasn't even accounting for thin but with a seagull, even if the kata description explicitly asked for it.
I've added now fixed and randomised tests for that, and fixed my own solution. I guess it may break some of the solutions by other people too, if they too didn't account for it. Not sure how codewars handles that.
You should really add some of those test cases (definately some from "should wait on too thin scenes") to sample tests as well.
Excellent kata
Thanks a lot! It's my first time writing one, just got authoring permission :)
Would you like your kata to take a part in the EPIC Challenge? I think that using a festival celebration as a theme, it qualifies. Should I note it down as one of the entries?
Hey! I didn't even know that was a thing.
Yes I'd love to enter that challenge! Do I need to do anything from my side? Also, do we need to wait for the kata to be approved? It's still in Beta now.
Missing useful assertion messages
Should shuffle the empty test cases with the seagull snapshot ones to prevent users from hardcoding the first N empty cases in random tests
That's a really neat point I hadn't even considered.
I thought about mixing and randomizing those, but didn't bother cause I thought it wouldn't make a difference, specially since it meant coding a way of making sure there'd be at least a bunch of each type.
It makes a lot of sense, though, the possibility of hardcoding the loophole.
I just republished a new version of the test that takes care of that (and also I made sure that there aren't always exactly 10 empty ones).
Thanks for the suggestion!
What kind of assertion messages would you expect?
I'm seeing that it already returns both the user attempt vs the expected one.
What is missing is input of the failed test.
I've added now the input on the message= argument of the test assertion.