Skip to main content

Documentation Index

Fetch the complete documentation index at: https://resources.devweekends.com/llms.txt

Use this file to discover all available pages before exploring further.

​
The CP Mindset

​
The Truth About Competitive Programming

Here’s what nobody tells you: The best competitive programmers aren’t the smartest. They’re the ones who learned to embrace failure, stay calm under pressure, and keep improving systematically. CP Success Pyramid
Your rating is not your worth. It’s a snapshot of your current skill level. Nothing more. The best programmers you admire were once stuck at the same rating you are now.

​
The Growth Mindset in CP

​
Fixed vs Growth Mindset

Fixed vs Growth Mindset
Fixed MindsetGrowth Mindset
”I’m bad at DP""I haven’t mastered DP yet"
"I’ll never reach Expert""I’m on my way to Expert"
"That problem was too hard""That problem taught me something new"
"Smart people don’t struggle""Struggle is where growth happens"
"I failed the contest""I found gaps to work on”

​
The Power of “Yet”

Every time you think “I can’t do this,” add “yet” at the end.
  • “I can’t solve DP problems” → “I can’t solve DP problems yet”
  • “I don’t understand segment trees” → “I don’t understand segment trees yet”
  • “I’m not fast enough” → “I’m not fast enough yet”

​
Dealing with Failure

​
The Contest Went Badly. Now What?

Failure Response Framework
1

Step 1: Accept (5 minutes)

Feel the disappointment. It’s okay to be frustrated. Give yourself 5 minutes to feel it fully.
2

Step 2: Analyze (30 minutes)

What went wrong? Was it:
  • Knowledge gap? (didn’t know the algorithm)
  • Implementation error? (knew what to do, made mistakes)
  • Time management? (spent too long on one problem)
  • Reading error? (misunderstood the problem)
  • Panic? (knew the solution but couldn’t think clearly)
3

Step 3: Extract Lessons

Write down 1-3 specific things to improve.
4

Step 4: Upsolve

Solve the problems you couldn’t. This is where learning happens.
5

Step 5: Move Forward

The contest is data, not destiny. Use it and move on.

​
The Rating Drop Recovery

Rating drops feel terrible. Here’s the truth: 
┌─────────────────────────────────────────────────────┐
│              RATING DROP REALITY                    │
├─────────────────────────────────────────────────────┤
│  • Even Grandmasters have bad contests              │
│  • One contest = one data point, not your ability   │
│  • Variance is real (luck in problem selection)     │
│  • Your true skill is your 20-contest average       │
│  • A drop often precedes a breakthrough             │
└─────────────────────────────────────────────────────┘

​
Building Confidence

​
The Confidence Cycle

Confidence Building Cycle Low confidence → Poor performance → Lower confidence is a trap. Break it with:
  1. Solve problems you CAN solve (at or below your level)
  2. Track your wins (keep a log of problems solved)
  3. Celebrate small victories (any AC is progress)
  4. Review past successes when feeling low

​
Before Every Contest

┌─────────────────────────────────────────────────────┐
│           PRE-CONTEST RITUAL                        │
├─────────────────────────────────────────────────────┤
│  1. I have prepared. I am ready.                    │
│  2. This is practice, not a test of my worth.       │
│  3. I will do my best with what I know.             │
│  4. Every problem is an opportunity to learn.       │
│  5. Win or learn—there is no lose.                  │
└─────────────────────────────────────────────────────┘

​
Managing Contest Anxiety

​
Why We Panic

Your brain treats contests like threats. Heart racing, sweaty palms, mind going blank—this is your fight-or-flight response activating when you don’t need it.

​
The 4-7-8 Breathing Technique

When you feel panic rising:
  1. Breathe in for 4 seconds
  2. Hold for 7 seconds
  3. Breathe out for 8 seconds
  4. Repeat 3 times
This physiologically calms your nervous system.

​
The “Stuck” Protocol

When you’re stuck on a problem and starting to panic:
1

1. Recognize

“I’m stuck. That’s normal. Everyone gets stuck.”
2

2. Step Back

Take a 30-second break. Look away from the screen.
3

3. Re-read

Read the problem again. Check constraints.
4

4. Simplify

“What if n was only 5? How would I solve it?”
5

5. Move On If Needed

Skip and return later with fresh eyes.

​
The Plateau Problem

​
Why Plateaus Happen

