I am not writing this from the top of the leaderboard. I am writing this from the bottom.
Like many of you, I am currently low-rated. For a long time, I looked at the gap between my rating and my goal and assumed the high-rated coders just had some innate genius I lacked. I treated contests like a lottery—hoping for problems that fit my specific knowledge, and forgetting the ones that didn't.
I was wrong. The difference isn't genius. It's upsolving.
I recently realized that my rating is stagnant because I have been wasting my failures. Here is the hard truth I had to accept, and if you are stuck like me, you need to accept it too:
Ignoring Errors is Choosing Mediocrity I used to finish a contest, see that I failed Problem C, and move on. That is a waste of time. If I couldn't solve Problem C during the round, that specific problem is the exact barrier holding me back. Ignoring it ensures I will fail the next similar problem too.
"Silly Mistakes" Are Just Knowledge Gaps I used to comfort myself by calling my bugs "silly mistakes." They aren't. Incorrect indices, edge cases, and logic slips are symptoms of a weak process. Upsolving forces me to confront these gaps without the clock ticking. You cannot fix what you refuse to look at.
The Shift in Mindset The contest is just an assessment. The actual improvement happens when the timer stops.
Old Me: Check editorial, say "Oh, I see," and close the tab.
New Me: struggle for another hour, code it myself, and prove the logic.
I am done relying on luck. I am focusing on the work. If you are tired of your rating, stop scrolling and start upsolving.
