Timeline for When to downvote? How can we tell if a person is lazy or just a noob?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:35 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Feb 26, 2017 at 20:48 | comment | added | Derek Litz | @Wildcard, I agree, this would depend on the persons perception of the situation. I imagine there is a sort of arbitrariness when one does not understand though, I would think someone with enough understanding to come to the conclusion "my question must be flawed", rather than, "the community demands too much of me as a new person", knows something about the stack overflow community already. Not sure if this feature exists, and I know there are guidelines, perhaps if the system were to suggest they read them if they get down voted asking questions as a new user in some way :) | |
| Nov 18, 2016 at 6:34 | comment | added | Wildcard | @DerekLitz, I disagree that a downvote can only serve to turn a newb away from programming. It could also encourage them to try to figure out why they got downvoted, which would lead them to articles and advice on how to write better questions. | |
| Dec 2, 2011 at 8:22 | comment | added | Derek Litz | This is exactly the problem though. I'm seeing questions that are not obviously bad being down voted. Sure, this will happen, and perhaps I just got a skewed view the last couple days, but that doesn't make the problem solve itself. A downvote to a newb could only add to their confusion and only server to turn them off from programming. My observation leads me to believe what you stated is not as obvious as it should be. | |
| Dec 2, 2011 at 8:08 | history | answered | Madara's Ghost | CC BY-SA 3.0 |