Graduating from university is a milestone, but walking across the stage to receive the Highest CGPA Award in my engineering branch (Computer Science with specialization in Networking & Security) at VIT (Vellore Institute of Technology) was one of the proudest moments of my academic journey.

Many people assume that topping a branch requires locking yourself in a room and studying 18 hours a day, sacrificing side projects, friendships, and internships. I’m here to tell you that isn’t the case. In fact, it was during these exact years that I built my developer community, worked on multiple side projects, and spoke at conferences.

Here is the exact practical framework I used to achieve academic excellence without losing my mind.

1. The Active Recall & Feynman Technique

Cramming a 500-page textbook the night before an exam is a recipe for stress and mediocrity. Instead, I structured my study sessions around Active Recall and the Feynman Technique.

• Active Recall: Instead of passively reading slides, I would close the presentation and try to write down everything I remembered from memory. Only then would I go back and fill in the gaps.
• The Feynman Technique: Whenever I struggled to understand a complex concept—like public key infrastructure (PKI) or TCP/IP flow control—I would try to explain it in simple terms as if I were teaching a first-year student. If I couldn’t explain it simply, it meant I didn’t understand it deeply enough.

This study method saved me hours of passive revision and helped me score high marks in both theory and lab exams.

2. Leveraged Labs and Assignments for Real Coding

In computer science, theory is only half the battle. The real learning happens when you write code. Instead of treating college lab assignments as chores to get over with, I used them as opportunities to hone my practical software engineering skills.

When we had database or networking labs, I would write clean, well-commented code, structure my database schemas properly, and build solid implementations. This not only earned me full internal marks (which are vital for a high CGPA) but also built the muscle memory needed to pass technical coding rounds for placements.

3. High-Value Time Blocking

Balancing academics, maintaining a high CGPA, and developing side projects like Swiftyn requires strict time management. I used a system called Time Blocking:

1. Academic Blocks: Dedicated hours during the week where I focused solely on lectures, assignments, and preparing notes.
2. Creative/Coding Blocks: Late evenings and weekends were reserved for coding side projects, recording YouTube videos, or writing technical guides.
3. Rest Blocks: Ensuring at least 7 hours of sleep and setting aside time to read books and disconnect.

By separating my focus, I avoided the trap of feeling guilty about studying when I wanted to code, or feeling guilty about coding when I should have been preparing for midterms.

4. Building Relationship with Mentors

VIT has an incredibly rich pool of professors and academic mentors. I made it a point to regularly discuss research papers, security protocols, and system design topics with my professors outside of class hours. Having their guidance not only expanded my knowledge beyond the standard syllabus but also opened doors to academic research opportunities and solid recommendation letters.

Advice for Current Engineering Students

If you are currently pursuing your engineering degree, remember that your CGPA is a key door-opener. It gets you past the initial recruitment filters and opens up prestigious opportunities.

However, a high CGPA without practical skills is useless, just as practical skills without a decent CGPA might restrict your initial placement chances. Aim for the sweet spot: keep your CGPA above 8.5 (or push for the top if you have the drive!), but never stop building, experimenting, and contributing to the developer community.