Do you submit immediately or do you try to make some more tests / check the program more?
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 3993 |
2 | jiangly | 3743 |
3 | orzdevinwang | 3707 |
4 | Radewoosh | 3627 |
5 | jqdai0815 | 3620 |
6 | Benq | 3564 |
7 | Kevin114514 | 3443 |
8 | ksun48 | 3434 |
9 | Rewinding | 3397 |
10 | Um_nik | 3396 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
3 | maomao90 | 162 |
3 | atcoder_official | 162 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 155 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
10 | djm03178 | 152 |
Do you submit immediately or do you try to make some more tests / check the program more?
Название |
---|
2-3 small cases, edge cases, and 1 to test for TLE.
Become a tester please.
yolo
what does yolo means?
You only love once
Live*
Well, "You only love once" is also correct :D
YOLO in YOLO algorithm means 'you only look once'.
If I think the logic is correct, I submit my solution. And then I get WA on pretest 2
Worst feeling ever
Depends on the problem and how confident I am on my solution. Usually you can also do a bit of thinking about whether your solution seems intended. For example Div 2A solutions are usually very short and require some quick observation or math formula.
For harder problems if I'm even just somewhat confident I'll just submit. I tend to use Proof By AC, and it usually works. After getting any WA I debug until I find at least one case which was broken, and then fix that and resubmit.
after my code passes the sample cases i go to the next one
You forgot to submit
I get the intuition before submitting, basically if my code is too complex then i don't submit it ( i think why would setter think of such a shitty solution ) and try to reduce it to a simple solution.
Think some seconds about what would I do if I get WA. Then do just this for like one or two minutes. If I do not spot a bug in that time, then submit.
The "one or two minutes" is less for simple problems, more for later ones.
Edited: I will try to do the next problem
I read the next problem
It depends on both the problem and the solution. If the problem was very Mathsy and the solution is a few lines I will think about edge cases first and then submit. If the problem required a lot of implementation and my solution looks too ugly I'll just submit and hope for TLE instead of WA.
Get WA on pretest 2.
I generally submit it once if logic seems fine to me. Even if my logic has no proof, it's intuitive, then I try my luck and submit it for once. If its accepted then fine, and if not, then I again try to figure out the correct logic and look for some edge values.
Usually I look at my friends rank list if people who are better than me are getting wrong answer then I look at corner cases,otherwise submit it.
If the sample cases were enough for me to solve the problem on paper, I submit immediately, else I test the code also on the cases that I'd generated on paper.
I do not test my code, I prove it correct.
What a heroic comment.
You prove that your code is bug free?
I try to prove/disprove before coding, think of small edge cases while/after coding and don't submit unless I think that it should pass (sometimes I am wrong). So in case of pretests pass, I move on to next problem.
I look over the standings and check whether I am leading or not