INTRODUCTION
My DSA Journey
*Learning in public. *
I’ve decided to learn Data Structures and Algorithms in a structured way, and instead of keeping my notes buried in a notebook, I’m documenting everything here.
This isn’t a tutorial, and I’m not claiming to be an expert. Think of this as a journal—a place where I record what I learn, the problems I solve, the mistakes I make, and the lessons I pick up along the way.
Why I’m Doing This
Like many computer science students, I’ve always known that DSA is important. It’s the backbone of problem-solving, software engineering interviews, competitive programming, and writing efficient code.
But knowing that it’s important isn’t enough.
This time, I’m focusing on learning it properly—understanding concepts, recognizing patterns, and building consistency instead of rushing through topics.
What You’ll Find Here
As I progress, I’ll document:
- Concepts I learn
- Key takeaways and insights
- Mistakes and common pitfalls
- LeetCode problems I solve
- Different approaches and optimizations
- My progress over time
Some posts may be short notes, while others may be detailed breakdowns of problems that challenged me.
The Goal
I’m not trying to finish DSA as quickly as possible. And it’s not the first time i am learning DSA.
I’m trying to build a strong foundation that will help me become a better software engineer and a better problem solver.
Consistency matters more than speed.
Why Document Publicly?
Writing things down forces me to understand them better.
It also gives me a way to look back and see how much I’ve improved over time. If these notes help someone else who’s on the same journey, that’s an added bonus.
What’s Next?
I’ll start from the fundamentals and gradually work my way through more advanced topics. Every post represents another step forward.
This is the beginning of my DSA journey.
Let’s see where it takes me.
Here Is my leetcode account.
I am also posting my DSA progress on linkedIn account.