r/geeksforgeeks • • Jun 30 '26

Free courses I got

Thumbnail
gallery
91 Upvotes

I got all of them for Free. But I'm also doing another course by my cousin which has more long videos.

So should I do this? Is it worth my time? Or just move on to another courses.


r/geeksforgeeks • • Jan 13 '26

Regarding My Previous Post (Tier-3 college to 40+ LPA)

84 Upvotes

Hi guys, I really got good response for my previous post mentioning about my journey from tier 3 college to 40+ LPA Offer. Thank you for that!!

As i mentioned in my previous post I am starting a community... where I will be sharing coding stuff (Patterns and interviews related) , job opportunites and also about hackathons/codeathons.

I seriously want to help students from tier-3 colleges without involving any money kind stuff, and will guide them in proper way to get thier first job. Yes! I might not be a great coder but sure there will be lot of things even i can learn from you guys!

It's open for everyone , anyone can join in this group. We can help eachother and grow together . If u r interested in coding stuff and tech stuff then send message to me , I will add u !

I will also create some activites to motivate you , i will share one pattern a week and then 1 easy and 1 medium question in that pattern everyday and also lot other stuff...

Let's create a space where we can learn and grow together by sharing our knowledge to eachother without involving money!

Trust me !! If you are someone from Tier-3 college and if resume not even getting selected OR If you want to learn coding seriously but dont know HOW then join... with me !!


r/geeksforgeeks • • Dec 31 '25

Some "real world" coding advice I wish someone told me in my first year

48 Upvotes

Hey guys,

I’ve noticed a huge difference between what we learn in our CS classes and what actually happens when you try to build something on your own. College teaches us the theory, but they kind of skip over the messy parts that actually make people want to quit coding.

If you’re feeling stuck or like you’re "not smart enough," you’re probably just hitting one of these common walls:

  • The "Blank Screen" Panic: In class, the professor gives you a starter file or a clear prompt. But when you try to start your own project, it’s just a blank folder and it’s terrifying. The fix: Don't try to build the whole thing at once. Just make one button work. Then make one text box work. It’s okay if your first 100 lines of code are complete garbage.

  • The "Professional Googler" Secret: I used to feel so guilty for looking up basic stuff on Stack Overflow or using AI. I thought "real" coders just knew everything. Truth is, even the pros spend half their day Googling. The skill isn't memorizing code; it's knowing what to search for when things break.

  • The "It works on my machine" Problem: In school, everything is set up for you. In the real world, you’ll spend 2 hours just trying to get a library to install or fixing a weird version error. This isn't "wasting time"—this is the job. Learning how to fix your environment is a huge part of being a dev.

  • Naming things actually matters: In an assignment, naming a variable x or abc is fine to get the grade. But if you look at that code two weeks later, you’ll have no clue what it does. Start naming things exactly what they are, like user_password or total_price. It saves so much shared headache.

Coding is hard, but it’s mostly just a game of who can stay frustrated the longest without giving up.

What’s something you’re currently stuck on that they didn't teach you in class? Maybe we can figure it out in the comments.


r/geeksforgeeks • • Jan 04 '26

Why do so many students recommend GeeksforGeeks for coding prep? Is it actually useful?

47 Upvotes

I had the same question earlier because GeeksforGeeks gets mentioned everywhere, and honestly I thought it was overhyped.

From my experience, the reason students keep recommending it is not because it’s perfect, but because it solves a very real beginner problem — where to start and what to study next.

When I began learning DSA, I was jumping between YouTube, blogs, and random PDFs. I wasted a lot of time. GfG helped mainly in three ways:

  • The DSA articles are structured from basics to advanced, so you don’t feel lost.

  • If a concept confused me, chances were someone had already explained it on GfG in simple terms.

  • Practicing problems topic-wise helped me understand why something works, not just memorize solutions.

It’s not magic — you still have to struggle, debug, and practice a lot. But as a reference + practice platform, it reduced friction for me.

I still use other resources too, but GeeksforGeeks became my “go-to” when I needed clarity or revision quickly.

Curious to know — what resources helped you most when starting out?


r/geeksforgeeks • • Jan 10 '26

Don't wait until 3rd year to start DSA

44 Upvotes

I see a lot of posts here asking if it's "too late" to start coding, so I wanted to share my honest experience as a CSE student currently in the grind.

The mistake I made: I wasted my first semester thinking I'd learn everything from college lectures. Spoiler: I didn't.

