|
Some of my colleagues have argued that when a statement/question uses the work "how", the reader expects to get a list of solutions. Examples:
Is this expectation correct? Does using "how" implicitly indicate that the answer should be all possible solutions/answers? |
|||||||
|
|
No, it doesn't. In the absence of any specific request, such a question invites suggestions which may or may not be comprehensive. |
|||
|
|
|
Of course the "method" or "way to do something" is one answer to a "How" question. But it isn't the only one. "How" also asks about manner. "How come..." is used to ask about the reason. "How is..." asks about condition. "How about..." is used to suggest or ask for your opinion. And it's very common for "How" to ask about degree when you combine it with other words. |
|||
|
|
|
Starting a question with "How" does not restrict the amount of solutions, but it does not implicitly ask for providing a list of possibilities. Such a question requires at the very least one answer. If I do expect a list of possible solution I would ask something along the following two examples which indicate that I like to have the choice between two or more solutions, likely including a discussion about the solutions.
|
|||
|
|
|
If I were asked either of these questions in a conversation, I would expect a discussion about a list of possible solutions with information of pros and cons of each. If somebody were to ask me the second question on stackoverflow, I would only provide them with one answer (if I knew any!) unless they explicitly asked for a comparison of options |
|||
|
|
