Is it actually good to write simple and direct solutions for CF problems?

Правка en1, от MedMdg_MOI, 2022-12-31 15:37:25

Many of you might disagree with me, but writing simple and direct solutions might be very dangerous and risky! With thousands and thousands of submissions and tens or maybe hundreds of contests, a total of more than 100 000 correct submissions will be made for the same problems as the one you solved; And with many of them being direct and simple, there is no way that no one will have a submission that is close enough for yours to be considered cheating by the system! That is exactly what happened to me yesterday after the "Goodbye 2022" contest. After failing to finish the solution to problem E before the contest is over, I was surprised by Codeforces system sending me that: "_Attention!_ __ Your solution 187304477 for the problem 1770C significantly coincides with solutions medmdg_MOI/187304477, Gman-343/187345410. Such a coincidence is a clear rules violation. Note that unintentional leakage is also a violation. For example, do not use ideone.com with the default settings (public access to your code). If you have conclusive evidence that a coincidence has occurred due to the use of a common source published before the competition, write a comment to post about the round with all the details. More information can be found at http://codeforces.net/blog/entry/8790. Such violation of the rules may be the reason for blocking your account or other penalties. In case of repeated violations, your account may be blocked.". I checked his code and compare it to mine, and they were actually very similar. Luckily, I was the first to submit so I was only accused of leaking but apparently, for him, they rejected all off his submissions. I don't know if that happened to any of you before, but the only way I found to avoid that occurring again is to write complicated solutions for any mid-difficulty problem.

Теги leaking, cheating, gman-343, goodbye 2022, 1770c

История

 
 
 
 
Правки
 
 
  Rev. Язык Кто Когда Δ Комментарий
en2 Английский MedMdg_MOI 2022-12-31 17:40:17 122
en1 Английский MedMdg_MOI 2022-12-31 15:37:25 2026 Initial revision (published)