What actually works:

  1. Pick one language and stick to it: C++ or Java. Don't jump around.

  2. Consistency > Intensity: Solving 1 problem a day is better than doing 10 on Sunday and quitting.

  3. Resources that helped me: • Logic Building: I started with simple pattern printing problems. • DSA Concepts: I used Striver’s sheet for the roadmap, but for actually understanding the logic behind concepts like Dynamic Programming or Graphs, I found the textual articles on GeeksforGeeks way faster than watching 2-hour videos. Sometimes you just need to read the code to get it. • Practice: LeetCode for contests, but I still go back to GfG specifically for their standard interview questions (like the "Must Do" list) because they are often asked directly in campus OAs.

My advice: Don't just watch tutorials. If you can't write the code on paper (or a whiteboard), you don't know it. Start today, even if it's just 30 minutes.


r/geeksforgeeks • • Jan 01 '26

Mistakes I (and many students) made while learning DSA

39 Upvotes

I’ve been learning DSA for a while now, and looking back, I realize most of my struggles weren’t because DSA is impossible, but because of the mistakes I kept repeating.

The biggest one? Jumping straight into medium or hard problems without really understanding the basics. I used to think struggling meant I was “learning,” but honestly, half the time I was just confused because my foundations weren’t clear. Another common trap is memorizing solutions—watching a YouTube video, feeling confident, and then completely blanking when a similar problem shows up.

I also ignored time and space complexity early on. As long as the code worked, I moved on. Later, I realized interviews care a lot about why your solution is efficient, not just whether it passes test cases. Inconsistency was another killer—doing DSA seriously for a few days and then disappearing for weeks. Progress slowed way more than I expected.

One mistake I still see a lot (and used to do myself) is skipping revision. You finish arrays, move to stacks, and never touch arrays again… until everything feels new during interviews. And yeah, recursion and pointers felt scary, so I avoided them—but that just made trees and DP even worse later.

What actually helped was slowing down, following a topic-wise roadmap, doing dry runs, and focusing on understanding instead of speed or problem count. DSA stopped feeling like a “placement-only thing” and more like a way to think better.

Just sharing this in case someone else is stuck in the same loop. If you’re learning DSA right now—what’s the one thing you’re struggling with the most?


r/geeksforgeeks • • Dec 30 '25

How I stopped ‘collecting’ resources and finally cracked DSA for placements

35 Upvotes

In my 2nd year I was doing what most of us do: bookmarking 50 DSA playlists, saving LinkedIn posts, joining every “placement prep” WhatsApp group… and still not being able to solve a simple medium question without peeking at the solution.The real problem wasn’t “lack of resources”, it was:No fixed topic-wise roadmapNo habit of solving timed questionsNo consistent revision of patternsWhat finally worked for me:Fixed one primary resource I decided to stop juggling and pick one main platform for DSA practice + theory. I chose GeeksforGeeks because it had:Topic-wise articles where I could quickly revise conceptsA lot of company-tagged questions for placement-style practiceDifficulty filtering so I could move from easy → medium → hard gradually You can pick any platform you’re comfortable with, but limiting to one as “main hub” helped a lot.Made a 90-minute daily routine20–30 mins: revise 1 concept (like sliding window, binary search, DP basics)45–60 mins: solve 3–4 questions on that topicLast 10 mins: write a short note in Notion/OneNote on what new I learned I treated it like gym reps instead of “finish this 450-question sheet in 2 weeks”.


r/geeksforgeeks • • Oct 16 '25

Did GeeksforGeeks cut off Brazil? I tried accessing it today and got a 403.

21 Upvotes

r/geeksforgeeks • • Jan 11 '26

Honestly, the "blank screen" anxiety is real. Here’s how I stopped failing at DSA problems.

19 Upvotes

