From Zero to Software Engineer — My First Year Coding Story

Let me be honest with you: when I joined B.Sc. Computer Science, I had never written a single line of code in my life.

Not a for-loop. Not an if-statement. Nothing.

My classmates seemed to already know what a variable was. I was Googling "what is programming" the night before my first lab.

The Panic Phase (Semester 1)

The first program we had to write was a Java console app that calculated the area of a circle.

It took me three hours.

I couldn't understand why System.out.println needed a semicolon. I accidentally deleted my entire file twice. I cried a little.

But I also noticed something — the moment it finally ran and printed the right number, I felt something click. Like, I told a machine what to do and it did it.

That feeling kept me going.

The "I Think I Get It" Phase (Semester 2)

I stopped trying to memorize syntax and started trying to understand concepts.

What is a class? A blueprint.
What is a method? A reusable instruction.
What is an object? A specific thing built from that blueprint.

Once I stopped treating Java like a foreign language and started treating it like logic — everything got easier.

I built a simple student grade calculator for a college assignment and for the first time, I actually enjoyed it.

The "YouTube University" Phase (Year 2)

I discovered that the best teachers were on YouTube and Udemy, not always in the classroom.

I completed:

Java for Complete Beginners on Udemy
Spring Boot tutorials by Amigoscode
Angular - The Complete Guide by Maximilian Schwarzmüller

I would wake up at 6am, watch 2 hours of tutorials, then spend the rest of the day trying to build something from scratch.

Building Eduquic — My First Real Project

By second year, I had enough confidence to build something I actually cared about.

I wanted to build an AI-powered learning platform — basically a smarter version of the platforms I was using myself.

I had no idea how to use OpenAI APIs. I had never touched Prisma or Clerk. I broke the app probably 200 times.

But I shipped it.

That project taught me more than any lecture. Every bug was a lesson. Every feature was a milestone.

The Capgemini Chapter

By the time I graduated with a 9.97 CGPA, I had real projects under my belt, certifications in Java, Spring Boot, Angular, and AWS — and most importantly, the habit of building things even when I didn't know how.

Capgemini hired me as a Software Engineer. Within months, I was working on a live telecom enterprise platform for Nuuday, delivering production features, and even mentoring newer trainees.

What I'd Tell First-Year Me

Stop waiting until you "know enough" to build things. Build before you're ready.
Confusion is not a sign you're bad at this — it's a sign you're learning.
Find one project you actually care about and build it. The motivation will carry you through the hard parts.
CGPA matters, but projects matter more.
Ask questions loudly. The ones who succeed are usually the most curious, not the most talented.

The journey from System.out.println("Hello World") to deploying microservices on a production telecom platform wasn't linear. It was messy, confusing, and occasionally exhausting.

But it was absolutely worth it. 🚀