Return to Answer

##Code must not be edited after an answer has been posted Code must not be edited after an answer has been posted even if the answer is still valid after edit.

Help Center states

However, any aspect of the code posted is fair game for feedback and criticism.

And answerer can edit his/her answer to include anything, anytime. And if the code has been changed answerer cannot add what he/she had thought to be included in the future.

##For description

If any part of updated description invalidates an answer, but if more answers are expected, It should be updated with information but yet avoid making answers invalid. Sample And OP can use comments or question body to make sure that doesn't happen

##Don't rush to answer Most new users might still be in the process of updating the question when fast answers are posted. Answerer should try to communicate using a comment or chat with the OP to confirm that question has been finalized. However this might not be feasible due to the competitive nature of Stack Exchange websites. (Everyone loves internet points)

Code must not be edited after an answer has been posted

Code must not be edited after an answer has been posted even if the answer is still valid after edit.

Help Center states

However, any aspect of the code posted is fair game for feedback and criticism.

And answerer can edit his/her answer to include anything, anytime. And if the code has been changed answerer cannot add what he/she had thought to be included in the future.

For description

If any part of updated description invalidates an answer, but if more answers are expected, It should be updated with information but yet avoid making answers invalid. Sample And OP can use comments or question body to make sure that doesn't happen

Don't rush to answer

Most new users might still be in the process of updating the question when fast answers are posted. Answerer should try to communicate using a comment or chat with the OP to confirm that question has been finalized. However this might not be feasible due to the competitive nature of Stack Exchange websites. (Everyone loves internet points)

##Code must not be edited after an answer has been posted Code must not be edited after an answer has been posted even if the answer is still valid after edit.

Help Center states

However, any aspect of the code posted is fair game for feedback and criticism.

And answerer can edit his/her answer to include anything, anytime. And if the code has been changed answerer cannot add what he/she had thought to be included in the future.

##For description

If any part of updated description invalidates an answer, but if more answers are expected, It should be updated with information but yet avoid making answers invalid. Sample And OP can use comments or question body to make sure that doesn't happen

##Don't rush to answer Most new users might still be in the process of updating the question when fast answers are posted. Answerer should try to communicate using a comment or chat with the OP to confirm that question has been finalized. However this might not be feasible due to the competitive nature of Stack Exchange websites. (Everyone loves internet points)

##Code must not be edited after an answer has been posted Code must not be edited after an answer has been posted even if the answer is still valid after edit.

Help Center states

However, any aspect of the code posted is fair game for feedback and criticism.

And answerer can edit his/her answer to include anything, anytime. And if the code has been changed answerer cannot add what he/she had thought to be included in the future.

##For description

If any part of updated description invalidates an answer, but if more answers are expected, It should be updated with information but yet avoid making answers invalid. Sample And OP can use comments or question body to make sure that doesn't happen

##Don't rush to answer Most new users might still be in the process of updating the question when fast answers are posted. Answerer should try to communicate using a comment or chat with the OP to confirm that question has been finalized. However this might not be feasible due to the competitive nature of Stack Exchange websites. (Everyone loves internet points)

##Code must not be edited after an answer has been posted Code must not be edited after an answer has been posted even if the answer is still valid after edit.

Help Center states

However, any aspect of the code posted is fair game for feedback and criticism.

And answerer can edit his/her answer to include anything, anytime. (Also known as pimping an answer) And if the code has been changed answerer cannot add what he/she had thought to be included in the future.

##For description

If any part of updated description invalidates an answer, but if more answers are expected, It should be updated with information but yet avoid making answers invalid. Sample And OP can use comments or question body to make sure that doesn't happen

##Don't rush to answer Most new users might still be in the process of updating the question when fast answers are posted. Answerer should try to communicate using a comment or chat with the OP to confirm that question has been finalized. However this might not be feasible due to the competitive nature of Stack Exchange websites. (Everyone loves internet points)

##Code must not be edited after an answer has been posted Code must not be edited after an answer has been posted even if the answer is still valid after edit.

Help Center states

However, any aspect of the code posted is fair game for feedback and criticism.

And answerer can edit his/her answer to include anything, anytime. And if the code has been changed answerer cannot add what he/she had thought to be included in the future.

##For description

If any part of updated description invalidates an answer, but if more answers are expected, It should be updated with information but yet avoid making answers invalid. Sample And OP can use comments or question body to make sure that doesn't happen

##Don't rush to answer Most new users might still be in the process of updating the question when fast answers are posted. Answerer should try to communicate using a comment or chat with the OP to confirm that question has been finalized. However this might not be feasible due to the competitive nature of Stack Exchange websites. (Everyone loves internet points)