​Hey everyone, ​I wanted to share something that took me way too long to figure out. For months, I was stuck in "tutorial hell"—I’d watch a video on Linked Lists, think I understood it, and then stare at a blank LeetCode screen for an hour feeling like a failure. ​If you’re feeling like you’re "just not built for logic," trust me, you probably just lack a structured workflow. Here is the 3-step routine I used to break the cycle: ​1. The "Pen & Paper" Rule (No Coding for 10 Mins) Most of us jump straight into for loops. Now, I force myself to dry-run the logic on paper first. If I can't explain the solution to a 5-year-old using physical objects (like cards for an array), I don't touch the keyboard. ​2. Pattern Recognition over Rote Learning Stop trying to memorize 500 individual problems. Focus on the 10-12 core patterns (Sliding Window, Two Pointers, Backtracking, etc.). ​Pro Tip: When I’m stuck on a pattern, I usually head over to GeeksforGeeks. Their articles are great because they often break down the "Naive Approach" vs. the "Optimized Approach" side-by-side. Seeing why a solution evolves from O(n2) to O(n) helped me more than just seeing the final code. ​3. The 30-Minute Wall If you haven't made progress in 30 minutes, look at the editorial/discussion. But here’s the trick: don’t just copy it. Read the logic, close the tab, and try to implement it from memory. If you fail, wait 2 hours and try again. ​This shift took me from struggling with Easies to comfortably handling Mediums. It’s not about being a genius; it’s about having a repeatable system. ​What’s the one thing that helped DSA finally "click" for you? Curious to hear your methods! ​Why this works: ​Value-First: It provides a genuine study framework (The 30-minute rule, Pen & Paper). ​Authentic Mention: GeeksforGeeks is mentioned as a specific tool for a specific problem (understanding complexity evolution), which feels like a recommendation from a friend. ​Engagement-Focused: It ends with a question to spark a discussion, making it less likely to be flagged as spam.

geeksforgeeks

r/geeksforgeeks


r/geeksforgeeks • • Jan 09 '26

What I wish I did earlier for DSA in college

19 Upvotes

I wasted my first year randomly watching tutorials without solving enough problems. In second year, I changed my approach:

Pick one topic per week

Solve at least 10–15 problems of the same pattern

Revise mistakes instead of moving on fast

Write solutions in my own words

This helped me recognize patterns faster during tests and interviews. Consistency mattered more than the number of platforms or resources.

If you’re early in college, focus less on “finishing DSA” and more on actually understanding why solutions work.


r/geeksforgeeks • • Jan 12 '26

Title: If you’re in 2nd or 3rd year, don’t wait for “final year prep”

17 Upvotes

I used to think placements were a final-year problem. Looking back, I wish I had started lightly earlier.

Not intense prep — just basics and regular problem-solving. I used GeeksforGeeks mostly to understand fundamentals when things felt confusing.

If you’re early in college, start small. Future you will be glad you did.


r/geeksforgeeks • • Jan 10 '26

Why "Tutorial Hell" is destroying your ability to problem-solve

17 Upvotes

Too many new developers are falling into the trap of "passive learning"—watching coding videos like entertainment without actually engaging with the logic.

The biggest issue is the expectation of being "spoon-fed." A perfect example is the "Greatest Sum Divisible by Three" problem. Many beginners get stuck and immediately look for a code solution, but the answer isn't about Python or Java syntax—it's about basic math.

If you sit down with a piece of paper, you realize it’s just about remainders (modulo arithmetic). If your sum has a remainder of 1, you remove the smallest number with a remainder of 1. You don't need a senior dev to explain that; you just need to think.

If you are struggling with the logic behind these types of mathematical array problems, don't just copy the code. Read a proper explanation of the algorithm to understand why it works.

Reference Resource: For a breakdown of the logic behind these remainder-based problems, check this guide:

Topic: Maximum sum of elements divisible by K

Link: https://www.geeksforgeeks.org/dsa/maximum-sum-of-elements-divisible-by-k-from-the-given-array/: Maximum sum of elements divisible by K

Discussion: Do you feel that modern tutorials make us too lazy to think through the "boring" math parts of programming?


r/geeksforgeeks • • Jan 10 '26

Not a topper, not an expert — just how I made progress with DSA in college

17 Upvotes

I used to jump between random YouTube playlists, PDFs, and courses whenever I tried learning DSA.
After a few weeks, I’d feel overwhelmed, inconsistent, and honestly… demotivated.

The biggest problem wasn’t difficulty.
It was lack of structure.

Here’s what actually helped me move forward:

1. I stopped trying to learn everything at once

Instead of “DSA in 2 months”, I picked one concept at a time (arrays → strings → recursion).
Progress felt slower, but retention improved a lot.

2. I followed a roadmap, not random videos

Having a checklist removed decision fatigue. I didn’t waste time thinking “what next?”
That’s when platforms like GeeksforGeeks helped — mainly for:

  • Topic-wise explanations

  • Beginner-friendly examples

  • Practice problems sorted by difficulty

(Not promoting — just sharing what I actually used.)

3. Consistency > Motivation