Skill Plateau Visualization Plateaus are normal. They happen because:
  1. Comfort zone: You’re solving problems you already know how to solve
  2. Missing fundamentals: There’s a gap in your foundation
  3. Wrong practice: Solving too many easy problems
  4. Burnout: Mental fatigue from overtraining

​
Breaking Through

ProblemSolution
Solving same difficultySolve problems +100-200 rating above your level
Missing fundamentalsGo back and master the basics
Wrong practiceFocus on weakest topics, not favorite topics
BurnoutTake 2-3 days off completely

​
The Long Game

​
Realistic Timelines

Realistic Rating Timeline Be patient. Getting good at CP takes time:
Rating GoalTypical Time (consistent practice)
Pupil (1200)1-3 months
Specialist (1400)3-6 months
Expert (1600)6-12 months
Candidate Master (1900)1-2 years
Master (2200)2-4 years
These are averages. Some people are faster, some slower. Both are fine.

​
The 1000 Problem Principle

┌─────────────────────────────────────────────────────┐
│              THE 1000 PROBLEM PRINCIPLE             │
├─────────────────────────────────────────────────────┤
│                                                     │
│  After ~1000 quality problems with full upsolving,  │
│  you will be fundamentally different as a coder.   │
│                                                     │
│  • Not 1000 random problems                         │
│  • 1000 problems with struggle + learning           │
│  • Across all major topics                          │
│  • With proper analysis after each                  │
│                                                     │
└─────────────────────────────────────────────────────┘

​
Daily Mental Habits

​
Before Practice

  • Set a clear goal: “Today I will focus on DP”
  • Remove distractions: Phone away, notifications off
  • Prepare mentally: “I’m here to learn, not to prove myself”

​
During Practice

  • When stuck: Struggle for 20-30 min before hints
  • After solving: Ask “Could I have done this faster?”
  • After not solving: Ask “What was I missing?”

​
After Practice

  • Log what you learned
  • Note what was hard
  • Plan what to review

​
The Daily Reflection

┌─────────────────────────────────────────────────────┐
│              END OF DAY QUESTIONS                   │
├─────────────────────────────────────────────────────┤
│  1. What did I learn today?                         │
│  2. What was challenging?                           │
│  3. What will I do differently tomorrow?            │
│  4. What am I proud of today?                       │
└─────────────────────────────────────────────────────┘

​
Comparing Yourself to Others

​
The Comparison Trap

“They’re 2 years younger and already Expert!” “My friend started after me and passed me!” Stop. You’re running your own race.

​
What You Don’t See

  • Their prior math/programming experience
  • How many hours they practice
  • Their natural affinity for certain topics
  • Their failures and struggles

​
The Only Valid Comparison

You today vs You yesterday. That’s it. Are you better than you were a week ago? A month ago? That’s all that matters.

​
When to Take Breaks

​
Signs You Need a Break

  • Dreading practice instead of enjoying it
  • Same mistakes repeatedly (brain fatigue)
  • Feeling burned out after every session
  • No improvement despite effort
  • CP affecting your mood/sleep

​
Healthy Break Protocol

  1. Short break: 1-2 days, do something fun
  2. Medium break: 3-7 days, complete rest from CP
  3. Strategic break: Focus on something else (different programming, reading, exercise)
Coming back refreshed often leads to breakthroughs.

​
The Champion’s Checklist

I embrace struggle

Difficulty is where growth happens. I lean into hard problems.

I learn from every contest

Win or learn. There is no failure, only feedback.

I am patient

Mastery takes time. I trust the process.

I compare to myself

My only competition is who I was yesterday.

I celebrate progress

Every AC, every insight, every improvement matters.

I rest when needed

Recovery is part of training, not laziness.

​
Your CP Mantra

Pick one or create your own. Repeat it when things get hard: 
"The struggle is the lesson."

"I'm not good yet, but I'm getting better."

"This problem is hard for me now. It won't be forever."

"Every expert was once a beginner."

"The rating will come. Focus on learning."

​
Next Steps

8-Week Roadmap

Start your structured journey with a clear plan.

Reading Problems

Master the art of understanding what problems are really asking.

​
Interview Deep-Dive

