| # | 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 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 158 |
| 2 | maspy | 150 |
| 3 | Um_nik | 146 |
| 4 | Errichto | 139 |
| 5 | adamant | 136 |
| 5 | nik_exists | 136 |
| 7 | maroonrk | 134 |
| 8 | DNR | 133 |
| 9 | Dominater069 | 131 |
| 9 | AmShZ | 131 |
I'm finding that I'm spending an equivalent amount of time implementing vs. generating ideas.
I feel like this is slow for problems that aren't specifically tagged as implementation.
Can any expert+ coders comment on how their breakdown typically goes? Bonus points if you can break it down by problem category.
im not expert coder but it honestly depends on difficulty of problem as say for an 800 problem idea may take 10 seconds but the implementation might take 2 minutes whereas a harder problem may take an hour to come up with the idea for but only 10 or so minutes to implement
Broo there is no constant time for implementation.
But I actually follow a strategy, DON'T IMPLEMENT ANYTHING BEFORE YOU DRAW THE CODE IN YOUR MIND ..
I mean don't implement while thinking.
If you really follow this you'll save a lot of time..
It's probably because you name your variables things like this
Naming variables more than 2-3 letters in competitive programming is bad practice unless you have a really good reason to name it longer
Hmmm, I find myself getting lost if I don't use human-readable names though
I don't think my working memory can handle a bunch of a, b, c, etc
Maybe you really can’t, but you should try nevertheless. Saying or thinking "while A times B greater than C" is faster and easier than whatever you do with "human-readable" (as if programming languages are not human-readable already). Long names are good for slow-paced work in a big team. You don’t need it, when you solely want to make a computer run your idea and then forget about it.
Makes sense, let me try.
TBH with tab complete it's not that big of a deal. You'll save like 2-3 minutes per problem at most maybe. If longer names help you (they occasionally help me), the time save will not be worth the lost time from debugging.
i vould say 3-4 is golden and i would reccomend also not using unnececary arrays etc: when you are writing a double seg tree iteration you can use an array of two vectors or a vector of two integers or a pair of vectors etc.
Maybe AI is the reason?
You can use templates and get used to them if you want to speed up your implementation a bit. Another good practice is to think more about the problem, make sure you have the full solution completed in your brain (or some sort of drawing/writing will also work), and then implement. This will help you make fewer bugs and implementation mistakes. Except for that, it really does depend on the person, problem, and solution you come up with. Some solutions are simple, some are not. You'll definitely get faster as you participate in more contests.
I usually spend 10 minutes implementing a problems, then spend 2 hours debugging it.