There may be value in limiting the breadth of questions asked. For example, if I was to ask the question
What components should I use to build a quality workstation for under $3000?, there are lots of components and hence individual part recommendations that need to be made. An answer to such a question could easily have the contents of many previously well thought-out answers that go in depth as to what factors need to be taken into account for each component.
How are we going to handle questions like this? I think the following points will need to be addressed in the future:
- How do we mitigate lots of these questions being asked(questions where many components are involved)? A wiki of some sort?
- If a wiki isn't used, as each question may require a unique set of components (database server, gaming machine etc.), do we list all of the components they should look at, or refer them to previously asked questions (best graphics card for gaming under $500 etc.)?
- If we allow these broader questions, are they going to have the same level of detail for each component when compared with a question that is specifically asking about one component, and one use-case?
Having a few standard wiki/new-user pages may be useful in future for directing new users to questions that will inevitably be asked numerous times (What parts do I need to make the best gaming/workstation/server computer? etc.)
Would be interesting to know what you all think about this.
I recently came across this question. It seems as though people are not too fond of it. Is this because it is too broad, or because the OP does not specify why they need the 80 tabs and 20 VMs (in other words, not enough information).