After this lesson, you will be able to: Build a portfolio project that applies the algorithms from this sub-track, either an interactive algorithm visualizer or a documented pattern-solutions repository.
Passion project per Curriculum-Upgrade.md. The best way to cement algorithms and show them to employers is to build something that uses them visibly. Pick one of the two briefs and ship it.
Both are portfolio-worthy. Choose the one that fits your goals.
A. Algorithm visualizer (web app): an interactive page that animates sorting (bubble, merge, quick) and/or pathfinding (BFS, DFS, Dijkstra on a grid). The user picks an algorithm and watches it run step by step. Deploy it live. Strong for frontend/full-stack roles.
B. Pattern-solutions repository: a well-organized, documented repo solving 2-3 representative problems for each major pattern (binary search, sliding window, two pointers, BFS/DFS, DP, backtracking, heap/top-K). Each solution has the approach, the Big O, and tests. Strong for backend roles and interview prep proof.
Ship in stages.
M1: Repo + README + test runner. For the visualizer, scaffold a Next.js or plain HTML/JS page; for the repo, set up folders by pattern.
M2: Implement the first algorithms with tests (one sorting algo + one search, or the first three patterns).
M3: Expand coverage to all targeted algorithms/patterns, each tested or animated correctly.
M4: For the visualizer, add controls (speed, input size, algorithm picker) and clear step highlighting. For the repo, add a Big O note and a short approach writeup to every solution.
M5: Polish: README with screenshots or a problem index, CI that runs tests on every push.
M6: Deploy (visualizer to Vercel) or finalize the repo and pin it on your GitHub profile.
For the visualizer, deploy to Vercel and put the live link at the top of the README. For the pattern repo, write a README index that lists each pattern with links to the solutions and the Big O of each. Add a GitHub Actions workflow that runs your tests on every push. Pin the project on your GitHub profile so it is the first thing a recruiter sees.
Building the visualizer but never deploying it, so there is no live link. Solving problems in the repo with no approach notes or Big O, so it reads as copy-pasted. No tests. Letting the project sprawl instead of shipping a focused, complete version. For the visualizer, animating only one algorithm and calling it done. Not pinning it on GitHub, so recruiters never find it.
Sign in and purchase access to unlock this lesson.