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://mirror.codeforces.com/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](https://mirror.codeforces.com/contest/1770/submission/187345410) and compare it [to mine](https://mirror.codeforces.com/contest/1770/submission/187304477), 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.↵
Edit: I was compiling using [jdoodle](https://www.jdoodle.com/online-compiler-c++/), does anyone know anything about it?
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://mirror.codeforces.com/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](https://mirror.codeforces.com/contest/1770/submission/187345410) and compare it [to mine](https://mirror.codeforces.com/contest/1770/submission/187304477), 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.↵
Edit: I was compiling using [jdoodle](https://www.jdoodle.com/online-compiler-c++/), does anyone know anything about it?
