Still Learning, Still Exploring — And That's Enough

This is a submission for the 2026 WeCoded Challenge: Echoes of Experience

I can read a coding problem and understand it.
I can follow the logic when someone explains it.
But when it's time to open a blank file and write the code myself — I freeze.
That gap, between understanding and doing, is where I've lived for most of my second year.

The Honest Truth About My Lab Sessions

In lab sessions, we're given problems to solve. Most of them are related to what we're studying — but not quite taught. The expectation is that we figure it out.
So I open the problem. I read it. I understand what it's asking.
And then I open AI.
I copy the code. I paste it. I run it. It works.
I feel a small relief — like I finished something.
But I didn't finish something. I just moved past it.
And the next lab session, the same thing happens. And the next. Each time telling myself I'll actually learn it properly later. That "later" kept moving forward without me.

Watching People Like Me Move Ahead

The pressure in my life doesn't come from a classroom where someone talks over me.
It comes from quieter places.
WhatsApp groups. LinkedIn. Program announcements.
Competitive coding contests. Campus programs. Internship selections.
I watch people who seem exactly like me — same year, same starting point, same course — attempt things I haven't attempted. Get selected for things I didn't even apply for.
And I feel it. A small jealousy. Not bitter. Just honest.
Followed immediately by: maybe I need to at least attempt properly. Maybe I need to practice. Maybe next time.
But next time came. And I froze again.
The problem was never that I didn't understand the question.
The problem was that I couldn't convert understanding into code.
And I didn't know how to fix that — so I kept collecting roadmaps instead of solving problems.

The Room Feels Louder Than I Do

I am a second-year Computer Science student at a top private university in South India.
Sometimes I am one of the few girls in spaces where coding is being discussed — online groups, college chats, technical communities.
I want to participate. When I understand something, when I have a doubt, when I think I could attempt an answer — I want to speak.
But then: What if it's wrong? What if it sounds too basic? What if everyone already knows this?
So I stay quiet.
And once you stay quiet once, it becomes easier to stay quiet again.
By the time I gather confidence, the conversation has already moved on.
It's not that I don't belong. I've never felt that.
I've only felt like I need to get better before I show up.
And that waiting — waiting to be ready — was keeping me stuck.

The Call That Changed the Direction

During the Campus Mantri program of GeeksforGeeks, we had a task to connect with an expert through GeeksConnect.
I was nervous — not because I didn't have questions, but because I wanted to ask the right one.
I asked her about DSA. About what to focus on. About how to stop feeling behind.
She didn't give me a strategy or a roadmap.
She said: "Second year is for exploring. Learn DSA. Explore. Don't rush."
It wasn't dramatic advice.
But it felt like permission.
Permission to stop collecting and start doing.
Permission to not have a title yet.
Permission to build slowly — but actually build.
When the call ended, I didn't feel transformed.
I felt calmer.

What Actually Changed

I stopped bookmarking twelve YouTube playlists and jumping between DSA sheets.
I picked one thing — the GFG 60 Day Challenge — and I started.
When I get stuck, I don't just copy anymore. I ask AI to explain the approaches. I read them. I try to understand which one makes sense. Then I attempt it myself.
It's slower. It's messier. Sometimes I still get it wrong.
But I'm 19 days in. Somehow maintaining.
And that "somehow" feels more honest than any clean transformation story I could tell you.
Half knowledge creates anxiety.
Deep knowledge creates confidence.
I'm not there yet. But for the first time I'm actually attempting — not just moving past it.

Still Learning. Still Exploring.

I still freeze sometimes.
I still feel that small jealousy when someone like me moves ahead.
I still have lab sessions where I don't know the answer.
But I'm getting better at sitting with that discomfort instead of scrolling away from it.
I don't need to call myself an engineer yet.
I don't need to compete with LinkedIn headlines or campus leaderboards.
Right now, I just need to become better than yesterday.
Second year isn't for proving.
It's for exploring.
I'm still learning.
Still exploring.
And for the first time — that feels enough.