文章创意:如何不问问题 [英] Article Idea: How Not to Ask a Question
问题描述
我认为快速解答"中有足够数量的不良问题，我将撰写一篇文章，以便答复者可以链接到该文章，而不必在每次发问者时都要重新解释自己.问一个坏问题.我将创建几个部分，并使每个部分都可链接(以便回答者可以直接链接到问题不佳的原因).本文的暂定标题为如何不问问题".
这是我到目前为止的部分. 随时添加到他们(通过编辑此问题或在下面添加答案).
- 不是问题
- 代码太多
- 格式错误的代码
- 措辞不佳的标题
- 家庭作业问题
- 面试问题
- 缺乏研究
- 细节不够
- 细节太多
- 问题太多
- 工作要求
- 难以理解
- 太无知
- 重新发布
CG:我会删除太无知".如果某人太无知，仅此而已，那么太无知"是什么? 难以理解"的帖子也应该有礼貌，因为我们有来自世界各地的人.我会补充:
问题不是英语-我们接受英语不好的人，但这是一个讲英语的论坛
没有提供代码/没有错误消息-如果您的代码中有错误，我们需要查看它，如果有错误，我们需要实际文本，而不是奇怪的措辞，以及该行会产生错误
范围太广-该问题的答案永远无法在论坛回复中找到，论坛是为有特定问题的人编写代码的论坛，那里的文章向初学者解释新概念.
我还将删除转发，我只是删除了这些转发，然后返回原始转发并说我已经删除了它们作为社区服务的转发.我还要添加一些内容，以解释人们应该编辑他们的帖子以提出更多问题，或者在下面的论坛中发布，答案部分仅用于回答问题.还有关于正确标记的一些知识，最近我有好几次他们从不提及ASP.NET，而是在使用它.
顺便说一句，我意识到这并不是一个真正的问题.我只是使用像Wiki这样的快速解答来产生一些想法，就像当前错误列表和建议和TODO 问题.
再一个
- 代码需求
我认为这是一个好主意，但我认为我们所做的一切；无论是哪种回应，无论是lmgtfy链接，还是链接到Chris的帖子，内容都是关于如何提出问题，侮辱，要求;我们给他们.这些问题将永远存在，并且数量将不断增加.你们仍然很高兴做出如此巨大的努力.
AspDotNetDev的答复:似乎在工作请求"类别下是这样的.或者，您是通过代码需求"来表示其他意思吗?对我来说，工作请求"是指有人要您为他们做他们的工作，这必然会要求您为他们创建代码(那些想要您制作图表或功能需求文档的人除外).
HimanshuJoshi的回复:是的，这就是我所说的代码需求".但是，"request"是您在此处使用的一个卑鄙的词，因为所有这些"requests"仅是"demand"类型的.例如为我提供X的代码/代码段".
Richard MacCutchan的回复:我不敢相信自己做到了.我只是错误地单击了此答案的1票.抱歉:(
HimanshuJoshi的Rant:上帝啊，我的声誉:((.BTW，没关系，Richard
像任何人一样抱歉，它甚至无法读懂任何文章，对我们正在谈论的人，无论是检查还是阅读，都无法解决，这是您最希望得到的要做的就是将人们链接到它，就像我以前链接到有关使用google的文章一样.
AspDotNetDev的响应:有两种可能性:
- 询问者真的愿意做所需的工作，并发布指向他们所遇到的问题的链接，这将有助于他们改善其帖子.
- 询问者对将更多的工作用于解决他们的问题没有兴趣.问，所以告诉他们任何事情都将是一个失败的原因.
由于我计划使文章的每个部分都可链接，并且我计划使链接到每个部分非常容易(我将制作一个目录，并告诉读者右键单击并选择"复制快捷方式"")，将为申请者提供指向适用于他们的特定部分的链接.这将减少他们的困惑.我还将每个部分进行一些介绍(因此，您被发送到这里，没有人回答您的问题...").如果他们然后问为什么将我发送到此链接"，人们可以提供更多详细信息.如果询问者是一个失败的原因，那么将链接发布到最起码的位置将问题从未回答的列表中删除，并将回答该问题的人保存写出完整答案的麻烦.
我不喜欢太无知"类别.这里有不同类型的无知海报:那些由于懒惰而无知的人，以及由于缺乏经验而无知的人.在许多情况下，后一种类型正在尝试学习，可能只需要一点帮助.
除此之外，你得到我的5.
AspDotNetDev的回复:是的，我还没有决定我要称呼那个那个，因为有些人可能会冒犯被称为无知的人.我正在考虑类似"Out of Asker's League"之类的问题.确实表明，询问者对许多基本主题一无所知，以至于他们问如何(例如)构建卫星同步系统超出了他们的能力，因此如果没有他们要求的确切代码来回答他们的问题将是徒劳的.我有时会看到这样的情况:当学生问如何做一些高级的事情时，您告诉他们使用数组，然后他们说:但是我还没有学会如何使用数组，而我的老师告诉我他不会告诉我". .哦，仅供参考，我不认为懒惰的人是无知的……他们通常属于其他类别之一，例如缺乏研究"或细节不足".
I''ve decided that there are a sufficient number of bad questions here in Quick Answers that I''m going to write an article so that answerers can link to it rather than have to re-explain themselves each time a questioner asks a bad question. I''m going to create several sections, and I''m going to make each section linkable (so answerers can link directly to the reason the question is bad). The tentative title of this article is "How Not to Ask a Question".
Here are the sections I have so far. Feel free to add to them (either by editing this question or by adding an answer below).
- Not a Question
- Too Much Code
- Poorly Formatted Code
- Poorly Worded Title
- Homework Question
- Interview Question
- Lacks Research
- Not Enough Detail
- Too Much Detail
- Too Many Questions
- Work Request
- Indecipherable
- Too Ignorant
- Repost
CG: I would remove ''too ignorant''. If someone is too ignorant and that is all, what is ''too ignorant'' ? ''Indecipherable'' posts should be deal with with some politeness, too, because we have people posting from all over the world. I would add:
Question not in English - we accept bad english with grace, but this is an English speaking forum
No code/no error message provided - if there''s an error in your code, we need to see it, and if there''s an error, we need the actual text, not a weird paraphrase, as well as the line that generates the error
Too broad - the answer for this question could never fit in a forum reply, forums are for people writing code with a specific question, articles are there to explain new concepts to beginners.
I''d also remove repost, I just delete those, then go back to the original and post to say I''ve deleted their repost as a community service. I''d also add something to explain that people should edit their post to ask more questions, or post in the forum below, the answers section is just for answers. Also something about tagging properly, I''ve had several recently where they never mention ASP.NET, but are using it.
By the way, I realize this is not really a question. I''m just using Quick Answers like a wiki to generate some ideas, much like the Current Bug List and Suggestions and TODOs questions.
One more
- Code demand
I think this is a great idea but I feel that whatever we do; whatever type of response, be it a lmgtfy link, link to Chris'' post on how to ask question, insult, request; we give to them. These kind of questions will always come and will come in a ever increasing quantity. Still very nice of you to make such a great effort.
AspDotNetDev''s Response: Seems like this would fit under the category of "Work Request". Or, did you mean something else by "code demand"? A "Work Request", to me, is when somebody asks for you to do their work for them, which necessarily will require you to create code for them (except for those who want you to make diagrams or functional requirements documents and such).
HimanshuJoshi''s Response:Yes that''s what I meant by "code demand". But "request" is a humble word you are using here, since all those "requests" are of "demand" type only; Like "provide me code/code snippets for X".
Richard MacCutchan''s Response:I can''t believe I did that. I just clicked the 1 vote on this answer by mistake. Sorry guys :(
HimanshuJoshi''s Rant: ow god, my reputation :(( . BTW, that''s okay Richard
Like anyone you''re talking about would even read the article. Sorry, but it won''t solve anything, b/c the people we''re talking about, don''t check anything or read anything. The most you could hope to do, is link people to it, like I used to link to my article on using google.
AspDotNetDev''s Response: There are 2 possibilities:
- The asker really is willing to do the work required and posting a link to exactly the problem they have will help them improve their post.
- The asker has no interest in putting more work into getting their question asked, so telling them anything will will be a lost cause.
Since I plan on making each section of the article linkable and I plan on making it very easy to link to each section (I''m going to make a table of contents and tell the reader to "right click and select ''Copy Shortcut''"), the asker will be given a link to the specific section that applies to them. This will reduce confusion on their part. I''m also going to have each section give a little introduction ("so, you were sent here and nobody is answering your question..."). If they then ask "why have I been sent to this link" people can reply with more detail. If the asker is a lost cause, then posting the link in the very least gets the question out of the unanswered list and saves the person answering the question the hassle of writing out a full-blown response.
I''m not keen on the "Too Ignorant" category. There are different types of ignorant posters here: the ones who are ignorant by virtue of their laziness, and the ones who are ignorant by virtue of their lack of experience. In many case the latter type are trying to learn and may just need a little assistance.
Other than that you get my 5.
AspDotNetDev''s Response: Yeah, I haven''t decided I''m going to call that one that yet, as some people may take offense to being called ignorant. I''m thinking about something like "Out Of Asker''s League" or something like that. It is really to indicate that the asker is ignorant of so many basic topics that them asking how to, for example, build a satellite synchronization system is above their capibilities and so answering their question without the exact code they request would be futile. I see this sometimes when students ask how to do something advanced, you tell them to use an array, then they say "but I haven''t learned how to use arrays yet and my teacher told me he won''t tell me". Oh, and FYI, I don''t consider lazy people ignorant... they usually fall into one of the other categories, such as "lacks research" or "not enough detail".
这篇关于文章创意:如何不问问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
