←back to thread

178 points henwfan | 1 comments | | HN request time: 0.423s | 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
ErroneousBosh ◴[] No.46212263[source]
Why do you need to "grind LeetCode"?
replies(1): >>46212306 #
linguae ◴[] No.46212306[source]
Some job positions are so competitive to get that a candidate with good data structures and algorithms skills but who hasn’t seen a specific LeetCode problem before and needs to solve it on the spot may lose out to a candidate who “grinded LeetCode.” It’s kind of like how a good student still needs to prep for standardized tests.
replies(1): >>46215432 #
1. ErroneousBosh ◴[] No.46215432[source]
Okay, fuck that noise. I'd walk out.

If you're interviewing me you'd better be prepared to ask me about things I do and things you do, and then just give me the job.

If you want parlour tricks, get a dog.