Goodbye 74TrAkToR - Codeforces

#	User	Rating
1	tourist	4009
2	jiangly	3823
3	Benq	3738
4	Radewoosh	3633
5	jqdai0815	3620
6	orzdevinwang	3529
7	ecnerwala	3446
8	Um_nik	3396
9	ksun48	3390
10	gamegame	3386

#	User	Contrib.
1	cry	167
2	Um_nik	163
3	maomao90	162
3	atcoder_official	162
5	adamant	159
6	-is-this-fft-	158
7	awoo	157
8	TheScrasse	154
9	Dominater069	153
9	nor	153

Problem A~E: The problems themselves are good and typical A~E. Indeed I like problem D. The pretest for A is a bit weak, and it's not a big problem yet.
Problem F: The problem has an origin. :) See the link: click. The problem in contest is only a weakened version of the one in Luogu.
Problem G: It's said that our great coordinator had not proved the time complexity of the intended solution is correct :) If the authors did, please share it in the editorial. (although this problem is completely beyond my ability :) )
Problem H: Oh dear 74TrAkToR, could you please OEIS the sequence before you use the "several-integer-input" problem in rounds next time? Anyone who copied the first example and opened https://oeis.org/A286331 could quickly get the formula. And the problem itself is not so hard imo. Anyway, it should not be used in contest, especially for the last problem.

For me personally, I won't participate in 74TrAkToR rounds any more. The quality of his rounds is far below the average of CF Rounds. This great coordinator has coordinated the following rounds:

Codeforces Round 907 (Div. 2), which has a *2000 problem as Div2F :)
Codeforces Round 880 (Div. 1 & 2), which got 1400+ downvotes :)
Codeforces Round XXX, which has a NP-Hard problem as Div2C with intended solution in O(n log n) :)
... (please take a look at Edit 6)

Dear Mike:

I advise making the round unrated.

You, of course, are shocked. You, of course, think that the round should be rated.

I was also an author of a previous official round. I completely understand the efforts the authors and coordinators paid behind a round. But it is not an excuse to evade responsibility. Serious problems appeared in today's round, in problem F&G&H, ALL OF LAST THREE problems in the contest. According to testers, this round even consists of an unproven problem. If this round remains rated, I guess it will be a decrease in programmers' trust in Codeforces. To avoid this, I kindly advise you to unrate this round and assign at least 2 coordinators for 74TrAkToR rounds in the future.

Please do not reply a "You're wrong, here's why" again!

Edit: I've saved this entry locally to avoid 74TrAkToR from deleting it. 74TrAkToR has done similar things on the announcement of his rounds before. Why can he delete these comments that criticize him?

Edit2: According to testers, the MCS of problem G is wrong, now it is not an unproven problem any more :)

Edit3: I've looked at 74's appeal. Unfortunately, he did not reply to anything that was mentioned in my entry. He just said, "it's all history". :)

Edit4: According to Appeal. 74TrAkToR,

We asked problem H from other authors and, unfortunately, it turned out to be known.

Is it pointing out that 74 knows that H is known, and still use it in the round?

Edit5: I'm sad to see that the rating has been updated. Parhaps I should mention MikeMirzayanov in this blog. Please take a look at this!

Edit6: I've listed all of 74 rounds in 2023. Please check it.

History

In Year 2023, 74 had coordinated $$$10$$$ rounds in total. Here's something about them:

Good Bye 2023. This round. I don't want to say anything more. Votes of the announcement: $$$-3405$$$. (up to 2023/12/31)
Codeforces Round 908 (Div. 1, Div. 2). No fatal problems occurred in the round, but it feels like Div1A=B=C=D for me :( And actually the performance people who solved problems range from CM to GM, so I would say that this round is of low discrimination. Votes of the announcement: $$$+175$$$.
Codeforces Round 907 (Div. 2). Also, no fatal problems occurred in the round, but problem F is way too simple. Difficulty disorder usually happens in 74 rounds. Votes of the announcement: $$$+232$$$.
CodeTON Round 6 (Div. 1 + Div. 2, Rated, Prizes!). Good contest imo, I enjoyed E very much. Qualities of the problems are above average. Votes of the announcement: $$$+394$$$.
Codeforces Round 880 (Div. 1; Div. 2). I didn't participate in this round, and a *2500 occurred for position Div1B/Div2D. Yet another difficulty disorder. Votes of the announcement: $$$-1467$$$.
Codeforces Round #873 (Div. 1 & 2). I didn't participate in this round, and it seems a good round. I saw problem Div1B/Div2D before the contest (guess why) and found it really cool. Votes of the announcement: $$$+439$$$.
CodeTON Round 4 (Div. 1 + Div. 2, Rated, Prizes!). Great round! I enjoyed the problemset very much. Kudos to the authors! Votes of the announcement: $$$+687$$$.
Nebius Welcome Round (Div. 1 + Div. 2, rated, t-shirts!). Good round. And a fact is that this round is coordinated by both 74 and KAN. Votes of the announcement: $$$+720$$$.
TypeDB Forces 2023 (Div. 1 + Div. 2, Rated, Prizes!). A just-so-so round. Problem E<C imo. According to feecle6418, this round also has a known problem, but fortunately it caused little influence. Votes of the announcement: $$$+209$$$.
Codeforces Round #846 (Div. 2). The NP-hard round. I'm really curious that why none of the authors and testers, and of course, the coordinator, did not find the error in the intended solution. Votes of the announcement: $$$-628$$$.

Out of these $$$10$$$ rounds, $$$4$$$ rounds are generally considered as good rounds, $$$3$$$ rounds have negative votes in announcement, $$$2$$$ rounds have serious problem disorder, and the average votes of these rounds is $$$-264.4$$$. In 2023, there are $$$6$$$ rounds getting negative votes in all (I didn't count educational rounds.), and 74 rounds take up half of them. Some authors said that 74 is the kind of coordinator who goes his own way. All in all, 74 should do improve his ability before coordinating rounds any more.

Comments (33)

Write comment?

heaksicn

11 months ago, # |

agree.

→ Reply

aleeex

11 months ago, # ^ |

← Rev. 2 →

-39

My name is aleeex

Error_Yuan

Please use spoiler. :)

xueshen666

-10

maybe reply a "You are right,but ..." instead XD

defnotmee

+13

I would also point out the obviously too small time limit for E. Let's wait for the FST's :) (unless the problem actually just have 20 test cases, which would be pretty weird)