rumike's blog

By rumike, history, 4 hours ago, In English

Each time, I faced a heavy implementation problems, even If I had the idea of the solution earlier, I just lost myself in the process of resolving, and look at the editorial many times. Every time, I missed a detail, and that took me sometimes 30 minutes without even remark it. Suddenly when I look at the editorial again, I say oh what the hell? and repeat the same process, again and again.

I am so slow on heavy implementation, and I know the common advice is to solve more implementation problems, but I am trying that and it's hard as described before. Did someone faced the same problem, and overcomed it? At least for implementation problems in range 1800 — 2000. If yes please give me advice, how should I trained this type of problems.

Also any tips to become quicker on resolving problems in general is welcome.

  • Vote: I like it
  • +5
  • Vote: I do not like it

»
52 minutes ago, # |
  Vote: I like it 0 Vote: I do not like it

Ask chatgpt to do the hard work

»
2 minutes ago, # |
  Vote: I like it 0 Vote: I do not like it

I've faced the same thing before, and my personal strategy is to not focus on simply solving any heavy implementation problems.

I think you should first identify more specific aspects of these problems that make them hard for you. To me, I was bad at data structures (other aspects can include constructive algorithm, brute force, etc.), so I practiced a lot of those. For example, I would try to replicate templates involving data structures, and this is a really hard thing to do, initially, but the only way out is to keep practicing.