Why am I not improving?

This section is inspired by -is-this-fft- and I highly encourage reading the original, because I couldn't have worded it better myself.

Attributing your failure to irrelevant things

When people fail to improve, they naturally start searching for reasons. Unfortunately, a lot of the reasons are wrong.

In my opinion, these mistakes can be categorized, and what they all have in common is that people tend to blame an input you can add more of instead of the methodology that is broken. It is easy to add more of the wrong thing out of cope, or feeling "productive" or "effort".

"I need to do more"

From my observation, within the leetcode community, this is the most common one. "I solved 500 problems and I am still failing interviews, so I clearly need to do 1000." No, stop. That should be a signal that something in how you practice is wrong, not a reason to double the effort. You should probably revisit how you're studying and be self-aware of whether your effort is converting to growth. It is the same trap as a daily streak: it lets you measure effort instead of progress, so you can pour in enormous volume and feel productive the entire time you are getting nowhere. Why solved count lies is also relevant for this.

Things like "solving every day" and "maintaining streaks" just burns people out in my opinion. Solving DSA should not be a full time job. Most reds or LGMs don't maintain daily streaks either, why should you?

"I need to know more"

The second one. "I keep getting stuck, so I must be missing some algorithm, let me go learn segment trees, or the next twenty patterns, or whatever exotic thing the editorial used." Almost always wrong. The problems that beat you are usually beatable with what you already know, and the reason you failed was not a missing technique, it was that you could not derive the path to it from the constraints. Memorizing one more named trick adds one more entry to a lookup table that was never the bottleneck. It feels like progress, because learning a new thing always does, but it leaves the actual gap untouched. Metacognition vs pattern recognition is the fix for this one.

"They had advantages I didn't"

The last one, and the most comforting, which is what makes it dangerous. "The people who got cracked had a CS degree, or a bootcamp, or a mentor, or started in high school, or could afford some course I cannot." Almost none of that is the reason. All the materials our there are free (e.g. codeforces, usaco guide), the feedback is instant, and the work is overwhelmingly self-driven, so nobody handed the strong people a secret. Plenty of them have no degree and never paid for anything.

So what is actually wrong

The fix is not another input. It is to stop asking "what should I add" and start asking where exactly does my reasoning break. That question has real answers. If you can follow a solution but never produce one, the gap is in generating ideas from constraints, not in your problem count. If you clear mediums but freeze the moment a problem is genuinely new, you trained recognition instead of reasoning. Find the specific step that fails, practice that step on problems you have not seen, and the thing volume could never move starts moving. White Room exists to run exactly that diagnosis with you, instead of handing you the generic "just keep grinding" that never fit your problem in the first place.