I fixed 30–40 minutes daily, no matter what.
Even bad days counted. That mindset shift changed everything.

4. I treated confusion as progress

Earlier, I’d quit when stuck.
Now, if a problem confuses me, I know I’m learning something new.

I’m still learning, not an expert.
But this approach helped me stay consistent instead of quitting every 2 weeks.

Curious —
👉 What’s the hardest part for you while learning programming or DSA right now?

Would love to hear different perspectives.


r/geeksforgeeks • • Jan 09 '26

One thing college didn’t teach me about placement prep

16 Upvotes

College taught subjects, not how to prepare. I learned this later: Basics matter more than advanced topics Explaining logic is more important than speed Consistency beats long study hours I used common resources like GeeksforGeeks to clear fundamentals, but discipline mattered more than any resource. Sharing for juniors who are just starting.


r/geeksforgeeks • • Jan 07 '26

How I started learning DSA in college (beginner-friendly approach)

16 Upvotes

I was completely confused about Data Structures in my first year. There were too many topics and too many resources, so I kept jumping from one thing to another without real progress. What finally worked for me was keeping things simple and structured: • I started with arrays and strings instead of jumping to trees/graphs • Learned time & space complexity early (this helped a lot later) • Practiced only easy problems until I was comfortable • Focused on understanding the why, not just memorizing code I used a mix of articles + coding practice. Structured explanations with examples helped me a lot in the beginning (platforms like GeeksforGeeks are useful for that), but consistency mattered more than the resource. If you’re a beginner, my advice would be: Don’t rush advanced topics. Build strong basics first and practice regularly, even if it’s just 30 minutes a day. Hope this helps someone who’s feeling stuck like I was 👍 esh content ko pic ke sath post kre ya nhi


r/geeksforgeeks • • Jan 07 '26

I was stuck in tutorial hell during college — this is what finally worked for me

16 Upvotes

I’m a pre final-year CS student, and for the longest time, I felt completely lost while learning coding.
I watched tons of YouTube tutorials, but the moment I tried to solve problems on my own — blank.

What helped me break out of this wasn’t switching languages or buying a paid course, but changing how I practiced.

Here’s what actually worked for me:

  • I picked one topic at a time (arrays, strings, recursion, etc.)

  • Solved easy problems first without worrying about optimization

  • Read editorial/explanations only after trying myself

  • Maintained a small notebook of mistakes I repeated often

One free resource that genuinely helped during this phase was GeeksforGeeks — mainly because:

  • Problems are categorized by topic

  • Explanations are beginner-friendly

  • You can cross-check concepts quickly before interviews

I’m still learning (definitely not an expert), but this approach helped me move from “just watching” to actually solving problems.

Would love to know — what helped you get out of tutorial hell?

(No promo, just sharing what worked for me.)


r/geeksforgeeks • • Jan 02 '26

How I’m actually improving my DSA (after struggling for months)

16 Upvotes

I used to think DSA was hard because I wasn’t “smart enough”. Turns out, it was hard because I was doing it the wrong way. I was randomly solving problems, switching languages, watching 10 tutorials a day… and still stuck.

Here’s the step-by-step approach that finally started working for me. Posting this in case it helps someone else who’s in the same loop.

First, I stopped rushing. I went back to basics — time complexity, arrays, strings, recursion. Not fancy topics, just understanding why things work. Dry runs helped a lot more than watching solutions.

Second, I picked one language and stuck to it. No more hopping between Python, C++ and Java. Once syntax stopped being a distraction, logic became clearer.

Third (this is important), I stopped doing random problems. I followed a topic-wise order: arrays → strings → recursion → hashing → stacks/queues → linked lists → trees → graphs → DP. One topic at a time. No skipping.

For every topic, I followed a simple cycle:
learn → solve easy → solve medium → reflect. Reflection was the game changer. I started asking: why did this approach work? where did I get stuck? what pattern was used?

Before checking solutions, I forced myself to write my own logic in plain English. Even if it was wrong. That struggle actually trains your brain — copying solutions doesn’t.

I also started maintaining short notes (just key ideas and mistakes). Over time I realized DSA is less about IQ and more about pattern recognition.

Revision mattered more than solving new problems. I revisited old questions after a few days and weeks. It hurt seeing I forgot things — but that’s how they actually stick.

Once I was comfortable, I added timed practice (30–45 mins). No distractions. Even failing within time helped build interview confidence.

