4 ms·
I think our observations are consistent: I would say that candidates ability to solve leetcode-style problem during an interview reveals very little of their ab
by matklad 3y ago
I think our observations are consistent: I would say that candidates ability to solve leetcode-style problem during an interview reveals very little of their ability to code in the small or in the large. "Algorithms during code interview" is a completely separate genre to what's discussed in the article.
To give a positive example here: when someone sends a 1k lines PR implementing a new big feature, how well a body of a single function is implemented is often a good predictor of whether the whole PR makes sense.
- angarg12 3y agoI'm not sure our observations are consistent. What I'm saying is that I've seen many times people who crush the DSA problem, but struggle to define clean APIs, write clear, maintainable and extensible code, or just design systems. In fact in some cases leetcode makes this worse, with it's emphasis on very terse code (e.g. single letter variables, all code in a single method, hard to understand coding constructs...). About your second point, not to be a dick, but if someone on my team sent a 1k loc single PR for a big feature, I would sit down with them to have a conversation about why that is bad (I have indeed done this before).