How to improve my debugging skill ?
# | User | Rating |
---|---|---|
1 | tourist | 3985 |
2 | jiangly | 3814 |
3 | jqdai0815 | 3682 |
4 | Benq | 3529 |
5 | orzdevinwang | 3526 |
6 | ksun48 | 3517 |
7 | Radewoosh | 3410 |
8 | hos.lyric | 3399 |
9 | ecnerwala | 3392 |
9 | Um_nik | 3392 |
# | User | Contrib. |
---|---|---|
1 | cry | 169 |
2 | maomao90 | 162 |
2 | Um_nik | 162 |
4 | atcoder_official | 161 |
5 | djm03178 | 158 |
6 | -is-this-fft- | 157 |
7 | adamant | 155 |
8 | awoo | 154 |
8 | Dominater069 | 154 |
10 | luogu_official | 150 |
How to improve my debugging skill ?
Name |
---|
Do more problems with implementation tag. You do more problems -> more chance of mistake -> more debugging to do.
Test programs locally by writing brute force-Allows you to find out edge cases, or get counter-case for tempting, but unproven, approaches.
Have a Debug template-Having a method or something which prints out variables in a "readable" format can be helpful to know how program states are changing in a certain scope.
Do problems-Doing lot of problems will help you catch your bugs quickly since you would be aware of the potential locations of the bugs.
Do Stress Testing.
Open status page, check submissions with WA verdict and try to come up with a test that will fail this solution. Start doing this with easy DIV.2 A problems, then with harder problems.