TheLooseCannon's blog

By TheLooseCannon, history, 20 minutes ago, In English

Hi everyone!

I've been wondering about something while practicing competitive programming.

Sometimes I spend quite a long time trying to solve a problem, but I still can't find a promising approach. At that point, I'm never quite sure whether I should keep thinking or move on to another problem.

I'm curious about how other people handle this situation.

A few questions:

  • Do you set a time limit for thinking about a problem?
  • What makes you decide that it's time to read the editorial?
  • Do you prefer taking a short break and coming back later?
  • Have you ever spent hours on a problem and suddenly found a simple solution?

I'd especially like to hear how your approach has changed as you've gained more experience.

I think this is something many competitive programmers struggle with, so I'd love to hear your thoughts!

Thanks for sharing!

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

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

Yeah its a thing that happens to me too. But more often than not I do find a way to solve the problem without looking at any hints, But only after a thinking for a long time of 2+ hours on tough problems. So I don't know whether I should be setting time limit to my thinking or not.