SlavicG's blog

More funny cheater defenses
By SlavicG, 2 years ago, In English

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)

  • Vote: I like it
  • +131
  • Vote: I do not like it

»
2 years ago, # |
  Vote: I like it -8 Vote: I do not like it

Unbelievable

→ Reply
»
2 years ago, # |
  Vote: I like it -13 Vote: I do not like it

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

why? because the world ends?

→ Reply
  • »
    »
    2 years ago, # ^ |
      Vote: I like it +44 Vote: I do not like it

    Because I can't find enough funny comments to make another part.

    → Reply
»
2 years ago, # |
  Vote: I like it +8 Vote: I do not like it

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

→ Reply
»
2 years ago, # |
  Vote: I like it +113 Vote: I do not like it

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.
→ Reply
»
2 years ago, # |
  Vote: I like it +3 Vote: I do not like it

I genuinely felt bad for the wholesome one(((

→ Reply
»
2 years ago, # |
  Vote: I like it +47 Vote: I do not like it

It is even funnier than trolling them in Telegram :)

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

→ Reply
»
2 years ago, # |
  Vote: I like it +5 Vote: I do not like it

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

→ Reply
  • »
    »
    2 years ago, # ^ |
      Vote: I like it +8 Vote: I do not like it

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

    → Reply
»
2 years ago, # |
← Rev. 4   Vote: I like it +19 Vote: I do not like it

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
→ Reply
  • »
    »
    2 years ago, # ^ |
      Vote: I like it -8 Vote: I do not like it

    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.

    → Reply
    • »
      »
      »
      2 years ago, # ^ |
        Vote: I like it +8 Vote: I do not like it

      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.

      → Reply