So as a mod I have access to some statistics on where traffic for our site comes from. A bit of this information can also be accessed by 25k users.
Let's have a bit of a look at some of that data.
In the last month, just below 2 million visits came from google alone. This is a whopping three orders of magnitude more than interlinkings between code review ...
There's nothing wrong with self-answering a question. There isn't even anything wrong with accepting your own answer if you review your own code and provide new insight that others haven't.
The problem is when your selfie is not actually a review. If you just implemented the advices given in one or more other answers, that's not a review. As such, it's not ...
Don't get me wrong, there is nothing bad with self-answering a question. There isn't even anything wrong with accepting your own answer if you review your own code with distinct points not stated in other answers. The problem comes in when you only implement the advice given to you by other answers into your own answer and choose to accept that instead.
Either action could be acceptable. Keep in mind that there is a possibility of a race condition (another user writing a review while you are enhancing the question). Therefore, I suggest…
Changes that are more trivial can be sneakily edited into the question before any answers have been posted. (Make your edits seamless, as if the question had been ...
No, answers that just contain code are not acceptable, even if it is a self-answer. I have added a notice calling for an explanation.
For an iterative review, is it okay to edit my own question to include revised code?
Short answers and code-only answers
Looking at our iterative review meta post:
Posting a self-answer
If you want to show everyone how you improved your code, but don't
want to ask another question, then post an answer to your own
question. Selfie answers are acceptable on Stack Exchange sites, and
even encouraged: there is a self-learner
you can earn for that. ...
In this scenario I think that specific user actually misunderstood site policies, See the screenshot below.
If it really is a misunderstanding as he claims we should forgive him, If he follow site policies from now on, and do not repeat the same mistake again he was probably saying the truth.
I suggested the user to participate in the chat as well.
If I ...
In recent discussions about Low Quality answers in the Low Quality Queue it was said that
a code dump is not a review, and therefore not an acceptable answer.
By Mat's Mug
Meaning that the answer should still be a review of the code originally posted code, if it is not a review then it is not a good answer.
If the selfie is a code dump, it is not a ...
I guess as long as the moving of the old elements of answer from the question to the self-answer won't invalidate the already given answer(s) it is ok.
If the old elements are code and already reviewed by an answer it is against the site policy.
It is fine to post external links with a description of the contents, but the description is important because sometimes external links become 404s, and the answer becomes useless if it didn't summarise the external content.
All answers should contain at least one insightful remark about the code. So if you propose to post an answer which only contains a link, a description/summary and a "this is relevant to understand encryption" remark, you have failed to write a proper answer and it may be flagged/removed as such.
You could post is as supplement to an answer, but it doesn't ...
In the specific case you linked, it should be altered to become a comprehensive review. That, or deleted. Sounds mean, but what we create here is reviews, not improved code. That the code improves as a result of the review is nice, but there's also reviews like "Your code is perfectly fine".
Nobody learns from "This is version A. This is version B. B is ...
I think you should at the very least provide a complete set of code. Scrolling between various snippets is hard and can lead to answers pointing at new AND old code unintentionally.
Aside from that, be aware that if you move the new code, then it can't be reviewed anymore.
And if you move the old code, then it becomes pretty unreferencable for the other ...
Leave your question the way it is. You have a solution for it, so add that. If someone else is looking for a solution to a similar problem, they won't be able to get anything out of your question if the original code is gone.