My recent biggest problem is that i start coding a problem to soon. Like in my head an idea that should solve a problem will work but when i start actuall coding i often realise that it wont at all. Also this process of realising can be quite time consuming. To fix this i tried to divide a problem into supbroplems and think about every part individually, how i would do this in code. But even then i often miss some small detail and solution falls apart. Any pro tips how i can fix this? How are you guys dealing with this? At what point do you realize that you are ready to code a solution?
→ Pay attention
→ Top rated
| # | User | Rating |
|---|---|---|
| 1 | Benq | 3857 |
| 2 | jiangly | 3810 |
| 3 | maroonrk | 3534 |
| 4 | tourist | 3528 |
| 5 | Kevin114514 | 3510 |
| 6 | turmax | 3411 |
| 7 | Um_nik | 3387 |
| 8 | Radewoosh | 3367 |
| 9 | heuristica | 3322 |
| 10 | strapple | 3317 |
→ Top contributors
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 158 |
| 2 | maspy | 150 |
| 3 | Um_nik | 146 |
| 4 | Errichto | 139 |
| 5 | adamant | 136 |
| 6 | maroonrk | 134 |
| 7 | DNR | 133 |
| 7 | nik_exists | 133 |
| 9 | Dominater069 | 131 |
| 10 | AmShZ | 130 |
→ Find user
→ Recent actions
Codeforces (c) Copyright 2010-2026 Mike Mirzayanov
The only programming contests Web 2.0 platform
Server time: Sep/04/2026 06:37:41 (g2).
Desktop version, switch to mobile version.
Supported by
Well I do start coding a problem too soon and then realize that algorithm not work. I think to fix it you must test some special testcases such as boundary value or all same values in an array, ...
Often that is not about testcases or boundaries, cause problem might be too hard to test everything by hands
Yeah that's why you need to be good at imagination
I dont think so. I think that maybe someone came up with simple list like "what should i check before coding"?