Struggling to Solve Contest/OA questions

# Struggling to Solve Contest/OA Questions: A Personal Journey and Solutions

Hello, fellow coding enthusiasts!

If you're reading this, you might relate to my ongoing struggle with online assessments (OAs) and coding contests. Despite investing a significant amount of time into preparing for these challenges, I find myself struggling to apply my knowledge effectively when it matters most. Let me share my experience and the steps I'm considering to overcome these hurdles.

## My Coding Journey So Far

I have been actively leetcoding for almost four months now. In this short span, I have tackled around **250 questions** and have made considerable progress through various learning resources. Notably, I have completed the **Neetcode 150 roadmap** ([Link](https://neetcode.io/roadmap)) and am steadily working my way through **Striver's A2Z DSA list** ([Link](https://takeuforward.org/strivers-a2z-dsa-course/strivers-a2z-dsa-course-sheet-2)).

While I have been diligent in my preparation, I have faced a significant challenge: when it comes to actual contests or OAs, I often feel completely blank. Though I can easily recognize and apply techniques like the **Sliding Window**, **Two Pointer** approach, or **Dynamic Programming** in practice, the pressure of a timed contest leaves me struggling to recall these strategies.

## The Problem: Knowledge vs. Application

The crux of my issue lies in the distinction between knowledge and application. During practice sessions, I can solve problems with ease, but when faced with a new question in a high-pressure environment, I can't seem to make the connections. This has led to disappointing outcomes in contests, where I sometimes fail to even solve the easier problems.

What's more frustrating is that once the contest is over, I can often solve the problems immediately after seeing the hints or solutions. This indicates that I possess the knowledge but lack the ability to apply it under pressure.

## Seeking Solutions: What Can I Do?

After reflecting on my experience and seeking advice from the community, I gathered some valuable insights that I plan to implement:

### 1. **Revisit the Basics**

One of the comments I received suggested going through the **Neetcode 150** again. It made me realize that I might still struggle with fundamental concepts. Revisiting these fundamentals could help solidify my understanding and reinforce my problem-solving abilities. Following that, I plan to tackle more advanced topics, such as **Grind 169**.

### 2. **Limit Exposure to Hints and Solutions**

Another piece of advice was to avoid looking at hints and solutions prematurely. It’s easy to get into the habit of seeking help when faced with a challenging question, but giving myself time to think things through could lead to better retention of problem-solving techniques. I intend to practice patience during contests and give myself a fair chance before resorting to external assistance.

### 3. **Simulate Contest Conditions**

To better prepare for the pressure of contests, I will create simulated environments at home. By timing myself and practicing under similar conditions, I hope to train my mind to think critically and quickly without the safety net of hints or solutions.

### 4. **Review and Reflect**

After each practice session or contest, I plan to take the time to review the problems I couldn't solve or struggled with. Understanding why I found certain problems difficult will help me identify gaps in my knowledge or reasoning and enable me to focus my future study sessions more effectively.

### 5. **Increase Problem Variety**

To enhance my adaptability, I will diversify the types of problems I tackle. Instead of sticking solely to the established lists, I will explore other resources and platforms to expose myself to a wider range of questions. This could help me become more versatile in my problem-solving approach.

## Conclusion

Struggling with contest and OA questions is a common hurdle many aspiring coders face. However, through reflection, targeted practice, and community support, I believe it’s possible to overcome these challenges. I hope my journey resonates with you, and perhaps some of the strategies I plan to implement will also benefit you.

Let’s continue to support each other in our coding journeys, and remember: every setback is a setup for a comeback!

Happy coding!

---