MikeMirzayanov's blog

By MikeMirzayanov, 4 weeks ago, In English

During the round Grakn Forces 2020 many of you can notice that now we highlight diff in statements if they changed. Do you like this new feature?

Also, I'm thinking on the way to automatically notify participants if statements changed. I still do not fully understand how this should ideally be implemented. Sometimes it is true that just a forgotten comma was added. On the other hand, it is almost always better to notify of changes. What do you think?

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

»
4 weeks ago, # |
  Vote: I like it +184 Vote: I do not like it

As a participant in contest I would expect the statements to not change without notification.

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

    I second this, I got screwed in a contest once because of that

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

    As a participant in contest I would expect the statements to not change!!!

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

      No, that's too much. Mistakes sometimes happen, we can't demand preparing contests with absolute absence of oversights and malfunctions (and in case of them having occurred, declare the round unrated). It's quite normal that statements change, and the question is whether to make an announcement or to edit the text silently (after all, notifications distract people solving other problems).

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

        So, why testers being the tester? If they test the statements without mistakes then there will be no problems just like this. Testers being a tester for just some contribution. They don't even test the contest right!!!

»
4 weeks ago, # |
Rev. 2   Vote: I like it +28 Vote: I do not like it

I think the guy who changed to statements should decide.

If its something like "just a comma" then the changer can choose not to notify the participants.

But if its something like changes the problem entirely or something easy-to-miss(but important to solve the problem) then yes it should be notified.

Notification can done by using the same system with the announcements.

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

    Nope. It should be automatic. Sometimes even comma can make a lot of difference for someone specific.
    Right now authors/setters do have a choice to make an announcement or not. Very often its seen that they ignore this. If it's non-trivial damage for 1 among 20000 participants. They just say sorry and move on. This thing already existed. There was a need for automatic and hence this feature.

    Anyways who changes should get an opportunity to decide what should be the body of the announcement. He can just write "I added one comma for the sake of completeness." Many can just ignore that.

    But a strict requirement should be there that any change in statement goes through an announcement.

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

      I don't think that would be a bad thing. Also I don't think there would be so much statement changes that actually distracts the participant so notifying every change is not a bad decision either.

      As is, I think you're right. Every statement change should be notified. It's better that way.

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

        Distraction due to so many changes just shows poor round preparation and authors deserved to be blamed.

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

          I definitely, completely, totally agree.

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

      I am afraid that then writers will be motivated not to make minor edits of statements, so as not to provoke a broadcast with attention to this issue.

»
4 weeks ago, # |
  Vote: I like it 0 Vote: I do not like it

How do we see this? I didn't find any highlighting for the change.

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

    A link comes up at the top of the problem statement.

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

    It shows changes with the first problem statement revision you viewed. So if you didn't see the incorrect version of the statement, you will not see it.

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

      Yeah. Got it. It's a good feature. Can you try to include the latex and stuff as well?

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

      I saw the link in the statement. But it was written in Russian even in the English statements. Please consider translating this.

»
4 weeks ago, # |
  Vote: I like it +257 Vote: I do not like it

Ah, I see, so the thing with B today was intentional for testing purposes?

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

    Yeah, users are always the best testers. Remember this when you develop software at a company, especially when you develop software for things like rockets or nuclear powerplants. (It's a joke)

»
4 weeks ago, # |
Rev. 2   Vote: I like it 0 Vote: I do not like it

Whether to notify or not may be up to authors, but the new revisions of the problem statement should be unconditionally available and highlighted on the page with the statement

»
4 weeks ago, # |
  Vote: I like it 0 Vote: I do not like it

When you are in bottom of problem, notification is unseen, right?