r/AskProgrammers 22h ago

Whats actually the difference between GfG, Leetcode and Striver's sheet for dsa??

Post image

so I'm starting DSA prep from scratch (2nd year, trying to get ahead for internships, placements next year, panicking a bit ngl) and everyone I ask recommends something different lol

some seniors said just do striver's sheet start to finish, some say leetcode is enough if you're consistent, and gfg has like a whole dsa course + articles for everything but idk if its outdated or still good in 2026

anyone actually used more than one of these and can tell me the real difference? like which one is better for actually understanding concepts vs just grinding problems

also open to other suggestions if I'm missing something obvious

1 Upvotes

2 comments sorted by

2

u/Cautious_Heat114 13h ago

People recommend different things because they confuse a roadmap, an execution platform, and an encyclopedia.

These three tools are not competitors; they serve three distinct functions in an engineering preparation pipeline:

[THE OPTIMAL DSA PREPARATION PIPELINE]

  1. THE SYLLABUS: Striver’s Sheet (takeUforward) └─► Tells you WHICH problem to solve next by algorithmic pattern. │ ▼
  2. THE ENCYCLOPEDIA: GeeksforGeeks (GfG) └─► Read the theoretical mechanics if a data structure is completely new. │ ▼
  3. THE ARENA: LeetCode └─► Write the code, execute against edge cases, and analyze runtime memory.

Here is the exact breakdown of the differences and how to use them without getting overwhelmed:

  1. The Differences Deconstructed
  • GeeksforGeeks (The Encyclopedia):

    • What it is: A vast, article-based reference library.
    • When to use it: When you don't know the theory behind a concept (e.g., "How does a Disjoint Set Union work under the hood?" or "What is the formal proof of Kadane's Algorithm?").
    • The drawback: The practice portal is cluttered, and many solutions are written in un-idiomatic C++ or Java. Use GfG as a textbook, not as your primary coding platform.
  • LeetCode (The Execution Engine):

    • What it is: The global industry-standard testing sandbox with strict time/memory limits and comprehensive edge-case test suites.
    • When to use it: To write, submit, and benchmark your actual code.
    • The drawback: It has 3,000+ uncurated problems. If you solve problems randomly, you will waste months on obscure, low-signal puzzles.
  • Striver’s A2Z / SDE Sheet (The Curated Filter):

    • What it is: A structured, sequential curriculum created by a former Google/Amazon engineer that filters LeetCode down to ~180–450 high-yield patterns.
    • When to use it: As your daily checklist. It solves the "what should I solve today?" decision fatigue and groups problems by pattern (Two Pointers, Sliding Window, Trees, Graphs, Dynamic Programming).
  1. The "Understanding vs. Grinding" Trap

Grinding 500 LeetCode problems by memorizing solutions is the fastest way to fail an interview when the interviewer changes one minor constraint.

«You do not need to solve 500 problems. You need to master the Core Algorithmic Patterns:»

  1. Two Pointers & Sliding Window (Array boundaries)
  2. Fast & Slow Pointers (Cycle detection / Floyd's algorithm)
  3. Monotonic Stack / Queue (Next greater element)
  4. Binary Search on Answer Space (Monotonic predicates)
  5. Tree Traversals (BFS vs. DFS, iterative with stack, recursion trees)
  6. Graph Traversals (Topological Sort, Dijkstra, Disjoint Set Union)
  7. Dynamic Programming (Memoization vs. Tabulation state transitions)

The Recommended 2nd-Year Daily Workflow:

  1. Open Striver’s A2Z Sheet. Pick the active topic (e.g., Binary Trees).
  2. If you don't understand the data structure, read the theory on GfG or watch Striver's video breakdown.
  3. Click the problem link and write the code directly on LeetCode.
  4. The 25-Minute Rule: If you are completely stuck after 25 minutes of dry-running with pen and paper, read the editorial/discussion tab, understand the pattern, reset the editor, and write the solution from memory.

«Do not overcomplicate it. Follow Striver for the sequence, solve on LeetCode for the compiler feedback, and consult GfG for the documentation.»

1

u/nian2326076 2h ago

I've used all three, so here's a quick rundown:

  1. Striver's Sheet: Great for structured prep. It gives you a list of must-do problems, usually organized by topic and how often they show up in interviews. Perfect if you want a clear plan.

  2. Leetcode: Awesome for practice with a huge collection of problems at different difficulty levels. Their discussion forums offer great explanations too. Good if you're consistent.

  3. GeeksforGeeks (GfG): It has detailed articles and a wide variety of problems, which is solid for understanding concepts. It can feel overwhelming if you're starting out because there's so much content.

For understanding concepts, start with GfG or Striver's Sheet. For problem-solving, dive into Leetcode. If you want more structured guidance, PracHub is another option I've tried for interview prep.