Так как 600 является юбилейным числом , я предлагаю сделать 600-тый раунд (combined Div1 + Div2) , ну или же просто сделать отдельный раунд для Div1. Я понимаю придумывать задачки немного проблематично , ну все же не обделяйте Div1 :( 
Так как 600 является юбилейным числом , я предлагаю сделать 600-тый раунд (combined Div1 + Div2) , ну или же просто сделать отдельный раунд для Div1. Я понимаю придумывать задачки немного проблематично , ну все же не обделяйте Div1 :(
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | Benq | 3792 |
| 2 | VivaciousAubergine | 3647 |
| 3 | Kevin114514 | 3603 |
| 4 | jiangly | 3583 |
| 5 | turmax | 3559 |
| 6 | tourist | 3541 |
| 7 | strapple | 3515 |
| 8 | ksun48 | 3461 |
| 9 | dXqwq | 3436 |
| 10 | Otomachi_Una | 3413 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | Qingyu | 157 |
| 2 | adamant | 153 |
| 3 | Um_nik | 147 |
| 4 | Proof_by_QED | 146 |
| 5 | Dominater069 | 145 |
| 6 | errorgorn | 141 |
| 7 | cry | 139 |
| 8 | YuukiS | 135 |
| 9 | TheScrasse | 134 |
| 10 | chromate00 | 133 |
Auto comment: topic has been translated by Scayre (original revision, translated revision, compare)
I completely agree, lets celebrate anniversary contest together
Поддерживаю, пацаны правы!
In fact,
#600 should be combined (Div.1 + Div.2 + Div.3)
What do you think?
Edit: Wow guys 78 downvotes, thank you very much. Can we get to 100 downvotes? Edit 2: 8 days passed and only 86 downvotes. DISGUSTANG
I think we deserve it! 3 hours and 10 tasks!
What, Div. 2 already counts Div. 3
.
Combined rounds suck
Agreed. It is really irritating if you get stuck in implementing a B or C and not able to move on to the better problems.
You can start from problem 'C' or 'D', like many do in combined rounds.
For example?
If no combined rounds then how will I gain some positive deltas?
1) Boring and tedious problems imported from Div2 whose main difficulty is to get through the statement? Yay!
2) Always ruined score distribution because of these Div2 problems that inflate values of Div1 problems by adding 1000 points to them. It really is terrible idea to have Div1A worth 1500 pts and Div1C 2500 pts and Div1B solved on the beginning worth same amount of points as Div1E solved in the end. Mentioned differences should be very big, but are in fact pretty small. Yay!
3) Much wider spread of skill level within rooms. Not possible to hack on nontrivial problems cause except you there is maybe one guy who can solve Div1C and that's it. Yay!
4) Increased probability of making stupid mistake because of these Div2 problems where nobody is really excited about putting care in solving them (maybe we should in order to maxizime rating's EV, but that's not fun — period). Yay!
5) Putting more emphasis on ability of getting through tedious easy problems really fast instead of solving more interesting problems which is much more interesting and challenging part of competitive programming. Yay!
Completely agree. And I also don't like the recent meta of giving 6+ problems for Div1/2 to make a "balanced" problem set. Even 5 is a lot. Why more?
Do you really count the first three or four problems, which are solved in first 10 minutes of a contest as a problems?
I think about them as a warm-up before real contest (and it really helps, judging by how often I am stuck at div1A for longer than div1C).
I don’t want to, but if they get FST.. :)))
And I think it’s better to give more time to think or code on hard problems.
If we talk about time, then it's 2:30 round with 3 easy extra problems vs 2:00 round without them.
I wanted to say about the case of 2:00 round with 1 extra problems (with random difficulty)
Such a round is fine if you can solve 4 problems with serious effort in under 1 hour, or if you have 2 easier, 2 medium and 2 hard problems. As long as it's not just easy shit and then a difficulty jump.
Well, for me an ideal CF round will contain 2-3 problems for 2 hours with subtasks. I don't think people will agree on this, so I'll just stop here :)
A lot of subtasks + time scoring doesn't work well and no time scoring also doesn't work well at a high level. However, there can be multiple good formats, this discussion was more about which formats are bad.
I'm also disappointed it's not for div1, but you "should" have proposed problems to make it so. If there's not enough people available for setting+testing right now, it could end up with a jubilee disappointment.
Why do you think 600 should be considered as as jubilee number? :)
Round[600].name.swap(Round[601].name) :)
Автокомментарий: текст был обновлен пользователем Scayre (предыдущая версия, новая версия, сравнить).