Timeline for Downvoting trivial answers
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 15, 2015 at 13:32 | comment | added | RubberDuck | @Barry then that answer doesn't deserve your upvote and that's fine. It's still useful, and a good answer IMO, so it doesn't deserve a downvote either. However, you are free to vote however you wish. | |
| Oct 14, 2015 at 11:20 | history | edited | Barry | CC BY-SA 3.0 |
typo
|
| Oct 14, 2015 at 11:20 | comment | added | Barry |
Also, I'm not saying advice about, e.g. indentation, is useless. Of course not. I'm saying that writing an answer solely about indentation when the code has, picking another recent example, 35 variables named Ans1 thru Ans35 is suggesting that there's nothing else wrong with the code. And that does make it a bad answer.
|
|
| Oct 14, 2015 at 11:18 | comment | added | Barry | The comment about low rep users is very unconvincing. Low rep is not the same as low programming experience, but even then... if a user can't provide important feedback, then I don't think that user deserves to gain rep. There is no shortage of questions on CodeReview, they cover lots of different languages, lots of them are solving problems that are easily accessible to new programmers (e.g. the Euler questions). So low-rep users should be able to easily find real problems, or ask questions themselves until they learn what real problems look like. | |
| Oct 13, 2015 at 23:28 | history | answered | user86792 | CC BY-SA 3.0 |