Code Apex: How a Casual Call Led to a District-Level Coding Victory

The Call That Started It All

"Bro, maza aane. Tuza registration kela aahe for Codeathon 2024. Please meet me at Reliance Mall at 8."

Atharva's voice had that mix of excitement and urgency. No details. No explanation. Just - I registered you, show up.

My response? "Bhai, burrr yeto." (Translation: Alright bro, coming.)

That's how it works with Atharva. No overthinking. No "let me check my schedule." Just trust and go.

Little did I know that casual agreement would lead to one of the most intense 48 hours of my college life.

Welcome to CODEATHON 2024

March 30, 2024. MGM University. District-level coding competition.

The numbers hit different when you see them in person:

• 240 duo teams - that's 480 coders in one venue
• 3 elimination rounds - Aptitude, Quiz, and Problem Solving
• One goal - survive each round and make it to the top

We registered as Code Apex. At the time, it was just a cool name. By the end of the day, it would mean something.

Round 1: The Aptitude Filter

First round is always the bloodbath. Aptitude tests are designed to eliminate quickly.

Logical reasoning. Quantitative aptitude. Pattern recognition. Speed matters more than perfection here.

Atharva and I split the questions. He's faster at patterns. I handle the math-heavy ones better. No ego. Just efficiency.

We watch teams around us finishing early, walking out confident. Some look defeated already.

We don't rush. We don't panic. We just work.

Results come out. Code Apex - Qualified.

Half the teams are gone. We're still in.

Round 2: The Technical Quiz

Second round is where casual participants get exposed. This isn't about Google-fu. This is about fundamentals.

Data structures. Algorithms. System design. Programming paradigms. The works.

Questions come rapid-fire. Multiple choice, but the options are evil - three of them look right until you really think about it.

This is where our different strengths complement each other:

• Atharva: Strong on DSA and algorithm complexity
• Me: Better with system design and architectural questions

We don't just answer. We discuss. Quick, whispered debates. "Are you sure?" "Yeah, trust me." "Okay, going with it."

That sync I felt on day one? It's real. We're thinking in parallel, not in sequence.

Results. Code Apex - Qualified.

Now it's getting real. Only the top teams remain.

Round 3: Problem Solving - The Final Arena

This is what we came for. Real coding problems. Real-time solving. Real pressure.

The format is brutal:

• Complex algorithmic problems
• Timed submissions
• Edge cases that break naive solutions
• Everyone can see the leaderboard updating in real-time

The Strategy

We don't go for the hardest problem first. We go for quick wins. Build score. Build confidence.

Atharva codes. I debug and test edge cases. We swap when he needs a break.

One problem cracks after 20 minutes. Submitted. Accepted. Green checkmark. Dopamine hit.

Leaderboard updates. We're climbing.

The Grind

Two hours of pure focus. No distractions. No phones. Just the screen, the IDE, and the clock.

Some teams solve problems faster but miss test cases. Their solutions get rejected. They panic.

We're slower but methodical. Every submission we make is clean. We test manually before submitting.

The room is tense. You can hear keyboards clicking. Occasional frustrated sighs. Sometimes excited whispers when code compiles.

The Final Push

Last 15 minutes. We're on our final problem. It's a tough one - dynamic programming with optimization constraints.

Atharva writes the core logic. I refactor for edge cases. We test with sample inputs.

Fails.

Debug. Find the issue - an off-by-one error in the loop condition.

Fix it. Test again. Passes.

Five minutes left. We submit.

Waiting for the verdict feels like hours.

Accepted.

The Announcement

All teams gather for results. The tension is unreal. Everyone knows they gave it their all. Now it's just numbers.

They announce from the bottom up. Third runner-up. Second runner-up. Faces light up. Applause.

Then they announce third place - the prize position.

"Code Apex - Sagar Waghmare and Atharva Wandhare!"

For a second, we just look at each other. Did we hear that right?

Then it hits. We made it. Out of 240 teams, we're standing on stage.

What We Won

The trophy is cool. The certificate is great for the portfolio. The prize money is nice.

But here's what we really won:

• Validation - All those hours of LeetCode grinding? They paid off.
• Confidence - We can compete. We can deliver under pressure.
• Partnership - Atharva and I work well together. That's rare.
• Experience - The nervous energy, the competitive environment, the problem-solving under time constraints - you can't learn this from tutorials.

What Made the Difference

Looking back, here's why we succeeded:

1. Complementary Skills

We weren't identical coders. We had different strengths. That's an advantage, not a weakness.

2. Trust

When Atharva said "trust me on this approach," I did. When I said "let me refactor this," he let me. No ego battles.

3. Communication

We whispered constantly. "Try this." "What if we use a hash map here?" "Check line 47." Clear. Quick. Effective.

4. Calm Under Pressure

When solutions failed, we didn't panic. We debugged systematically. Pressure makes some people freeze. It made us focus.

5. Preparation Met Opportunity

The registration was spontaneous. But our skills weren't. We'd been grinding problems for months. When the opportunity came, we were ready.

The Bigger Picture

CODEATHON 2024 wasn't just about winning. It was about realizing something important:

The right partner amplifies your abilities.

Solo coding is great for learning. But pair programming, especially under competition pressure, teaches you things you can't learn alone:

• How to articulate your thoughts quickly
• How to accept feedback without taking it personally
• How to divide tasks based on strengths
• How to maintain morale when things get tough

Atharva's spontaneous "I registered you" turned into one of the best decisions of second year.

To Aspiring Competitors

If you're thinking about entering a hackathon or coding competition, here's my advice:

Before the Competition

• Practice consistently - daily coding beats weekend marathons
• Know your fundamentals - fancy algorithms won't help if you can't implement basic data structures
• Find a coding partner early - test your sync before the competition
• Participate in online contests - Codeforces, LeetCode contests, HackerRank challenges

During the Competition

• Read all problems first - don't tunnel-vision on the first one
• Start with what you can solve - confidence builds momentum
• Test before submitting - failed submissions cost time and morale
• Watch the clock but don't obsess - time awareness, not time anxiety
• Communicate with your partner - silent collaboration doesn't work

After the Competition

• Review your solutions - what could you have optimized?
• Check other teams' approaches - always something to learn
• Don't dwell on mistakes - analyze, learn, move on
• Celebrate regardless of rank - you showed up and competed

The LinkedIn Post That Almost Didn't Happen

After we won, Atharva insisted I post about it on LinkedIn. I hesitated. Felt like showing off.

But he was right. It's not bragging. It's sharing the journey. Inspiring others. Building in public.

That post reached more people than I expected. Seniors congratulated us. Juniors asked for tips. Recruiters noticed.

Your achievements matter. Share them. You earned it.

Final Thoughts

That casual call from Atharva. "Tuza registration kela aahe."

I could have said no. Could have made excuses. Too busy. Not prepared. Maybe next time.

But I said yes. And that "yes" led to:

• A trophy on my shelf
• A line on my resume
• Stories to tell
• Lessons learned
• A stronger friendship
• Proof that preparation meets opportunity when you show up

CODEATHON 2024. Code Apex. 3rd place out of 240 teams.

Not bad for a spontaneous registration.

Thanks, Atharva. For the call, the push, the partnership, and the victory.

Next competition? I'm ready. Just call. I'll be there.

"Bhai, burrr yeto."