In the Life of a Computer Science Student: The Survival Diaries

Episode 2: Does GPA Even Matter?

Does your GPA really matter?

Should you attend every lecture?

Is it possible to maintain good grades and work on personal projects at the same time?

If you’re a Computer Science student, these questions will hit you at some point-usually right after the first wave of assignments starts landing.

Let’s talk about it.


The Reality of University Rhythm

Something I’ve noticed is that the beginning of every semester feels almost deceptively easy.

In the first few weeks, everything feels structured. You attend lectures consistently, stay on top of readings, and tell yourself:

“This semester is going to be different.”

And for a moment… it is.

Then deadlines start stacking. Workload increases. Energy drops. And slowly, attendance and consistency begin to shift.

That’s usually when the real questions start showing up.


So… Does GPA Even Matter?

The honest answer is: yes and no.

The “No” side

In the tech industry-especially in STEM fields-your GPA is not the only thing that defines your value.

Most recruiters and hiring managers care more about:

  • Real-world projects

  • Internships or experience

  • Problem-solving ability

  • Leadership and teamwork

  • How quickly you learn and adapt

You can have a perfect GPA and still struggle to build practical systems.

So in that sense, GPA is not everything.


The “Yes” side

But your GPA is not meaningless either.

It reflects:

  • Your consistency

  • Your ability to understand concepts under pressure

  • Your discipline in academic environments

  • Your ability to handle structured learning

It also matters for opportunities like scholarships, internships, and academic recognition.

So the real answer is not choosing one over the other.

It’s learning how to balance both.


The Real Struggle: Time vs Energy

The hardest part of Computer Science isn’t just the content.

It’s the balancing act.

You’re trying to:

  • Keep your grades stable

  • Learn new programming languages

  • Build personal projects

  • Attend workshops or clubs

  • Maybe even apply for internships

And somehow still function like a normal human being.

That’s where I had to stop and rethink my approach.

Because effort without structure eventually collapses.

That’s when I developed something I now call:

The IEP Method

Identify. Eliminate. Prioritize.

It’s a simple system, but it changed how I manage my workload completely.


1. IDENTIFY

Start by identifying what actually needs your attention.

Not everything deserves equal energy.

For example, in my first semester, I had five modules. Instead of treating all of them the same, I identified the ones that required deeper focus.

Two of them stood out as more demanding:

  • Discrete Mathematics

  • Business Management

These were the modules that needed intentional effort, not passive studying.

Identification is about clarity-knowing where your energy actually matters.


2. ELIMINATE

This doesn’t mean ignoring modules.

It means removing unnecessary pressure and distractions from your workflow.

Not every subject needs the same level of intensity at all times.

Some require:

  • Regular revision

  • Light review

  • Or scheduled study blocks

Once you identify what matters most, you stop overloading yourself trying to treat everything as equally urgent.

Elimination is about reducing mental noise so you can actually focus.


3. PRIORITIZE

Now that you’ve identified and streamlined your workload, you can focus properly.

This is where real growth happens.

You prioritize:

  • Deep understanding over surface-level reading

  • Practice over passive learning

  • Key modules over scattered attention

  • Personal projects alongside academics

For me, this is also where real-world learning started to click.

Because once I started applying what I was learning in class to personal projects, everything made more sense.

You don’t just study Computer Science.

You build it.


Final Thoughts

The truth is, there is no perfect way to survive Computer Science.

But there are smarter ways to navigate it.

Your GPA matters-but it’s not your entire identity. Your projects matter-but they don’t replace your foundation. Your time matters-but only if you manage it intentionally.

If you take anything from this episode, let it be this:

You don’t need to do everything. You just need to do the right things consistently.

And once you find your rhythm, everything starts to feel a little less chaotic...  and a lot more possible.

Thank you for reading Episode 2 of The Survival Diaries.

I'll see you in the next episode.

println("Ciao");

If you enjoyed this article, you might also like Is Computer Science Really Worth It?


Author

Selma Nghinamanu

Known as Ndilly

Computer Science Student |Software Engineer | Founder 


Image Credits

  • Hero image: Photo by Selma Nghinamanu
Sharing the real journey behind university, technology, entrepreneurship, and building a career in tech.

Comments

Popular posts from this blog

In the Life of a Computer Science Student: The Survival Diaries

In the Life of a Computer Science Student: The Survival Diaries