【游记】2026年 CSP-J/S 游记

· · 生活·游记

This blog is a tribute to my final CSP-J/S contest.

I first started learning IT back in Grade 4. I dabbled in many languages, including HTML, Scratch and Python. But it was C++ that took up most of my time — and this is where my whole story began.

Soon I entered middle school. Heavier academic pressure and growing challenges wore me down. At the same time, programming problems grew increasingly difficult, and I started to wonder whether I simply had no talent for this.

I once believed I was gifted. Reality taught me otherwise: I was nowhere near as good as I imagined. My mom comforted me, telling me I needed to adapt and adjust my mindset. I tried my best to follow her advice.

Before long, I reached Grade 9, and the day of my last CSP-J/S rolled around. I was flooded with stress and anxiety, terrified that I would mess up the exam.

The night before the contest, I went over all my algorithm templates, trying to commit them to memory. Even so, I had no idea what the next day would bring.

At last, I walked into the exam hall. I went through security, found my seat, sat down, and laid out my ID card and admission ticket for a second check. On the wall hung large words: 2026 Certified Software Professional Junior / Senior.

I glanced at the clock. It was 8:25. The contest was about to begin. Excitement tangled with nervousness inside me.

The morning contest — CSP-J — started. I skimmed through the problems first. They looked fairly manageable, probably because this was the Junior round. I finished the first two problems quickly and moved on to the third one. It was trickier. I puzzled over it for nearly 30 minutes with no full solution, so I settled for grabbing partial points instead.

Next came Problem 4. I read the statement and tried to analyze it, yet I made no real progress. Again, I could only write code to earn partial scores.

After that, I used the calculator to add up my estimated points. Three hundred and four. That was a surprisingly high score, even for me. But after a moment, I told myself it made sense. I had spent three years learning so much about IT. Wasn’t a good result what all that hard work deserved? I argued with myself back and forth.

The Junior round ended. I stepped out to rest, because the Senior round, CSP-S, would take place in the afternoon.

The afternoon contest began. I felt confident, buoyed by my performance that morning. The first problem seemed easy at first glance, and I jumped straight into coding. But my eyes must have been tired. I misread a key condition and wrote entirely wrong code. I had to delete everything and start over.

“Binary search must be the way to go!” I thought. My hunch was right, yet I still failed the final sample test case. I had butterflies in my stomach. I revised my code over and over, overwhelmed by anxiety.

I pushed that thought aside and re-read the problem carefully. “Maybe this is a layered graph problem,” I guessed. I started coding accordingly, but still got nowhere. I could not even get a clean, error-free program. I blamed myself bitterly for my poor coding and comprehension skills.

I circled back to the first problem again, hoping for new inspiration. No ideas came. I could only stare blankly at the screen.

Time was running out. I was still frantically editing my code. My hopes had faded away. I hastily wrote some code for partial points and waited for the inevitable.

The CSP-S contest ended. I walked outside, swallowed by self-reproach. The same thought popped up again: I’d studied IT for three years. Shouldn’t all that effort bring me a good score? This time, the answer was no.

I do not have much to say about this crushing Senior contest. When the official scores were released, I felt nothing. I had already predicted how poorly I would do. Almost everyone around me scored better than I did. Maybe I really lack talent for this. Perhaps this was just how it was always meant to be.

Still, I will never forget this experience.