My Competitive Programming Journey: From Beginner to Instructor
How solving 100+ problems taught me more about engineering than any framework, and why I now teach CP at KUET.
Why competitive programming
I started CP the way most people do: out of curiosity, then out of frustration, then out of habit. The first 20 problems were painful. The next 50 were illuminating. By 100, I'd internalized patterns I now use every day at work — sliding windows, prefix sums, binary search on the answer.
What CP actually teaches
- Decomposition — break a fuzzy problem into smaller, well-defined steps.
- Edge cases — you'll never write a clean
ifagain without thinking about bounds. - Communication — explaining a solution clearly is a superpower.
Teaching at SGIPC
I took instructor sessions for SGIPC, KUET's competitive programming circle. The biggest lesson: don't show solutions. Show intuition. The "aha" moment is what students remember.
Recommended path
- Solve 30 easy problems on Codeforces.
- Read the editorial even if you solved it — there's always a cleaner way.
- Compete in virtual contests. Pressure reveals gaps.
- Teach someone. If you can't explain it, you don't know it yet.
The 100+ problems I solved in 2024 changed how I write production code more than any tutorial I read.