Strong Answer:
  • First, I examine their practice data. Are they solving problems at or below their level (comfort zone solving) or pushing into harder territory? If 90% of their problems are 200+ rating below their level, the issue is technical: they are reinforcing existing skills, not building new ones. Prescription: shift to 60% problems at their level and 40% problems 100-200 above.
  • Second, I check their contest performance versus practice performance. If they solve hard problems in practice but choke in contests, the issue is psychological — anxiety, time pressure, fear of rating loss. Prescription: more virtual contests treated as practice (no rating at stake), breathing techniques, and reframing contests as learning opportunities rather than evaluations.
  • Third, I look for topic avoidance. If their solve history shows zero DP problems in 2 months, they are avoiding their weakness. Plateaus often come from having one critical gap that blocks progress on harder problems. Prescription: dedicated focus on the weakest topic for 1-2 weeks, even if it means temporarily solving easier problems in that topic.
  • Finally, I check for burnout. If they dread practice sessions, make the same mistakes repeatedly (a sign of cognitive fatigue), or show declining performance despite increased hours, they need a strategic break — 3-7 days completely away from CP, followed by a fresh start with a revised practice plan.
Follow-up: How do you distinguish between a natural skill ceiling and a temporary plateau?There is no permanent ceiling in competitive programming below the Grandmaster level — the techniques are learnable, not dependent on innate talent. What feels like a ceiling is usually either a missing fundamental (they cannot improve at 1600-level DP because their 1200-level DP understanding has gaps) or diminishing returns from their current practice method. I would ask: have they changed their practice approach in the last 3 months? If they have been doing the same thing (solve random problems, occasionally upsolve) since they started, that approach has hit its ceiling. Switching to targeted topic practice, spaced repetition, and deliberate contest simulation almost always breaks through.
Strong Answer:
  • The only valid comparison is you today versus you one month ago. Other people’s trajectories are invisible — you do not see their prior math olympiad experience, their daily practice hours, or their natural affinity for certain problem types. Comparing visible outputs (rating) without seeing inputs (practice hours, background, method) is fundamentally misleading.
  • Practically, I redirect comparison energy into analysis. Instead of “they are better than me,” I ask “what are they doing that I am not?” If they upsolve every contest and I skip it, that is actionable. If they drill DP daily and I avoid it, that is actionable. Transform emotional comparison into tactical intelligence.
  • The second practical step: track your own improvement metrics. If I was solving CF 1200 problems in 20 minutes last month and now solve them in 12 minutes, that is concrete progress regardless of anyone else’s rating. If my first-submission acceptance rate went from 40% to 65%, that is measurable improvement.
  • Long-term perspective: competitive programming careers span years. Someone who reaches Expert in 6 months and someone who reaches Expert in 18 months are both Experts. The destination matters more than the speed, and the skills acquired along the way (problem-solving, debugging, algorithmic thinking) compound regardless of pace.
Follow-up: Is there any scenario where comparing yourself to others is actually productive?Yes — when you use it for method analysis, not self-evaluation. If a peer at your rating level consistently solves problem C in Div 2 contests and you do not, study their approach. Read their submissions. What pattern do they recognize that you miss? What template do they use that you do not have? This is competitive analysis, not self-deprecation. The key distinction: “they are better than me” is unproductive. “They see binary-search-on-answer patterns faster than me, so I should drill that topic” is productive.
Strong Answer:
  • The ideal ratio for someone actively improving is roughly 30% contests (including virtual), 40% topic-focused practice, and 30% upsolving and review. Pure contest grinding without topic study leads to plateaus; pure study without contests leads to slow speed and poor time management.
  • Weekly schedule: Monday and Thursday — virtual contests (past Div 2 rounds, 2 hours strict). Tuesday and Friday — upsolve the previous day’s virtual contest. Wednesday — targeted practice on weakest topic (identify from contest performance). Saturday — live rated contest. Sunday — review the week’s mistake journal, re-solve problems from spaced repetition queue, and plan next week’s focus topic.
  • The key insight: contests reveal gaps, and practice fills them. Without contests, you do not know what to practice. Without practice, contests just repeatedly expose the same gaps. The cycle of contest -> identify weakness -> practice weakness -> contest -> verify improvement is what drives rating growth.
  • Adjustments by level: below 1200, emphasize implementation speed (more easy problems). 1200-1600, emphasize topic breadth (make sure you can handle every major pattern). Above 1600, emphasize depth in weak areas and speed on strong areas.
Follow-up: How do you decide which topic to focus on in a given week?I look at my last 5 contests and identify the highest-rated unsolved problem in each. I categorize each by topic (DP, greedy, graphs, etc.). The topic that appears most frequently is my focus for the next week. If the data is unclear, I fall back to the topic I have the fewest solved problems in on my CF profile. The meta-principle: practice what you are worst at, not what you enjoy most.