Please change the score of hacking in CF rounds

Revision en2, by VLamarca, 2018-05-14 23:04:47

Hi!

In this blog I would like to suggest a change in how hacking is calculated in CF rounds. I've talked to some of my friends and they agree that it feels a little unfair that someone who solved more problems scores less than someone who hacked more. A great example from where this happens is from the top positions (and other positions too) in today's round: Codeforces Round #482 (Div. 2) .

I have two main suggestions on how to calculate hacking points in a way that I consider fairer. The specific way may vary, but the key points are:

1) The more you successfully hack a certain problem, the less you should score with it. This means that the first hack on problem A should get you 100 points, but the second 50, the third 25 and so on (or something like this, maybe keep 50 for all the following hacks starting with the second one). I feel that a decreasing function for this is fairer because, in most times, when you hack a certain problem, it is easier to hack it again. It only depends on luck to have lots of people in your room that made the mistake you spotted. Notice that, in this suggestion, if you hack problem A one time and then problem B one time, both of them should get you 100 points each.

2) The harder the problem, the more you should score by hacking it. This means that hacking problem A should get you 100 points, and hacking problem B 150 points, or something like this. I feel that in most cases it is harder to hack harder problems because generally their solutions are longer and therefore harder to read. Also fewer people solve harder problems, so it makes sense to increase the value of hacking them to make it more attractive for people that did passed pretest for this problem to try to hack others' solutions.

I am happy to discuss ideas in this regard.

Thanks for reading! (Also if you spot any mistakes in my english I would appreciate to hear about them in my private talks :) )

#### History

Revisions

Rev. Lang. By When Δ Comment
en4 VLamarca 2018-05-15 00:04:23 7 Tiny change: 'd like to suggest a' -> 'd like to humbly suggest a'
en3 VLamarca 2018-05-14 23:09:57 6 Tiny change: ', in most times, when y' -> ', in most cases, when y'
en2 VLamarca 2018-05-14 23:04:47 3
en1 VLamarca 2018-05-14 22:39:45 2047 Initial revision (published)