During my first semester, I participated in my university's IUPC selection contest.

There was one problem that looked easy. I came up with the solution quickly and submitted.

WA. "No problem," I thought. Submitted again. WA. Again. WA.

At some point, I wasn't solving the problem anymore. I was farming penalties.

After 20+ submissions, I finally found the culprit:

(int)

The problem needed: (long long) That's it. My algorithm was fine. My observations were fine. My confidence was definitely not fine.

That day I learned an important lesson: In competitive programming, the hardest bug isn't always in the logic. Sometimes it's hiding inside four innocent-looking letters:

(int)

Why Most Beginners Quit Competitive Programming After 3 Months

I've noticed something interesting over the years.

Every semester, many students start competitive programming with a lot of excitement. They create a Codeforces account, solve a few easy problems, participate in contests, and dream of becoming a strong coder.

But after 2-3 months, most of them disappear.

Why?

I think the biggest reason is expectations.

Many beginners think they'll see rapid improvement if they solve enough problems. But CP doesn't work that way. Sometimes you practice for weeks and still perform badly in contests. Sometimes your rating drops even though you're working hard.

Another common mistake is comparing yourself to others. You solve two problems and feel happy, then you check the standings and see someone your age solved everything. Suddenly, your progress doesn't feel good enough.

Motivation is also a factor. In the beginning, every AC feels exciting. Later, you start getting WA, TLE, and difficult problems that make you feel stuck. That's usually the point where many people quit.

The truth is, competitive programming is a long journey. Progress is often slow and invisible. The people who improve aren't necessarily the smartest; they're usually the ones who keep going when things become frustrating.

If you're currently struggling, you're probably experiencing what almost every competitive programmer experiences at some point.

The first three months are where excitement ends.

The real journey starts after that.