←back to thread

178 points henwfan | 2 comments | | HN request time: 0.413s | 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
pelagicAustral ◴[] No.46204606[source]
Any company using leetcode as their primary way to assess competency is time wasting, soulless black hole unworthy of any real talent.
replies(5): >>46204740 #>>46204776 #>>46204921 #>>46205049 #>>46209004 #
neilv ◴[] No.46204740[source]
Any company still using LeetCode at all during interviews is signaling that either they are run like a frat house, or are so dim/indifferent that they're unwittingly cargo-culting one.
replies(1): >>46227301 #
1. stackedinserter ◴[] No.46227301[source]
Or it's just big corpo policy that everyone except HR hates and is just hard to change.
replies(1): >>46256998 #
2. neilv ◴[] No.46256998[source]
I like your optimistic theory.

I'm the type to talk with HR about when the company could do something better, and some of them appreciate it.

(Most recent was when a company was starting each Monday morning with a miserable cross-hemisphere all-hands meeting videoconf... that sucked the life out of the recharged energy people came back from the weekend with, for the potentially rewarding work we were doing. The company improved.)