Timeline for Suggested Edit rejected because reviewers didn't know programming language
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 10, 2013 at 8:44 | comment | added | Gilles 'SO- stop being evil' | NO. Correcting mostly-correct answers, like this one, is a valid and encouraged edit. Comments are only for unresolved issues, such as “there's an error but I don't know how to correct it”. If there's an error in a post and you know how to correct it without fundamentally changing the post, editing is the right thing. This is very clearly spelled out in the SE rules, in particular the about page, editing help, and the comment privilege description. | |
| Oct 9, 2013 at 8:02 | comment | added | jmac | Preventing productive edits that provide better quality answers and better resources for future visitors are not 'showing the power of collaborative thought'. Feel free to disagree. Disagreement is good. However, when disagreeing, think about the bigger picture and what support for a certain position will have on the quality of the site. If the quality of the site suffers, no amount of upvotes makes it a good idea. | |
| Oct 9, 2013 at 7:52 | comment | added | sashkello | I don't see where this discussion is going. The upvotes on this answer are clearly showing the power of collaborative thought. I do comply with many meta-discussed practices which I don't really agree with, because community decided this way. Let's leave it for community to decide this time as well. | |
| Oct 9, 2013 at 7:49 | comment | added | sashkello | @jmac If the question was about syntax errors (like this one), all the answers will have similar logic, nothing wrong with that. Fixing syntax errors IS fundamental in such case. The one which fixes them all and have nice explanation of what's going on will get upvotes and probably will be accepted. People don't click on edit history that often and changes of a roll-back are extremely small. Wrongly edited answer will likely be ignored or downvoted, and again, making it wrong is way worse than making wrong comment. | |
| Oct 9, 2013 at 7:33 | comment | added | jmac | @sash, if the edit goes in to the queue, it is not unilaterally applied. This issue is only for sub-2000 rep editors. If the edit (after approval) does not solve the problem, the asker can point that out. If another poster comes across and knows it is wrong, they can roll it back if they have over 2000 rep, or can put it in the suggested edit queue otherwise. Posting a second answer with identical logic and two syntax errors fixed is absurdity, and flies in the face of the collaborative editing principles stated in the [help/editing]. If you take issue with that, make a separate meta question. | |
| Oct 9, 2013 at 7:28 | comment | added | sashkello | Correctness of the answer is verified by votes, not by edit/review system. | |
| Oct 9, 2013 at 7:27 | comment | added | sashkello | @jmac 1. Making wrong edit is FAR worse than making a bad comment. Firstly you are hurting the reputation of the poster. Secondly, why do you suppose he or she will ever get back and re-edit it? This is a slim possibility. 2. Since it is a collaborative effort, discussing improvements in comments is a pretty logical step to improve the post. If you get comments to your answer you are notified and you can get back and re-evaluate your answer accordingly. 3. Don't comment if you think the answer is wrong and you know how to fix it. Post your own answer. It is better than both comment or edit. | |
| Oct 9, 2013 at 5:19 | comment | added | jmac | What benefit does a comment provide over directly editing the code? If the comment is correct, it just adds an extra step to fixing it in the answer. If the comment is incorrect, it creates ambiguity since comments can't be downvoted (and removing the comment would require another comment and cooperation of the commenter, or a mod). If the edit is made, the correction is immediate, and if it is wrong it can be corrected by the person who answered. This is exactly the sort of case the edit system was designed for! | |
| Oct 9, 2013 at 2:50 | history | answered | Hugo Dozois | CC BY-SA 3.0 |