The biggest mindset shift: consistency > intensity.
1–2 good problems daily beats solving 20 in one random burst.

DSA still feels hard — but now it feels manageable. If you’re stuck, it doesn’t mean you’re bad at coding. It probably just means your process needs fixing.


r/geeksforgeeks • • Dec 25 '25

QUORA QUESTION : How should a college student prepare for coding placements from scratch?

16 Upvotes

When I started my coding journey in college, I was honestly confused. I didn’t know what language to choose, how much DSA was enough, or how to stay consistent with academics going on.

What helped me was following a simple, realistic structure instead of random YouTube hopping.

Here’s what worked for me:

  1. Pick ONE language first (don’t multitask) I chose C++ because most placement problems are easier to handle with STL. Python or Java is also fine—just stick to one.

  2. Focus on DSA basics before advanced topics Arrays, strings, recursion, stacks, queues, and basic linked lists matter more than jumping straight to DP. Many students skip fundamentals and struggle later.

  3. Practice problems daily (even 2–3 is enough) Consistency matters more than quantity. Solving a few problems daily builds confidence.

  4. Use structured resources instead of random content I personally found platforms like GeeksforGeeks helpful because:

Topics are structured

Explanations are beginner-friendly

Problems are tagged by difficulty

I didn’t rely on one source only, but GfG was a solid reference whenever I felt stuck.

5. Don’t ignore projects & CS basics Even small projects and basic OS, DBMS, and CN questions can make a difference during interviews.


r/geeksforgeeks • • Jan 02 '26

Confusion at its peak.. AI feels overcrowded, web feels meh, quant maybe? Legends, I need your help....

15 Upvotes

I’m currently in my second year at an okay-ish university with an okay-ish CGPA. I’m honestly pretty confused about what domain I should be targeting for internships.

Initially, I wanted to get into AI/ML, but it feels like everyone I know is already doing it. Kaggle, Coursera, same projects, same buzzwords and I’m not sure I actually enjoy it enough to go deep.

I’m fairly proficient in DSA, and I’ve built a few web stack projects. Frontend especially feels extremely wide and honestly boring now. Backend is more interesting to me, but even there I’m unsure how to specialize instead of just doing “generic web dev”.

At the back of my mind, I’ve always had this thought about doing something quant-related, like a quant developer role or something adjacent. My language fundamentals are solid, and I enjoy problem-solving and systems-level thinking more than UI work.

So my question is:
What domain should I realistically focus on right now for internships?

Please don’t say “it’s too early to decide”. I’m from India either you follow the classic SDE role properly, or you risk ending up with skills that don’t convert into opportunities. Very few people actually get to “just follow their passion” here.


r/geeksforgeeks • • Jan 13 '26

Title: Anyone else keep restarting DSA prep every few weeks?

14 Upvotes

Not sure if it’s just me, but I kept “starting DSA” again and again. I’d study seriously for a week, then college work or exams would take over and everything would stop.

What helped me was lowering my expectations. Instead of chasing perfect schedules, I just focused on understanding one topic at a time.

I mostly used GeeksforGeeks whenever I needed a clear explanation or a few practice problems. Nothing fancy — just slow, regular practice.

I’m still learning, but at least now I’m consistent. How do you guys manage coding with college stuff going on?


r/geeksforgeeks • • Jan 04 '26

Journey

14 Upvotes

I was stuck in DSA for months — this is what actually helped me In my early college days, I felt completely lost with DSA. I knew it was important for internships and placements, but I kept jumping between topics, solving random problems, and honestly… making no real progress. What changed things for me was stopping the “solve everything” mindset and focusing on structure instead. Here’s what worked: Pick one topic and stay with it until the basics are clear Understand the logic before touching the code Solve fewer but well-chosen problems Maintain a simple mistake notebook (game changer) For learning and revising concepts, I used GeeksforGeeks mainly as a reference because explanations are straightforward and topic-wise, which helped me avoid feeling overwhelmed. I’m still learning, but now at least I know why I’m practicing something — not just copying solutions. For anyone struggling with DSA: progress comes from consistency and clarity, not speed. Would love to know — what helped you break out of the DSA confusion? Thanks to GeeksforGeeks


r/geeksforgeeks • • Jan 06 '26

I was stuck in DSA for months — this is what finally worked for me

13 Upvotes

’m a college student and honestly, DSA felt overwhelming at first.

I kept jumping between topics — arrays one day, trees the next — and nothing was sticking.

