When I was in my first year of college, I started learning programming seriously.
My first programming language was Python.
I had already used Python a little bit in school, and I liked it. But when I entered college, I realized that I didn't actually understand programming as well as I thought I did.
So I decided to go back to the basics.
I started learning C, and then moved to C++.
C++ was interesting to me because it forced me to understand things more deeply — memory, pointers, data structures, how things work under the hood, and so on.
Eventually, I started learning Data Structures and Algorithms (DSA) with C++.
But there was something I noticed along the way.
I was learning C++ mainly to solve problems and understand DSA. I wasn't really using C++ to build things.
I would learn a concept, understand the syntax, solve some questions, and then move on.
Later, when I started learning JavaScript, my approach changed.
Instead of only asking:
"How does this language work?"
I started asking:
"What can I actually build with this?"
That changed the way I looked at programming.
With JavaScript, I started exploring things like web development, React, Node.js, APIs, databases, and eventually TypeScript and Next.js.
I wasn't just learning the language anymore.
I was learning what the language could help me create.
And I think that's something I missed when I first started learning C++.
I knew how to write C++.
But I didn't spend enough time asking:
What can I build with C++?
What problems is C++ good at solving?
How is C++ actually used in the real world?
What happens beyond DSA and competitive programming?
Now I'm trying to change that.
I'm continuing to learn C++ more deeply while also learning things like operating systems, networking, DBMS, algorithms, and DevOps.
At the same time, I'm building projects with the technologies I already know.
I'm still learning. I don't have everything figured out.
But one thing I'm trying to do differently now is:
Don't just learn the syntax. Understand the technology, build with it, and figure out where it fits.
This blog is going to be a place where I document that journey.
Let's see where it goes.
Top comments (0)