3 ms·

I hate medium and hard LC questions in interviews, it's very hard for me to not get panicky, so I'm surprised i'm going to argue against what you're saying: If

I hate medium and hard LC questions in interviews, it's very hard for me to not get panicky, so I'm surprised i'm going to argue against what you're saying: If you want to test raw coding ability, asking someone to implement some very basic graph or tree traversals is a pretty good way to see if they know the basics of conditionals, loops, recursions, maybe hashmaps. If you want to see someone debug something, and you make them run their code it will inevitably fail or not compile the first time...so they'll have to debug.

josephg 5y ago
> If you want to see someone debug something, and you make them run their code I hear what you’re saying, but that doesn’t assess what I want to assess. We all have experience debugging our own code, that we just wrote. But how well can you read someone else’s code? How well can you find and fix bugs in it? It’s a different skill! And it’s vital in a team setting. Or when you’re depending on complex 3rd party packages (which is most of the time). I want coworkers who can read the code I write and debug it when it breaks. That’s a much more useful skill than what leetcode problems train.