What changed things for me was following one structured path and solving problems daily, even if it was just 2–3.

One resource that helped me a lot was GeeksforGeeks, especially because:

Topics are broken down clearly

Practice problems are sorted by difficulty

Explanations are beginner-friendly

I’m still learning, but consistency helped more than motivation.

If you’re stuck like I was, start small and stay consistent.

What helped you stay disciplined while learning DSA?


r/geeksforgeeks • • Jan 04 '26

GeeksForGeeks not just a website.

13 Upvotes

Most people see GeeksforGeeks as a DSA website. That’s only a fraction of its real value.

As a student, here’s what actually helped me:

  1. Structured thinking, not shortcut thinking The explanations force you to think in terms of why an approach works, not just what the answer is. This mindset matters more than memorizing solutions.

  2. Consistency beats motivation GFG problems are not “flashy,” but they are reliable. Showing up daily and solving even one problem compounds faster than binge-learning once a week.

  3. Interview reality check Many questions feel basic until you try explaining them clearly. That gap between “I know this” and “I can explain this” is where most candidates fail.

  4. Foundational clarity > advanced hype Everyone wants to jump to ML, Web3, or AI. GFG quietly fixes your fundamentals so you don’t collapse later when things get complex.

  5. Community exposure Contests, discussions, and editorial comments show you how differently the same problem can be approached. That flexibility is underrated.


r/geeksforgeeks • • Jan 08 '26

How I stopped feeling lost in early college and found direction in tech (as a first-year student)

12 Upvotes

When I started college, my biggest confusion wasn’t how to code — it was what to learn and in what order.

In my first semester, I explored many things just to understand the tech ecosystem. I participated in hackathons and competitions like SIH, Mumbai Hack 2025, and an IEEE Ideathon. These experiences were exciting, but after every event I felt the same question coming back:
Am I actually moving in the right direction, or just trying random things?

My college (Central University of Jammu) recently started its BTech department, so the tech culture and senior guidance system are still developing. As freshers, we don’t really have many seniors or mentors to ask for realistic advice, which made things even more confusing.

By my second semester, I realized that AI/ML—especially Generative AI—really interests me. But I also knew I didn’t want to spend another semester just experimenting blindly. I wanted clarity:
What skills actually matter?
What should I focus on as a beginner?
What mistakes should I avoid early on?

What helped me was getting structured guidance instead of random information. In my case, connecting with a mentor through GeeksforGeeks helped me understand how people already working in AI/ML think about learning, projects, and long-term growth. The discussion was honest and practical—more about fundamentals and problem-solving, less about chasing certificates or hype.

That one conversation helped me build a clear roadmap and gave me confidence that I’m not just guessing anymore.

I’m sharing this because I know many first- and second-year students feel the same confusion, especially in colleges where the tech community is still growing.

For seniors or fellow students here:

  • How did you figure out which tech domain to focus on?

  • What helped you avoid wasting time in early college?

  • Do you think mentorship actually makes a difference, or is self-exploration enough?

Would love to hear real experiences and advice.


r/geeksforgeeks • • Jan 06 '26

How I stopped feeling lost while learning DSA as a student. The study method that worked for me

12 Upvotes

I’m a student, and for a long time, I felt completely overwhelmed while learning Data Structures and Algorithms. My problem wasn’t lack of effort; it was lack of structure. I kept jumping between random tutorials, solving questions without understanding the “why,” and losing motivation whenever I got stuck.

What finally helped me was building a simple and consistent learning routine instead of trying to chase every resource at once.

Here’s what worked for me:

I learned one topic at a time:

Arrays, Strings, Recursion, Linked Lists, Trees.

No more hopping around because someone on YouTube claimed, “This topic is more important.”

I followed a learn, practice, reflect cycle.

I’d first understand the concept, then practice a few problems, and later revisit them to see if I really understood the logic.

I started using structured explanations instead of random problems.

The concept pages and example problems on GeeksforGeeks helped a lot, not just for answers but for understanding how to think about the problem. I didn’t treat it like a shortcut site but as a reference when I was stuck or needed clarity.

I stopped comparing my progress to others.

It turns out consistency beats speed. Once I focused on little daily progress, everything felt lighter.

This approach didn’t magically make DSA “easy,” but it made it manageable, and for the first time, I started feeling confident instead of lost.

I’m sharing this in case someone else is going through the same phase. If anyone wants, I’m happy to share the rough topic plan I followed or how I balanced practice with theory.