Уже давно я использую codeforces на интервью для отсеивания кандидатов.
Я часто слышу рекомендации как улучшить читабельнось условий задачи. Одна из частых рекомендаций "Добавьте примеры недопустимого ввода".
Например для задачи 1469A - Regular Bracket Sequence
Можно было бы использовать такие примеры
Неправильный ввод — слишком много скобок
1
(())
Неправильный ввод — слишком мало скобок
1
(????????????????
Неправильный ввод — слишком много случаев
1337
.....
.....
.....
Codeforces is one of the best platforms (compared to codechef or hackerearth) ... the question prompts are complete and apt ... The questions are already properly explained well enough ..
We want to be more of a coding competition rather than reading comprehension competition.
Any change that switches the focus from reading to coding should be welcome.
Also codeforces community is extremely toxic. Every blog post which is not an editorial of exceptional quality or a major scientific breakthrough in fundamental algorithmics is getting downvoted.
Автокомментарий: текст был переведен пользователем muxecoid (оригинальная версия, переведенная версия, сравнить).
Автокомментарий: текст был обновлен пользователем muxecoid (предыдущая версия, новая версия, сравнить).
Input overly longSo you are saying you dont understand simple inequalities like t (1≤t≤1000)
Maybe this part is redundant, but the part about braces in problem statement was initially misunderstood by several coders who saw it. Example would help.
Question is fine. Coder probably doesn't have much experience with competitive programming questions, and they're also probably stressed out due to interview pressure. So they messed up.
Also, it's best to keep the constraints description exactly how they're right now. It's far more easier and faster to read 1<= n <= 1000, than any overly explicit explanation. The reason the constraints are given in a simple inequality equation, is to prevent mistakes due to language differences. We got coders who speak Japanese, Hindi, Russian, etc. Simple inequality equations are best. They're well understood.
You just gain my upvote!
I do not have a statistically significant sample, but it happened more than once. You can say that I work in shit company that only gets bad candidates who can not read, but it is only part of the truth.
It is actually possible to make problem statements significantly more approachable with little extra effort from problem writers and reviewers.
Unfortunately most of our community is "it worked like this for several years so it must be perfect."
Why not add in the required clarifications to the questions for your interview process?
Honestly it will give you best ROI on your effort.
Prepare the new clarifications that would be required for your interview process, and send them to the candidate?
This way, your interview process satisfies your requirements.
That would give you the most ROI on your effort, as most likely, things aren't going to change in codeforces or any other competitive programing website. Everyone follows the same format.
Sure I learned my lesson and will add examples of illegal input in future interviews. Because it provides significant improvement to quality of problem statement. However I want to give back to the community and if I have a good idea not just keep it to myself.
"Everyone follows the same format" is simply not right. That's what topcoder fans said about impeding failure of codeforces in the past long forgotten.
Image of typical codeforces reader downvoting in advance any new entry before reading.
Yes, yes, Codeforces is perfect circlejerk. Any suggestion is evil by definition.
Ok boomer