Skip to main content

Command Palette

Search for a command to run...

From Memorizing to Building: My First Lesson in Computer Science 🚀

Updated
•2 min read
From Memorizing to Building: My First Lesson in Computer Science 🚀
A
"Computer Science Student & Aspiring Technical Writer | Passionate about Software Engineering, AI, and Tech Innovation. I enjoy breaking down complex concepts and sharing insights with the global developer community."

When I first started my Computer Science journey, I walked in with a "High School Mindset." I thought learning meant reading thick textbooks, memorizing definitions word-for-word, and highlighting notes for exams.

But very quickly, the world of Tech taught me a hard truth: You can't memorize your way into becoming a developer.

The "Aha!" Moment đź’ˇ

In those first few weeks, I found myself frustrated. I knew the definitions, but I couldn't solve the problems. That’s when it clicked:

"IT is a "doing" field, not just a "reading" field."

Here are the three fundamental shifts that completely transformed my learning process:

1. Practice Over Reading đź’»

You can read about a Loop or a Function for hours, but you won’t truly understand it until you write it, run it, and—most importantly—see it fail.

My New Rule: For every 30 minutes of theory, I spend 60 minutes coding.

The Lesson: If your hands aren't on the keyboard, you aren't truly learning; you're just observing.

2. Googling is a Superpower 🔍

I used to think that "real" developers had everything memorized. I was wrong.

Professional developers use Google, Stack Overflow, and AI tools every single day.

The Shift: The goal isn't to know every answer by heart. The real skill is knowing how to ask the right question and how to navigate the documentation to find the solution.

3. The "Rubber Duck" Method 🗣️

Whenever I struggle with a complex concept, I try to explain it to a friend—or even to my rubber duck!

The Test: If I can’t explain a concept simply, it means I don’t understand it well enough yet. This realization is exactly why I started writing this blog—to bridge the gap between "knowing" and "explaining."

The Journey Continues... 🌟

Studying Computer Science can feel overwhelming, but the magic happens when you stop trying to be a "memory card" and start being a "builder." Don’t fear the red error messages; they aren't failures, they are just the steps to discovering what works.

What about you? What was your "Aha!" moment when you first stepped into the world of programming? Let’s discuss in the comments! 👇