Join us on clubhouse: https://www.clubhouse.com/house/leetcode-daily
Week 1
Dynamic Programming
- Read Dynamic Programming Notes Hackerearth
- Read DP Tutorial involving grids
- Read TopCoder Tutorial on DP
- Solve the following classical problems:
- Solve the following MISC problems:
Week 2
Trees & Graphs
☆ | Problem Link | Finished |
---|---|---|
★☆☆ | Diameter of a Binary Tree | |
★☆☆ | Path Sum | |
★★☆ | K-th smallest element in a BST | |
★★☆ | Find duplicate subtrees | |
★★☆ | Lowest Common Ancestor of a binary tree | |
★★★ | Sum of distances in tree |
- 🎥Finding Bridges in Graphs
- 🎥Articulation Points
- 🎥Dijkstra's Shortest path
- Bellman Ford algorithm
- 🎥Floyd Warshall's algorithm
- 🎥Kruska's Minimum Spanning Tree
- 🎥Prim's MST Algorithm
- UVa 00315: Network (finding articulation points)
- UVa 00796: Critical Links (finding bridges)
- CF 193A: Cutting Figure
Week 3
String Algorithms
- Basics of String manipulation
- KMP algorithm
- Z algorithm
- Z algorithm II
- Manachar's algorithm
- Manacher's algorithm II
- Rabin-Karp and KMP TopCoder
☆ | Problem Link | Finished |
---|---|---|
★★☆ | Find the substrings | |
★★☆ | The Cheapest Palindrome | |
★★☆ | Largest Lexicographical Rotation II | |
★★☆ | Monk and Monster | |
★★★ | Prefix Number | |
★★★ | Last Forever |
☆ | Problem Link | Finished |
---|---|---|
★☆☆ | Sherlock and the Valid String | |
★☆☆ | Highest Value Palindrome | |
★★☆ | Sherlock and Anagrams | |
★★☆ | Common Child | |
★★★ | Build a Palindrome |
☆ | Problem Link | Finished |
---|---|---|
★☆☆ | Petya and Exam | |
★★☆ | Password | |
★★★ | Prefixes and Suffixes |
Week 5
Data Structures
Week 6
Square Root Decomposition
- Tutorial 1: Base Concept + Mo's algorithm
- Tutorial 2
- Tutorial 3 : Read the comments
- Tutorial 4 : Video Lecture, find slides in video description
- Tutorial 5 : Exhaustive PDF
- Tutorial 6 : Mo's Algorithm
Week 7
Segment Tree
Week 8
Fenwick Tree
Why use this list?
Since getting better at competitive programming takes a lot of effort, you need to keep practicing a lot of problems. This list will keep you focussed and you will have a target with you that you need to finish atleast these many problems before moving on. It can help you organize your practice.
How to use this list?
The Github markdown's task list feature is used to check progress.
Create a new branch so that you can check items like this, just put a x in the brackets: [x]
- One time steps:
-
Fork this repository.
-
Clone the forked repository.
git clone https://github.com/your_user_name/Get_Better_at_CP_in_2_Months.git
-
Create a new branch for tracking your progress. Let's name this your_user_name
git checkout -b your_user_name
-
Add remote
git remote add your_user_name https://github.com/your_user_name/Get_Better_at_CP_in_2_Months.git
-
Marking tasks as completed and pushing to your branch:
git add . git commit -m "Completed tasks x and y" git rebase your_user_name/master git push --force
-
Keeping your fork's list updated with the changes made here:
git remote add upstream https://github.com/sahilbansal17/Get_Better_at_CP_in_2_Months.git git checkout master git pull upstream master git push your_user_name master
Refer to this for understanding more about Fork and PR workflow.