←back to thread

178 points henwfan | 1 comments | | HN request time: 0.959s | source

I built AlgoDrill because I kept grinding LeetCode, thinking I knew the pattern, and then completely blanking when I had to implement it from scratch a few weeks later.

AlgoDrill turns NeetCode 150 and more into pattern-based drills: you rebuild the solution line by line with active recall, get first principles editorials that explain why each step exists, and everything is tagged by patterns like sliding window, two pointers, and DP so you can hammer the ones you keep forgetting. The goal is simple: turn familiar patterns into code you can write quickly and confidently in a real interview.

https://algodrill.io

Would love feedback on whether this drill-style approach feels like a real upgrade over just solving problems once, and what’s most confusing or missing when you first land on the site.

Show context
nialv7 ◴[] No.46212238[source]
Actually curious, how often do you find uses for LeetCode patterns in your actual work?
replies(1): >>46213234 #
1. JoeOfTexas ◴[] No.46213234[source]
In web development, you mostly deal with data, sometimes you need to group that data, and some of these algos can help with that.

Most useful when you work with large datasets, if you can reduce a workload that takes hours into minutes or less, congrats, otherwise, you are forced to wait the hours. Either way, job security.