Introduction: An Unexpected Challenge

I'm not typically someone who tackles coding challenges or spends hours solving Data Structures and Algorithms (DSA) problems on platforms like LeetCode. But something inside me whispered, "What if participating in a challenge could help me understand coding structures and patterns?" So, I decided to dive in. Thankfully, my teammates shared a similar mindset, and we quickly formed a team, registered with IEEE, and submitted our participation form.

Preparation (Or Lack Thereof)

Preparation? Well, that's a generous term for what I did. I was actually on a family vacation in my mom's hometown and arrived in Kathmandu just two days before the event. My "preparation" consisted of a quick online search of practice problems, which looked intimidatingly difficult. I quickly realized that last-minute cramming wouldn't make a significant difference.

My approach became simple: give my best effort, set realistic expectations, and most importantly, have fun during the challenge.

The D-Day

I arrived early morning at the hotel hosting Nepal's on-site participants. While most participants were students from Pulchowk Engineering College, there were some unfamiliar faces that added an interesting dynamic to the event.

When the challenge officially began, the first question threw me off—it was just a simple message printing task, unscored and seemingly inconsequential. But as the problems started rolling in, we quickly realized this was no walk in the park. In the initial hours, our team was struggling, firmly positioned in the bottom ranks.

The Secret

What saved us was an unwavering determination to at least pass a few test cases, even if solving the entire problem seemed impossible. This strategic approach prevented us from getting stuck on a single question. We divided our work smartly:

1. One teammate would use brute force techniques to pass initial test cases
2. Another would focus on optimization
3. The third would tackle the most challenging problems, regardless of the time investment

The result? An epic all-nighter that set us apart from other teams who took turns resting.
(Pro tip: I don't actually recommend this approach—we consumed far too much coffee and looked absolutely exhausted the next morning!)

The Final Stretch

By morning, despite looking like zombies, we had climbed from the bottom to the top 10 in Nepal. Our initial modest goal transformed into a competitive drive. We became greedy, aiming higher with each passing hour.

In the final minutes of the challenge, we achieved something remarkable—securing second place in Nepal. Ironically, by this point, our bodies had nearly shut down, and we could barely muster the energy to celebrate our achievement.

Conclusion: Lessons Learned

Was it a good experience? Absolutely. Would I participate in another coding challenge? Definitely! However, I'm planning to brush up on my C++ skills before my next adventure. And while the challenge was exhilarating, the idea of another 24-hour coding marathon? Let's just say I'm not rushing into that again.