|
|
|
|
|
|
by pmiller2
2845 days ago
|
|
|
> You may well need to spot a deadlock or a race condition in code. You may well need to spot code that is inefficient by construction, in precisely that kind of situation. How is that relevant to the practice of "memorizing enough canned answers to most of these dang questions"? |
|
|
It's not. Instead, ask something not particular tricky, a bit open ended, and just a little bit involved (at least 3 things interacting) with the purpose of seeing if basic skills can be applied. Instead of looking for an answer that can be memorized, you're looking for evidence to see if people have actually designed, implemented, and debugged something at a level beyond gluing libraries together.