Step 01
Solve & document
Work the problem, then immediately write down the pattern and the trade-off — while it’s still fresh, not after moving on.
What’s inside
Built to answer “have I seen this pattern before?” in seconds, not minutes.
Pattern-first structure
Problems are grouped by the underlying pattern — two pointers, sliding window, backtracking — so revision targets the concept, not just a topic label.
Multi-language solutions
Key problems are solved in more than one language, which forces a cleaner understanding of the pattern itself, separate from any one syntax.
Notes per problem
Each solution carries a short note on the trick, the complexity trade-off, and the mistake I made the first time through it.
Revision checklists
Grouped checklists make it easy to sweep a whole pattern the night before an interview instead of hunting file by file.
Mentoring companion
Doubles as a shared reference when walking juniors through their own DSA prep — consistent structure, less re-explaining.
Version-controlled history
Every revision lives in git, so old approaches stay visible instead of being overwritten and lost.
How I use it
Step 02
Tag by pattern
File the solution under its pattern folder rather than its source (LeetCode, HackerRank, coursework), so revision stays topic-driven.
Step 03
Revisit before it matters
Before interviews or a mentoring session, sweep the relevant pattern folder instead of re-solving everything from scratch.
Full source
Browse the repo directly
The full set of solutions, notes, and folder structure lives on GitHub — that’s the source of truth, kept current as prep continues.