OrionLoop's blog

By OrionLoop, history, 2 days ago, In English

I've been doing competitive programming for about a year now, but I feel like my progress has been slower than I expected. I know improvement takes time, but sometimes I feel stuck and unsure if I'm practicing the right way.

I'd really appreciate some guidance from more experienced programmers. What should I focus on, and how can I make my learning process more effective?

Any advice, personal experiences, or suggestions would mean a lot. Thanks in advance!

  • Vote: I like it
  • -12
  • Vote: I do not like it

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

solve problems, understand them, study algorithms

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

How are you practicing? What are your goals (ICPC, IOI, CF rating, etc)? Do you have any problem-solving background?

  • »
    »
    43 hours ago, hide # ^ |
     
    Vote: I like it 0 Vote: I do not like it

    Right now, my goal is ICPC. And I am solving problems Randomly. Um, about Problem-solving background, to be honest, I have nothing worth mentioning. Never been any Problem-Solving level competition like Math Olympiads. But I am a quick learner.

    • »
      »
      »
      41 hour(s) ago, hide # ^ |
       
      Vote: I like it 0 Vote: I do not like it

      Your answer about how you are practicing is very vague. What resources, how consistent, etc. If you actually want guidance you need to be more specific, otherwise I don't believe anyone can help you.

      That being said, I have very limited knowledge regarding ICPC style problems, I mostly specialize in OI, but as you are in the early stage of your career I would definitely suggest working on your problem solving skills as much as possible. You being a quick learner is good, but unfortunately it doesn't help as much in CP, because knowing algorithms and languages is useless up to 1500-1600 rating. Even then, you can get by without knowing stuff like segtrees. Try not to read about algos too much until they are the reason you can't break through a problem.

      Consistency is really important in CP. I would say in peak times I solved pretty much every day for months, but often 3-4 times a week is good enough to ensure you are making progress. Do as many virtual contests as you can, not necessarily on CF. Leading up to ICPC try to ramp up ICPC-specific practice, by solving past problems from your region, or even others. Put a lot of stress into upsolving, and make sure you fully understand what you are doing. Whenever you have questions about solutions that you can't answer, or actually stuck debugging (>10-20 minutes) and can't tell if the idea is wrong or the implementation is messed up, try to prompt AI. Use your pen and paper as much as possible, and draw/sketch everything that you can while solving — I personally found this super useful and my rating went up a bunch once I stopped mind solving.

      As you are training for ICPC, I assume you know people around your skill rating. Try to engage with them as much as possible, even if it seems a little akward. Discussing things with your friends like sharing your progress, or maybe hard problems that you've solved, can go a really long way for your motivation.

      And when it comes to the basics that you might need, I would highly recommend going through usaco.guide's "bronze" (and if you have the time/motivation, the "general") sections. Not all info is going to be useful to you at first, but I think a lot of it is quite essential. Once you have gotten all of it down, you should just be able to solve+upsolve problems and push to green/cyan. Let me know if you have any further questions

      • »
        »
        »
        »
        39 hours ago, hide # ^ |
         
        Vote: I like it 0 Vote: I do not like it

        Your point about focusing on problem-solving rather than constantly learning new algorithms really caught my attention. I think I've been spending too much time learning concepts instead of developing the ability to recognize and apply them.

        I'll also try to incorporate more virtual contests, consistent upsolving, and pen-and-paper approaches into my routine.

        I have one question: When you were around my current level, how did you approach problems that you couldn't solve? For example, how long would you struggle before looking at hints or editorials, and how did you make sure you actually learned something from those problems?

        Thanks again for the guidance!

        • »
          »
          »
          »
          »
          36 hours ago, hide # ^ |
           
          Vote: I like it 0 Vote: I do not like it

          There really isn't a magic number of minutes that you have to spend on thinking before looking at a solution. If you asked me to quantize it for you, I would say 15-30 minutes with 0 progress is where you might want to call it wraps, but you actually have to be clueless within those minutes. If you still see a direction that you haven't explored properly, then you should explore it. For me it was when I knew I've exhausted everything out of the problem — I was always kind of paranoid to look at solutions before I got absolutely every thought out of my brain regarding this problem. At that point I knew that it's either a new idea, a new concept, or a really stupid oversight — and in all cases learning how to solve it will benefit me quite a bit.

          And also, please stop using AI when responding/writing, it kind of makes most people think as if you're talking to a brick wall...

          • »
            »
            »
            »
            »
            »
            32 hours ago, hide # ^ |
             
            Vote: I like it 0 Vote: I do not like it

            all of this advice is very reminiscent of colin galen videos (not saying its bad or good or whatever just another source of information)

    • »
      »
      »
      41 hour(s) ago, hide # ^ |
       
      Vote: I like it 0 Vote: I do not like it

      To add to my previous comment as well, it's very easy to get discouraged from CP because it really does have one of the highest floors -- solving basic problems from scratch, and actually understanding ~90% of what you're writing is really hard. But I promise, once you get going, and once you unlock more complex problems, it really does get better and better. What I am saying is basically the learning curve at the beginning is super steep, probably one of the steepest amongst any similar activity, and that's why at the start it can feel like you're achieving nothing. So maybe your progress isn't actually as slow as you think.

»
17 hours ago, hide # |
 
Vote: I like it 0 Vote: I do not like it

If your goal is ICPC, I would recommend.

While your rank is <= Specialist : You should focus on just solving hard ad-hoc problems, they're usually good to develope problem solving skills, in codeforces most of the <= 1800 rating problems are just like this. I would recommend trying to solve a problem for 3 to 4 hours before seeing the full solution. In my personal experience I had a very fast growth from unrated to expert taking less than a year of real studying and I think this part is the easiest one.

You are expert :D -> You should start learning new things / algorithms, but not hard algorithms like aho corasick or smth, just learn the basics start solving 2000 — 2200 rating problems and see what algorithms that you don't know apper in this kind of problems, e. DSU, Binary Lifting. Keep doing ad hoc codeforces problems but now also do the easy problems of any 3 star official icpc contest gym.

You are cm+ -> Here you keep the codeforces + gym preparation but depending on your region harder algorithms would be more or less necessary to surprass your current level on ICPC, start reading usaco guide, and learn new algorithms, also try upsolving more the gyms rather than upsolving cf.