What I have to say is in next contest I’m expecting to have something new on table. After seeing so many suggestions. Finally admin has to decide. 
Will ask them to take this feedback as well. Though I feel second step can take time to implement
@aryanc403 xD. I knoow what you’re feeling, but usually we test things out and bring changes to contests only when fully sure. So, things may take some time. 
1 Like
Hi oleg_b! I completely agree with your first three paragraphs.
Maybe it’s not necessary to give the contestant a special choice of solution. Under last-one-counts, if a contestant wants a different submission as his/her final answer, they just have to resubmit it so that it becomes the last one.
(I say this because I don’t want to put too much burden on admins to change the UI. Probably the less we ask for, the greater the chance of a change. I know I suggested a UI change earlier, but I’m coming round to algmyr’s POV that last solution + complete separation is the simplest/best method.)
1 Like
As for reducing randomness, I looked at stats for CHEFPAR to see what might be feasible. In Div 1 there were ~6400 submissions from 274 people, and in Div 2 ~10300 from 1158. Current system (AIUI) evaluated 20*16700 tests. Last-one-counts would evaluate 1432n tests. Breakeven is n=233 tests, but it’s not quite so simple because it’s not ideal to have all the server burden at the end of the contest. Probably the server would have to speculatively run some solutions in the hope that they don’t change. So maybe n=100 would be more realistic? Unless there is a spare server capacity - I don’t know.