Please read the new rule regarding the restriction on the use of AI tools. It applies starting from round 972. ×

rumike's blog

Heavy implementation

By rumike, history, 10 days 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
  • +25
  • Vote: I do not like it

»
9 days ago, # |
  Vote: I like it -96 Vote: I do not like it

Ask chatgpt to do the hard work

→ Reply
»
9 days ago, # |
  Vote: I like it +2 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.

→ Reply
  • »
    »
    9 days ago, # ^ |
      Vote: I like it 0 Vote: I do not like it

    Thanks, I will continue practicing on different related fields

    → Reply
»
9 days ago, # |
  Vote: I like it 0 Vote: I do not like it

for me, i usually solve how they said i should. like we have an elovator and it does this and that and bla bla and then i will IMPLIMENT what the prob says. it works like 90 % of the times.

→ Reply
»
9 days ago, # |
  Vote: I like it +1 Vote: I do not like it

Um_nik

→ Reply
»
9 days ago, # |
  Vote: I like it +8 Vote: I do not like it

Other than more practice, code style also matters in solving implementation problems. Knowing the full solution with all the conditions and then implementing it will be more helpful rather than figuring out various conditions and scenarios while implementing. One thing you can do is to break your solution into multiple parts and implement them separately, maybe use distinct functions for each part. Then it will be more readable and will help you to understand the purpose of each function, making it easier to identify and fix any bugs.

→ Reply