| I have no idea offhand if that's the full list - it's the list I come up with when I think about the question. But that's the thing - it's a bad question. It should be asked as "what does this do?" or "how do you do this?", like: "What does this code do: foo(1, 2, kw)?" Or: "How do you import all exported names from a module into your module's namespace?" These show your code reading and code writing skills. The original question is based on unreliable use of memory. Memory is great at slightly-fuzzy-key lookups. It is usually terrible for table scans applying a pattern filter. Think of the challenge "Provide 5 common Unix command line utilities start with t"? Most people who actually know 15 or so of them and regularly use 7 or so of them would have trouble providing all 5. Some will just blank for a minute (because there are just no pathways to work from), most will find 2 or 3. People who studied a Unix text book the night before would also know 2 or 3. A few might just totally blank and become affected by the fact they can't even remember something so easy that they will be unable to answer that question, and may affect their interview performance after that. So it just is not in your interest to ask those types of questions. |