When submitting a solution in C++, please select either C++14 (GCC 6-32) or C++17 (GCC 7-32) as your compiler. ×

Scayre's blog

By Scayre, history, 4 years ago, translation, In English

Since 600 is a jubilee number, I propose making the 600th round (combined Div1 + Div2), well, or just making a separate round for Div1. I understand coming up with problems is a little problematic, but still don’t deprive Div1 :(

  • Vote: I like it
  • +355
  • Vote: I do not like it

| Write comment?
»
4 years ago, # |
  Vote: I like it +8 Vote: I do not like it

Auto comment: topic has been translated by Scayre (original revision, translated revision, compare)

»
4 years ago, # |
  Vote: I like it +45 Vote: I do not like it

I completely agree, lets celebrate anniversary contest together

  • »
    »
    4 years ago, # ^ |
      Vote: I like it +13 Vote: I do not like it

    Поддерживаю, пацаны правы!

»
4 years ago, # |
Rev. 3   Vote: I like it -86 Vote: I do not like it

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

»
4 years ago, # |
  Vote: I like it -65 Vote: I do not like it

Combined rounds suck

  • »
    »
    4 years ago, # ^ |
      Vote: I like it +21 Vote: I do not like it

    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.

  • »
    »
    4 years ago, # ^ |
      Vote: I like it -26 Vote: I do not like it

    If no combined rounds then how will I gain some positive deltas?

  • »
    »
    4 years ago, # ^ |
      Vote: I like it +111 Vote: I do not like it

    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!

  • »
    »
    4 years ago, # ^ |
      Vote: I like it +63 Vote: I do not like it

    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?

    • »
      »
      »
      4 years ago, # ^ |
        Vote: I like it +43 Vote: I do not like it

      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).

      • »
        »
        »
        »
        4 years ago, # ^ |
          Vote: I like it 0 Vote: I do not like it

        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.

        • »
          »
          »
          »
          »
          4 years ago, # ^ |
            Vote: I like it +35 Vote: I do not like it

          If we talk about time, then it's 2:30 round with 3 easy extra problems vs 2:00 round without them.

          • »
            »
            »
            »
            »
            »
            4 years ago, # ^ |
              Vote: I like it 0 Vote: I do not like it

            I wanted to say about the case of 2:00 round with 1 extra problems (with random difficulty)

            • »
              »
              »
              »
              »
              »
              »
              4 years ago, # ^ |
                Vote: I like it 0 Vote: I do not like it

              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.

              • »
                »
                »
                »
                »
                »
                »
                »
                4 years ago, # ^ |
                  Vote: I like it 0 Vote: I do not like it

                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 :)

                • »
                  »
                  »
                  »
                  »
                  »
                  »
                  »
                  »
                  4 years ago, # ^ |
                    Vote: I like it 0 Vote: I do not like it

                  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.

»
4 years ago, # |
  Vote: I like it +50 Vote: I do not like it

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.

»
4 years ago, # |
  Vote: I like it -52 Vote: I do not like it

Why do you think 600 should be considered as as jubilee number? :)

»
4 years ago, # |
  Vote: I like it +34 Vote: I do not like it

Round[600].name.swap(Round[601].name) :)