You can improve your proficiency and efficiency by doing more questions with difficulty levels similar to your current level (Div.2 A, B). But more importantly, do more difficult questions (not too difficult, slightly higher than your current level, such as C and D in Div.2), learn to summarize your gains and review them every day. Of course, we also need to learn more new knowledge points.

I hope these suggestions can help you, good luck!

Sorry for my poor English.

Learn how to manage your time in contests better. If you feel stuck on one problem then skip and return later if needed

just chill and everything's gonna be alright

To improve your ability to solve Problem C in Codeforces Div. 2 contests during the competition, follow this structured approach:

1. Identify Weak Areas

• Analyze past contests: Review Problem C from previous contests you struggled with. Categorize them by topic (e.g., greedy, DP, binary search, graphs).
• Focus on recurring themes: Prioritize practicing topics that frequently appear in Problem C (e.g., 1600-1800 rated problems).

2. Targeted Practice

• Study key algorithms: Master common techniques like dynamic programming, binary search, or graph traversal through focused practice.
• Solve topic-specific problems: Use Codeforces filters or platforms like A2OJ Ladders to tackle problems in weak areas.
• Simulate "contest-like" practice: Set strict time limits (e.g., 30 minutes) for solving Problem C-level questions during practice.

3. Contest Simulation

• Join virtual contests: Regularly participate in Codeforces virtual contests to adapt to time pressure and stress.
• Time management: Allocate fixed time slots for each problem (e.g., 10 min for A, 20 min for B, 40 min for C). Stick to these limits even in practice.

4. Problem-Solving Strategies

• Break down problems: Start by simplifying the problem, testing small examples, and identifying patterns.
• Plan before coding: Outline your approach on paper or in comments. Write pseudocode to avoid getting stuck mid-implementation.
• Edge cases: Consider corner cases early (e.g., minimal input, edge values) to validate your logic.

5. Debugging and Efficiency

• Write clean code: Use modular code and meaningful variable names to reduce errors.
• Test incrementally: Validate each part of your code with sample inputs as you build it.
• Practice debugging: Learn to use print statements or debuggers effectively.

6. Review and Reflect

• Post-contest analysis: After contests/virtual contests, review Problem C solutions, even if you solved them. Compare your approach with editorial solutions.
• Keep a progress log: Track solved problems, time taken, and mistakes. Reflect on improvements and recurring issues.

7. Mindset and Confidence

• Stay calm under pressure: Use breathing techniques or short mental breaks to reset focus during contests.
• Build confidence: Celebrate incremental progress. Remind yourself of past successes when tackling Problem C.

Example Practice Plan

• Monday/Wednesday/Friday: Solve 2-3 Problem C-level questions (1600-1800 rating) with a 40-minute timer.
• Tuesday/Thursday: Study a specific topic (e.g., binary search) and solve 3-5 related problems.
• Weekend: Join a virtual contest and review solutions afterward.

By combining topic mastery, strategic practice, and contest simulation, you’ll bridge the gap between post-contest and in-contest performance. Consistency is key—track your progress and adjust your plan as needed. Good luck!

h

Training is nowadays quite a difficult challenge. For example, in my country, I have to book train tickets 10 days earlier. Even then if you are more than a minute late you are going the miss the tickets and have to wait until the next day to book another ticket, delaying your journey by another day. So I stopped training and started bussing