Leetcode For A Year?
I’ve reached a point where I’m comfortable with syntax and building applications, but when I see a blank LeetCode screen, I often freeze. I have solved only 11 problems so far. I do realize that there is a massive difference between writing code and solving problems.
Starting today, December 28th, 2025, I am committing to one year of LeetCode. My goal is to bridge my knowledge gap by solving one problem every day using both Python and C++.
My Strategy
Since I already understand loops, classes, and logic, I don't need to relearn the basics of programming. Instead, I need to learn Pattern Recognition. My 2026 will be focused on moving from "How do I write this?" to "Which algorithm fits this?"
Why Python & C++?
-
Python: To quickly prototype the logic and master the high-level "interview-style" approach.
-
C++: To understand the underlying efficiency. Since I'm new to problem-solving, C++ will force me to be intentional about data types and memory.
The 2026 Roadmap
Phase 1: Breaking the "Blank Screen" (Jan – March)
Focus: Mastering Big O and Linear Patterns.
- Complexity Mastery: Learn to calculate Time and Space complexity for every solution.
- The "Easy" Grind: Focus on Arrays, Hashing, and Two Pointers.
- Language Goal: Implement common sorting algorithms from scratch in both languages.
- Target: 100+ "Easy" problems.
Phase 2: Identifying the Pattern (April – June)
Focus: Moving beyond brute force.
- Sliding Window & Binary Search: Learn how to optimize nested loops into linear or logarithmic time.
- Stack/Queue Logic: Solve problems related to Undo/Redo operations and nested structures.
- C++ Focus: Master the STL (Vectors, Maps, Sets) to write cleaner, faster code.
- Target: 100+ "Medium" problems.
Phase 3: The Non-Linear Shift (July – Sept)
Focus: Recursion and Trees.
- Thinking Recursively: This is usually the hardest hurdle for intermediate devs. I will solve 30+ recursion-based problems.
- Trees & Graphs: Master BFS (Breadth-First Search) and DFS (Depth-First Search).
- Target: 100+ "Hard" problems.
Phase 4: Optimization & Polish (Oct – Dec)
Focus: Efficiency and Interviews.
- Dynamic Programming (DP): Tackle the "taboo" of algorithms. Start with basic memoization.
- Heap/Priority Queue: Learn how to handle "Top K" style problems efficiently.
- Target: Complete the year with a 365-day streak and 300+ unique problems solved.
My Daily Workflow
- The Logic (10 mins): Read the problem and write the pseudocode. No coding yet.
- The Python Implementation (20 mins): Get the solution to pass all test cases using Python’s flexible syntax.
- The C++ Refactor (30 mins): Re-write the solution in C++. Pay attention to
pass-by-reference,pointers, andtype safety. - The Post-Mortem: Read the most "upvoted" solution on LeetCode. Compare their approach to mine.
Success Metrics
- Consistency: A green square on LeetCode for every day of 2026.
- Dual-Repo: A GitHub repo containing 365 folders, each with a
solution.pyand asolution.cpp. - Mental Shift: Being able to read a problem and identify the required pattern within 5 minutes.
Conclusion
Being an intermediate programmer is a great start, but true engineering excellence requires deep problem-solving skills. By the end of 2026, I want the transition from a problem statement to a working, optimized C++ solution to be second nature.
The clock starts now.