1. Trying to Learn Too Many Things at Once

In my early semesters, I jumped into everything  Python, Java, web development, data science, and even cybersecurity.
The result?
I knew a little bit of everything but wasn’t good at anything.

What I learned:
Pick one skill, build one project, finish it, then move to the next.

Consistency beats speed.

2. Avoiding Documentation Because It “Looked Boring”

I used to search YouTube or copy code from blogs instead of reading official documentation.
But when I finally learned to read documentation, everything became easier  fewer bugs, cleaner code, and faster learning.

What I learned:
Documentation is actually the shortest path to mastery.
It’s clear, structured, and always updated.

3. Not Working on Real Projects Early

For a long time, I only solved assignments and classroom exercises.
No portfolio, no personal projects, nothing to show.

What I learned:
Projects are the real proof of your skills.
Even simple projects like a calculator app, weather app, or a small data analysis report can help build confidence and your portfolio.

4. Being Afraid to Ask Questions

Whether in class or online forums, I hesitated to ask questions because I thought they might be “too basic.”

What I learned:
Everyone starts somewhere.
Good programmers ask great questions.
Asking early saves hours of debugging later.

5. Ignoring Soft Skills

I focused only on coding, forgetting communication, teamwork, time management, and teaching skills.

But as I started teaching O-Level CS and working with others, I realized soft skills matter just as much as coding.

What I learned:
A programmer who communicates well, explains ideas clearly, and manages time will always stand out.

Final Thoughts

Mistakes are part of the journey. What matters is learning from them.
Every semester teaches me something new, not only about technology but also about myself.

If you’re a CS student reading this:
Keep learning, keep experimenting, and don’t be afraid to make mistakes just make sure you grow from them.