Блог пользователя SlavicG

Автор SlavicG, 2 года назад, По-английски

This is the part 2 of the previous blog, where I selected some of the comments I found funniest from the Rule about third party code is changing blog post. So, here is the compilation:

Act of coincidence
I cheated, give my rating
Never believe long code
Atcoder
Wholesome
Same person

(There probably won't be a part 3)

  • Проголосовать: нравится
  • +131
  • Проголосовать: не нравится

»
2 года назад, # |
  Проголосовать: нравится -8 Проголосовать: не нравится

Unbelievable

»
2 года назад, # |
  Проголосовать: нравится -13 Проголосовать: не нравится

'(There probably won't be a part 3)'

why? because the world ends?

»
2 года назад, # |
  Проголосовать: нравится +8 Проголосовать: не нравится

no part 3, i am crying, my life is ruined

»
2 года назад, # |
  Проголосовать: нравится +113 Проголосовать: не нравится

I think we should make the rules clearer somewhere. Not that the current rules are bad, but they are apparently not understood clearly enough by a certain part of the community, and should be more explicit. A lot of people seem to think, or at least have a tiny hope, that if they did something like discussing with a friend or submitting the same code from multiple accounts, then it is somehow okay, and the only blockable offense is directly copying the code from someone else. The "rule about third-party code..." blog has hundreds of comments filled with weak excuses and there are hundreds more scattered around round announcements, editorials, author PMs and even completely unrelated blogs. If even 20% of these people could be dissuaded from writing such comments, I would consider it a great success.

For example, I would explicitly write the following somewhere:

  1. Discussing a problem, even implementation or "general approaches" during the contest counts as cheating.
  2. Submitting the same code from multiple accounts counts as cheating: if you started participating on one account, do not switch to another account.
  3. Unintentionally leaking your code counts as cheating: it is your responsibility to make sure your code does not reach the hands of cheaters.
  4. If you are guilty, writing an apology or saying that "this won't happen again" will not grant you an one-time exception or restore your ratings.
»
2 года назад, # |
  Проголосовать: нравится +3 Проголосовать: не нравится

I genuinely felt bad for the wholesome one(((

»
2 года назад, # |
  Проголосовать: нравится +47 Проголосовать: не нравится

It is even funnier than trolling them in Telegram :)

Thanks for this blog! Had a very good time reading this.

»
2 года назад, # |
  Проголосовать: нравится +5 Проголосовать: не нравится

Ha! Cheaters in Atcoder will also be banned. See this post.

  • »
    »
    2 года назад, # ^ |
      Проголосовать: нравится +8 Проголосовать: не нравится

    Of course, but they will make the excuse "we came from Codeforces". That's how things work.

»
2 года назад, # |
Rev. 4   Проголосовать: нравится +19 Проголосовать: не нравится

If you read the cheater blog you CAN find other funny ones!

Dumb debugger
Reason: Don't know
Disheartening
Unfair
Curser downvoted this
it IS unintentional! So give back my rating!
Just experimenting
  • »
    »
    2 года назад, # ^ |
      Проголосовать: нравится -8 Проголосовать: не нравится

    A lot of these comments tend to repeat, once you see the same comment a hundred times, you tend to find them more annoying than funny. That is why I think the author decided not to include them.

    • »
      »
      »
      2 года назад, # ^ |
        Проголосовать: нравится +8 Проголосовать: не нравится

      The most prevalent ones are like 'I didn't see the rules.' So probably the second one isn't funny...

      The others mostly aren't so repetitive though. The experimenter one cracked me up.