Discussing CodeChef's problem on other platforms?

The Long contest at codechef has been a success due to its challenging status but of late during the last 2 competitions , I found out that a lot of lot of people asked the questions as it is on websites like stackoverflow, stackexchange, topcoder and codeforces while the contest was still on . Nevertheless everyone knows that one could get a whole lot of good answers in these websites and because of that 500 people more view that post within 1 day or so . This really pisses those who do by themselves . Therefore, the admins should have a look at this issue because its growing exponentially with every competition and could well diminish the hard work put up by the psetters and testers and its integrity.After all there are whole bunch of solutions available after the competition then why do they need to cheat during the 10 days?

11 Likes

I have also seen several questions on Stackoverflow.com related to the live contest on Codechef.

One example : integer overflow in matrix exponentiation <-- This contains the exact base matrix that I constructed for CHEFWD (Sept 2012). The question was asked on Sep 8 2012. (I might be mistaken)

This is very annoying. I was going to comment, that it is a problem from live contest and shouldn’t be answered, but someone else did it before me.

I don’t think Codechef can do anything about it. Cheating is unfortunate, but impossible to prevent.

So it is best to just ignore it.

6 Likes

I, too, have came across some questions on stackoverflow and stackexchange that are EXACTLY the codechef’s problem question, but, with minor changes in the statement, maybe in the hope people wouldn’t notice it…

But, in fact, with such an awesome work from the problem setters and testers and with the best editorials I’ve ever read available after the contest, that’s not the way to go if you want to have a successful participation in CC long contests…

From my own experience:

I became friends with one person who joined the FB page and is also more or less at the same level of expertise as I am (probably a bit better :)) ), but I can say that only speaking about the problems and literally “digging” trough websites like cplusplus allowed me to increase my expertise A LOT and did it in a way that no other website could do! Once again, thanks to the community :smiley:

@everyone who googles for solutions: Trust me, you can get happy if you are provided with an answer for your question and get an extra AC, but seeing yourself progressing and passing from solving only 1 problem (like I used to do) to being able to solve around 2/3 more consistently and learning new ideas on your own is MUCH MUCH more valuable!

And regarding the problems you were unable to solve during the live contest, if you read the editorials along with setter’s/tester’s solutiions and try to implement them on your own you will gain a lot more :smiley:

This community is doing an excellent job, all we have to do, either as contestants or setter’s or tester’s is seize it and hope that it stays up for many more years to come :wink:

Also, successful participation in codechef is being able to solve a problem that you were previously unable to solve!! A tip: if you read editorials carefully, you will see that there are usually around 1-2 problems that are simply implementation related and that require only some statement understanding and careful implementation!! Do those on your own and you will gain more confidence for future contests and tackling harder problems!

There are no shortcuts :wink:

Bruno

14 Likes

My opinion is that cheating is the way to hell…

First of all one have to realize why is he/she doing contest programming. You can cheat in Codechef long contests, there is a lot of time, but on the other hand short contests are more important. Not only those on CodeChef, but others as well - Google Code Jam, Facebook Hacker Cup, TopCoder SRMs and TopCoder Open…

I’m angry for a while when I find that someone is cheating, on the other hand I know, that I’ll always beat such coder in short contest…

4 Likes

At first Codechef had linked all of us with a great platform to learn many unknown things with respect to Algorithm theory as well as their implementation.I believe that if any one asked the questions of Live Long contest in the Knowledge sharing websites then it will surely not going to help that person in any way because getting the better rating post to the competition will give him a pleasure of achievement in terms of Numeral’s but not in terms Knowledge.At first he must realize for what sake he had joined in the Community whether it is for improve his Knowledge along with rating or to just to improve his rating with out any Knowledge improvement…One thing i can really say if any body had cheated and obtained a good rating it will surely last for very less days but if any body learned from contest to contest then today his rating may be low but one day it will surely improve and will last for Long days…
So it’s up to the contestant to decide which path to prefer.And i strongly believe that change must come from a Contestant…

5 Likes

@everybody… I dont actually get what you are saying here. If one doesnt know, how to solve a problem, whats wrong in googling about it to know how to approach such a kind of problem? Its after all, increasing knowledge as you keep on knowing more and more… Whenever you are faced with a problem… you obviously google it to know a better algorithm… Isnt it the sole aim of Long Contests so that people simultaneously learn and contest…

        Whats wrong in knowing the approach , algorithm and then implementing it by yourself,

by writing code… and submitting to the judge to know whether you did it right? I personally learnt a lot through these contests, especially long contests… Thank you very much Codechef… Whatever knowledge and skills I have gained in programming ,most of it is due to codechef.

1 Like

Chill out dude.There is nothing wrong in that, but in many cases, some users were found indulged in malpractices. More here http://discuss.codechef.com/questions/9043/misbehaviours-in-may-challenge-to-be-reported-here
and few more existing threads are there. Please don’t take out a buried thread and topic back to live. You’re okay to google for the ideas man.

1 Like

one last question… so , is a new algorithm not a new idea ?

Yes, why not. Don’t think about others, you learned something while searching on the internet? Yes, then good. Those blindly copying codes do not learn, and the motto of these discussions was to reduce such incidents.

Hi All, we understand your concerns regarding the decorum of the monthly contests. Hence, we’d like you all to contribute and help us maintaining it by reporting any CodeChef account involved in such malpractices. We’ve already mentioned it in our rules for any ongoing contest that any individual found indulged in such practices will be banned from the platform without any prior intimation. So, if any of you come across such accounts feel free to report to us at feedback@codechef.com. We will take appropriate action against such accounts.

@admin : Why don’t you run MOSS- A System for determining the similarity of programs or Plagiarism , after every long contest? Quite Efficient tool, there is no way cheaters can “by-pass” MOSS?

http://theory.stanford.edu/~aiken/moss/

1 Like

@ritesh_gupta - a brute force over 75000 submissions will amount to O(75000^2) calls to moss. Intelligent pruning may reduce it, but we believe that there are more important things to be done for the community than to try and find people who are harming themselves and not reaping the benefits that the platform has to offer.

@admin there should be an agreement and/or manual that users should read before the contests. A lot of users, mostly new users think that it’s ok to ask for help in the comment section… And some of them even give hints after solving the problem… The comments are turned into discussions regarding test cases, etc, etc… This behaviour only motivates other users to do the same, every month these types of situations are becoming more frequent.